help.sitevision.se hänvisar alltid till senaste versionen av Sitevision
You choose what is sent as identifier in the SAML ticket at set-up of IdP and SAML solution. You can choose between the different unique fields available to a user in the custom directory. We recommend that you choose a stable identifier without direct personal data. The identifier in the SAML ticket does not have to be the same as the username for the login. The identifier is case-sensitive; in other words, "kallekula" is not the same as "KalleKula".
The identifier in the SAML ticket is the basis for the association between a user in the Federated Directory Service and SiteVision. Therefore, changes to the identifier result in SiteVision not being able to reconnect the user with the user item.
All changes to the identifier result in the creation of a new user item in SiteVision. Therefore, if the identifier is changed, the user will still be able to log in to SiteVision with the SAML ticket, but now get another user item. Therefore, on websites where Social Collaboration is enabled, the new user item will create a new social profile.
There are a couple of different scenarios for when the identifier changes.
In the first case, you can be proactive and through an order job from SiteVision Support get help to both create the new user items and reconnect social profiles, so that users retain their old profile and settings.
In the other two cases, the "damage" is already done. SiteVision Support can help to carry out the changeovers even then, but because the order job needs some foresight, you can live with that some or all users over a period do not have their old profiles and have no settings.
SiteVision has two types of user item.
Information about the user is saved on the user item.
If Social Collaboration is enabled on the website, a social profile is created by SiteVision for each user item that is created. The user item and social profile have a two-way reference and are therefore interdependent.
The social profile saves information associated with the user and Social Collaboration.
The page published: