Skip to main content

Currently, inSided SSO is only configured as a consumer and not an identity provider (IDP), so while we can pass accounts into inSided via SSO, we cannot pass accounts out from inSided to another system.

Use Case

We are trying to set up an integration between our inSided community and our LearnUpon portal for our Academy. (LearnUpon is a learning management system or LMS.)

The inSided SSO docs focus on SSO as a consumer but not as an IDP, and this is where we are stuck. We want to set it up so that a user account from our inSided community passes the user information/credentials into LearnUpon. According to inSided Support, this is not currently possible.

Rationale

Zaps just don’t cut it for certain integrations, especially where we are trying to provide the smoothest experience possible for our customers. Our goal here is to reduce the number of logins for our customers and provide them easy access to our resources outside of the Community.

Be the first to reply!