


How to configure SSO on LiveCycle ES 8.2 update 1 for OpenLDAP?
I can configured & synchronized user and group from OpenLDAP, but i can't configuring SSO.
please help.
Thank you
Views
Replies
Sign in to like this content
Total Likes
What do you mean by SSO here. is it just username/password based authentication. If that is required then just add a Authentication provider for that domain and things should work for you there
Thank you from your answer,
Views
Replies
Sign in to like this content
Total Likes
2009-11-06 12:50:04,711 INFO [com.adobe.livecycle.formdataintegration.server.FormData] ALC-FDI-001-307: Processing importData operation on source document 3465256.
2009-11-06 12:50:07,680 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 29632435] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:08,539 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 29632435] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:08,649 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 29632435] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:08,774 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 29632435] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:08,774 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 33415108] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:08,789 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 25732012] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:08,805 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 22446341] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:08,805 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 29632435] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:10,946 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 25732012] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:11,117 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 33347835] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:11,149 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 25732012] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:11,164 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 25732012] Portal SSO can not proceed as canonical name is null
2009-11-06 12:50:11,164 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 22446341] Portal SSO can not proceed as canonical name is null
2009-11-06 12:51:02,711 INFO [com.adobe.idp.um.auth.filter.PortalSSOFilter] UserM:: [Thread Hashcode: 32408616] Portal SSO can not proceed as canonical name is null
2009-11-06 12:51:03,821 WARN [com.adobe.idp.um.auth.filter.SSOFilter] No value found for header [uid] hence Headers based SSO cannot be performed. This may be due to the SSO using headers is not configured properly or incorrect headers are mapped in the Portal SSO configuration page.
I setup Portal Configuration for enable Single Sign-On (SSO)
Views
Replies
Sign in to like this content
Total Likes
SPNEGO based SSO would only work with Microsoft Active Directory and not with any other directory server like LDAP. With OpenLDAP you would have to rely on username/password based authentication
The Header based SSO requires a Third Party Security Product like Netigrity which handles the SSO.
Views
Replies
Sign in to like this content
Total Likes