AEM cloud | Azure SSO SAML login failure | Community
Skip to main content
P
pradeepdubey
Level 2
July 6, 2022

AEM cloud | Azure SSO SAML login failure

  • July 6, 2022
  • 1 reply
  • 2115 views

Hi Folks,

 

I am integrating Azure SSO in AEMAaCS publish instance. 

After doing all setup I am getting one last exception 

 

*ERROR* [FelixLogListener] LogService.org.apache.felix.http.jetty Exception while processing request to /saml_login (org.apache.felix.log.LogException: java.lang.SecurityException: javax.jcr.PathNotFoundException: keystorePassword not found on /etc/truststore)

 

All changes like dispatcher, SAML authentication handler, referrer filter, sling auth configurations etc are done as per the need. I installed and took the certificate package from local AEM instance and deployed as part of cloud manager pipeline. 

 

Could you please help me to resolve this issue in cloud publish instance. Appreciate the help.

 

Thanks,

Pradeep

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
July 6, 2022

Hi,

Can you check https://www.albinsblog.com/2018/05/exceptionsissues-while-configuring-aem-saml-authentication-handler.html

if this is related to AEM user or idp certificate alias

Arun Patidar
    P
    pradeepdubeyAuthor
    Level 2
    July 6, 2022

    Hi,

     

    Those issues/solutions were identified either on prem or AMS. Where admin user can directly upload the certificates manually and create trust store or key store. We are using cloud.

    I think the issue could be keystore(in my case it is truststore) password is not same what I used in local when creating the truststore. Or is it a permission issue to the group where user is getting added after successful authentication?

      P
      pradeepdubeyAuthor
      Level 2
      July 7, 2022

      @pradeepdubey could you please try removing the "keystore" node under /home/users/system/.... and recreate the keystore.


      In the cloud environment crx/de access is disabled. Also dev console repository browser is not allowing anything to delete, that is just read only. 

        Terms & ConditionsAccessibility statement

        Loading footer...