Return to Jive Software

Skip navigation
605 Views 5 Replies Last post: Mar 3, 2010 4:21 PM by bryan.head RSS
rrutan Intermediate 736 posts since
Jun 5, 2007
Currently Being Moderated

Feb 9, 2010 8:23 AM

Delegated Authentication - ProfileField Manager only returning attributes that are Editable?

I'm trying to use the delegated Authentication feature in SBS 4.0; however, I'm running into an issue with the ProfileFieldManager.  It appears that if a field is not editable, it is not showing up in the list of fields returned from ProfileFieldManager.getProfileFields.  I've looked through the DAOImpls and ManagerImpls for this; however, I do not see where this is getting filtered out.

 

I would like to use the Delegated Authentication service to pull data from a foreign system, sync it on login, but not allow the user's to edit it.  As it stands, the only way I can get this to work is by making the profile editable...which renders an edit-time field on the profile page during Profile edit.

 

To replicate this issue:

  • Create a new profile field (mine is called alias)
  • Make it Externally Managed (or leave it blank for all options)...
  • Save
  • Setup delegated service to return XML with the <alias>...</alias> tags in it.
  • Debug the DelegatedSSOProvider, in the authenticate method, the profileValues list comes back empty on login
  • NOW, go to Admin console, enable Editable on the alias field, and retry your login. (no restart required)
    • Debug should now show a value in the profileValues list

 

Any known issues behind this?  Much appreciated.

bryan.head Jive Employee 698 posts since
Dec 3, 2009

Hi Ryan,

 

I'm looking into the exact workings of ProfileFieldManager. I'll let you know what I find.

 

Best,

Bryan

bryan.head Jive Employee 698 posts since
Dec 3, 2009

Hi Ryan,

 

You're right, it doesn't look like it should be filtered out. Would you run

 

SELECT fieldID, idx FROM jiveProfileField ORDER BY idx;

 

with alias marked as not editable, and post the results?

 

Thanks,

Bryan

bryan.head Jive Employee 698 posts since
Dec 3, 2009

Hi Ryan,

 

Apologies for the delay on this one. I'll definitely let you know if I find anymore information on it.

 

Best,

Bryan

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.