Forum Discussion

Claudius's avatar
Claudius
Boss
13 years ago

Getting details for user viewed on profile page

Now here's a tough one: I'm currently working on a custom component extending the View User Profile page with links to a few internal tools. (This component of course will only be visible to certain...
  • Claudius's avatar
    Claudius
    13 years ago

    Unfortunately not :( That takes me back to the 303 error.

    But reading a bit further into the UserReference class in the REST API JavaDoc I think this should be the way to go

    <#assign viewed_sso_id = restadmin("/users/id/${page.context.user.id}/ref/sso_id").value />

    At least http://community.lithium.com/my-community/restapi/vc/users/id/8/ref/sso_id in the browser shows a more friendlier 303 error then:

    UserRef[id=-1] does not have access to RequiredPermissions[(allow_manage_users)] on CommunityByDisplayIdRef

    But executed as restadmin Freemarker call in my custom component then shows yet another discouraging 303:

    The object 'User ....' inherently does not support the action 'sso.action'

    Guess I need to work on some other component first to get the head free again :(

     

AdamN's avatar
AdamN
Khoros Oracle

The error you're seeing means that you aren't properly authenticated to make that particular REST API call. SSO ID is a protected resource, so you'll need to be authenticated as an administrator to see the SSO ID for other users. You definitely have the right idea though...

 

If your component is on the profile page, you can use the page context object to determine the user whose profile page you're showing. Here's an example of how to get the id for that user:

${page.context.user.id}

Once you have the user id, you can use that in your REST API call to get the SSO ID for the user. Keep in mind that you'll likely need to use restadmin() instead of rest() to make your call for the reason I mentioned previously.

Claudius's avatar
Claudius
Boss
13 years ago

Hi Adam,

thanks for digging into this. I still couldn't make it work though, e.g. the returned SSO Id is empty. Here's the full component code I tried:

<#if user.registered >
	<#assign rank = restadmin("/users/id/${user.id?c}/ranking").ranking />
	<#if rank.name?? && ((rank.name == "Staff Moderator") || (rank.name == "Community Manager")) >
		<#assign viewed_sso_id = restadmin("/users/id/${page.context.user.id}/profiles/name/sso_id").value />
		SSO ID: ${viewed_sso_id}
		<a href="https://secrettool.company.com?user_id=${viewed_sso_id}">User in Backoffice</a>
	</#if>
</#if>

 Any idea?

 

  • AdamN's avatar
    AdamN
    Khoros Oracle
    13 years ago

    I'm not sure you can access the SSO ID through the profiles method like that. There's a method specifically for getting the SSO ID, so I'd suggest that instead. For getting the SSO ID, try this instead:

     

    <#assign viewed_sso_id = restadmin("/users/id/${page.context.user.id}/sso_id").value />

     Let me know if that doesn't work for you.

    • Claudius's avatar
      Claudius
      Boss
      13 years ago

      Unfortunately not :( That takes me back to the 303 error.

      But reading a bit further into the UserReference class in the REST API JavaDoc I think this should be the way to go

      <#assign viewed_sso_id = restadmin("/users/id/${page.context.user.id}/ref/sso_id").value />

      At least http://community.lithium.com/my-community/restapi/vc/users/id/8/ref/sso_id in the browser shows a more friendlier 303 error then:

      UserRef[id=-1] does not have access to RequiredPermissions[(allow_manage_users)] on CommunityByDisplayIdRef

      But executed as restadmin Freemarker call in my custom component then shows yet another discouraging 303:

      The object 'User ....' inherently does not support the action 'sso.action'

      Guess I need to work on some other component first to get the head free again :(

       

      • AdamN's avatar
        AdamN
        Khoros Oracle
        13 years ago

        Hmmm... it should work with or without the "ref".

         

        A couple things I would suggest confirming...

        1. Is SSO turned on and configured in your environment?
        2. Does the account you're trying to obtain an SSO ID for actually have an SSO ID? On stage, this may not necessarily be the case if the account was created via Lithium Registration instead of SSO.

        If either of the above isn't true, then that would likely be the issue.