When Single-Sign-On Fails-2 - How a merged account in AMS cause a failed SSO in LMS

2 - How a merged account in AMS cause a failed SSO in LMS

Video Transcription

Video Summary

In this video, it discusses a scenario where two user accounts are merged into one in OASIS, resulting in a single account with conflicting email and member ID information. OASIS requires unique email addresses and member IDs for each account. When the merged user tries to log in, OASIS faces challenges identifying the correct user due to the duplicate email address issue. As a result, the single sign-on process fails. The video aims to address this issue in the next tutorial.

Meta Tag

Creation Year 2024

Keywords

OASIS

user accounts

merged

conflicting information

single sign-on

SSO

Single Sign On

AMS

merge account in AMS

failed SSO

bandung

KGConcept: User Account Merge (10)

KGConcept: Account Attribute Inheritance (8)

KGConcept: Unique Email Address (10)

KGConcept: Unique Member ID (10)

KGConcept: Single Sign-On (9)

KGConcept: Member ID Matching (8)

KGConcept: Account Mapping (7)

KGConcept: Email Conflict (9)

KGConcept: Login Failure (8)