Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM 6.2 SAML Login issue

Avatar

Level 4

Dear All,

We have migrated AEM 6.0 to 6.2. After we migrated to 6.2 when we logged in through SAML in 6.2 our userid is creating like encrypted. due to which our some functionality is not working fine

Attached below is the screenshot for 6.2 , how users are creating under publish user profiles.

Also I have attached the screenshot for saml configuration for our 6.2.

Please help me on this how the user should be created under user profile without encryption .

1 Accepted Solution

Avatar

Correct answer by
Level 3

Thank you all for the interest .. Tagging issue got resolved post giving read access to system user to access /etc/tags/<project>

View solution in original post

8 Replies

Avatar

Level 9

Hi Sunitha,

You have attached same screenshot twice.  I am using you mean randamized home node path?   Then it is expected. What problem are you facing.

Thanks,

Avatar

Level 3

Hi Prince,

Thanks for your help here.

The exact issue here is when user is created post SAML authentication was created with a plain text below /home/users before upgrading to 6.0. But post upgrading same user is create with some encrypted way

 

example: In 6.0 user is created in a way /home/users/sandeep.vishwanath@gmail.com

In 6.2 /home/users/Zskdfkdfdhfjjfdhdjfjd for the same user and email attribute of this user is saved as sandeep.vishwanath@gmail.com here we are using SFDC login id which is user mail id for logging in to AEM portal through SSO.

Due to this one of Service which we have is failing to  fetch the user attribute being synced. Login is happening but code written was not able to find the user based on mail id and find the tag information associated with that user.

Avatar

Level 9

Hi Sandeep,

  it is expected behaviour in 6.2 for security reason. You can configure to behave as in 6.0 By configuring in felix console.  Before taking that path please provide us reason of problem you are facing with Zskdfkdfdhfjjfdhdjfjd ?

Thanks,

Avatar

Level 3

Hi MC,

Thanks for your reply.

We had further debugged the issue and found 

final TagManager tagmanager =getResourceResolver().adaptTo(TagManager.class);

final Tag tag = tagmanager.resolve(tagName);

tag information is throwing null,It's failing to resolve the tagid passed.not sure what has gone wrong we have correct tags which we were using in 6.0 is deployed in 6.2 and the same lines of code was working fine in 6.0

Is there any changes required for the way we are getting tags required to get this working?

Your inputs are appreciated.

Thanks

Sandeep

Avatar

Level 4

Hi, Sandeep

Please upload logs. It may be helpful to debug the issue. 

Thanks! 

Avatar

Correct answer by
Level 3

Thank you all for the interest .. Tagging issue got resolved post giving read access to system user to access /etc/tags/<project>

Avatar

Level 3

Thank you all for the inputs .... Tagging issue got resolved post giving read access to system user to access /etc/tags/<project>