SSO Users - Update Login Details to Prevent Duplicate Profiles

  • Updated

Ensure a user retains access to their historical data (in Unimarket) when their name, username, or email changes. This article explains how to update before or after, the user's information has changed (e.g. last name, email address). To prevent or resolve duplicate user profiles.

 

Prerequisites

  • User with the Community Administrator role
  • SSO is enabled and configured, within the community.
  • User’s updated details (first name, last name, username, email)

 

Limits & Notes

  • Username is the primary identifier used by Unimarket for SSO login matching.
  • SSO does update:
    • First Name
    • Last Name
    • Email Address
  • SSO does NOT update:
    • Username (must be manually managed).
  • Always update the username correctly to avoid duplicate account creation.

 

Option 1: Update User Details Before the User Logs in (Recommended)

  • Navigate to the Administration module and click Users.
  • Locate the user and select Edit.
  • Update the following fields:
    • First Name
    • Last Name
    • Username
    • Email Address
  • Click Save
  • Ask the user to log in via SSO, using their updated username. To successfully access the existing profile with historical data.
     

Option 2: Fix a Duplicate User After SSO Created a New Account

  • Navigate to the Administration module and click Users.
  • Locate the newly created user profile (e.g. created by SSO auto-provisioning).
    • Note: This profile will not contain any historical data.
  • Select Edit and change the username to something temporary (e.g., "username-bad")
  • Locate the original user account (e.g. the profile with historical data).
  • Select Edit and update:
    • First Name
    • Last Name
    • Username (set to the correct/new username)
    • Email Address
  • Click Save
  • Ask the user to log out and log back in, via SSO. To successfully access the existing profile with historical data.

 

Results/Validation

  • User logs into Unimarket using SSO successfully.
  • Historical data (orders, approvals, etc.) is visible.
  • No duplicate active user profile exists with the same identity.

 

Troubleshooting

  • User still cannot see historical data: 
    • Confirm they are logging in with the correct username tied to the original account.
  • System keeps creating new users on login: 
    • Verify that the username in SSO attributes matches the Unimarket username.
  • Email or name updates are overwritten:
    • Expected behavior: SSO automatically updates First Name, Last Name, and Email fields.
  • Cannot update username due to duplication error: 
    • Ensure the duplicate username has been temporarily reassigned first.