Skip to main content

I am trying to use the user API to get the sso info. However when I was using the “Fetches all users” API, some of the users have null values in the insided_sso_customeruid field. I used the “Find User by field / value” API to search for the exact same user again and found this user does have values in the sso field. I am wondering what’s the reason that those fields are not consistent through two endpoints?

This problem doesn’t apply to all users and most of the users have the same values in the insided_sso_customeruid field and the sso field.

 Hi @ZFU 👋,

Apologies for the delay in replying to this topic! 

Our engineers took a look into this and let us know that these fields are distinct, and serve(d) a different purpose:

  • insided_sso_customeruid was used by legacy SSO and is not filled anymore

  • the sso object is related to our current SSO implementation and is reliable

As you have a relatively new community we suspect that the legacy field is filled with the new information through the API with the primary SSO link.

In any case, you should use sso as the most reliable field.

Let me know if this makes sense or if you have any questions 😁

Reply


Terms & ConditionsCookie settings