AEM Forms SAML authentication | Community
Skip to main content
October 21, 2020
Question

AEM Forms SAML authentication

  • October 21, 2020
  • 3 replies
  • 1948 views

I am trying to setup SAML Authentication for SSO on AEM Forms 6.5. I am following this https://docs.adobe.com/content/help/en/experience-manager-65/forms/administrator-help/setup-manage-domains/configuring-authentication-providers.html#saml-settings 

I am creating a new Enterprise Domain and I can save the SAML Authentication provider but when I try to save the new domain it returns "not found" and the server.log has "java.lang.IllegalArgumentException: Value too long: " followed by an 8,937 base 64 string.  That string is not in the SAML Identity Provider Metadata file so I don't know where it is coming from or why it is breaking.

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

3 replies

October 21, 2020

i have done AEM Forms with OKTA on OSGI. the steps are documented here

https://docs.adobe.com/content/help/en/experience-manager-learn/forms/single-sign-on-with-okta.html

October 22, 2020
I am working with Active Directory and don't believe SAML in OSGI will work for adminui login on the other side of AEM.
Kosta_Prokopiu1
Adobe Employee
Adobe Employee
October 26, 2020
@gphillips58 this is too complicated an issue to be resolved on this forum. If you have followed the instructions in the manuals but receive unexpected results, you could contact Support, provide all the neccesary information and have them help you with it. Here we are limited to guesswork what may be missing or wrong and have only limited time for each issue.
Mayank_Gandhi
Adobe Employee
Adobe Employee
October 26, 2020

@gphillips58  There have been UM related fix lately on 6.5. Please try with 6.5.6 jee.

October 26, 2020
Thanks! I'll wait for the next service pack though, because it is supposed to have a fix for "Version number may be negative or greater than 255 at com.adobe.agl.util.VersionInfo.getInstance(VersionInfo.java:191) " that occurred when we updated to Java 1.8.0_261.