When a user logs into SchooLinks using SSO, we rely on ClassLink’s SourcedId field to match a portion of the Third Party Account ID of that user in SchooLinks. We have observed scenarios where this sourcedId field can be changed for a specific user in ClassLink, Example: A user moves from a Teacher role in the district to a role as an Aide. When the sourcedId is changed and we have a mismatch between what is in ClassLink and SchooLinks, the SSO connection is broken.

However, we have also noticed that ClassLink can “cache” the old SourcedId in an SSO connection attempt which would also cause a mismatch if the user identifier was correctly update in SchooLinks after the sourcedId was changed in ClassLink.

In the above screenshot, you will notice that in ClassLink the SourcedId is set to 7899990979. This is the new SourcedId. However on Nov. 16th, the SSO attempt was still using the old SourcedId (no longer in ClassLink) TCH_990979. The SSO login was then successful on Nov. 21st. when the correct SourcedId was passed.

ClassLink Support has instructed that if we run into this scenario where a user is unable to login after a recent update to a SourcedId field, we should either instruct the district to open a support ticket with ClassLink’s help desk or to have the district wait a few days to try again (if that is an acceptable solution).