Expand my Community achievements bar.

SOLVED

AEM SSO Authentication - Multiple users get created (with same synchronized attributes) after a successful authetication

Avatar

Level 2

Good morning, afternoon or evening.

 

I'm trying to set up AEM SSO authentication with Azure and on top of that, I'm also trying to synchronize attributes (which works just fine. I'm using Adobe Granite SAML 2.0 Authentication Handler to achieve that), after the Azure SSO authentication ends successfully. A user with synchronized attributes is created in AEM User Management section (as expected.) The thing here is that every time I authenticate the same user, new users are created with the same data (email, name, lastname). The only difference among them is their ID.  Am I missing something like setting a constraint to avoid records with the same data? 

 

This is how the duplicated records look like.

Oscar_S360_0-1693531226669.png Oscar_S360_2-1693531460909.png

 

In case it helps, under the Adobe Granite SAML 2.0 Authentication Handler section, I checked the Autocreate CRX Users option

Oscar_S360_3-1693531709869.png

 and this is how I'm synchronizing the Azure SSO response attributes

Oscar_S360_4-1693531942423.png

 

Thanks in advance for any support and guidance you could give me.

Regards, Oscar.

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Level 2

For those reading and facing a similar issue, I could fix it myself.

After doing a research and reading other posts, I noticed I had left the UserID attribute empty. (that's the reason why user records have a random string as ID and more than one user can have the same synchronized data) 

Oscar_S360_0-1693587692699.jpeg

All I had to do to fix the issue was setting an XML attribute (from the athentication response) in that UserID attribute field (in my case I used the user's email address as unique ID)

 

Oscar_S360_1-1693587797444.png

 

Oscar_S360_2-1693587853776.jpeg

 

Then I just had to save changes and test my user again (multiple times, to make sure it was not being duplicated like before) 

Oscar_S360_3-1693587960892.jpeg

 

Hope this info can help others facing similar issues (synchronized attributes and duplicated users with random ID's).

 

Regards, 

Oscar.

 

 

View solution in original post

1 Reply

Avatar

Correct answer by
Level 2

For those reading and facing a similar issue, I could fix it myself.

After doing a research and reading other posts, I noticed I had left the UserID attribute empty. (that's the reason why user records have a random string as ID and more than one user can have the same synchronized data) 

Oscar_S360_0-1693587692699.jpeg

All I had to do to fix the issue was setting an XML attribute (from the athentication response) in that UserID attribute field (in my case I used the user's email address as unique ID)

 

Oscar_S360_1-1693587797444.png

 

Oscar_S360_2-1693587853776.jpeg

 

Then I just had to save changes and test my user again (multiple times, to make sure it was not being duplicated like before) 

Oscar_S360_3-1693587960892.jpeg

 

Hope this info can help others facing similar issues (synchronized attributes and duplicated users with random ID's).

 

Regards, 

Oscar.