It is not the principal to establish the initial LDAP connection. By 'admin' user I mean just the default admin user that is created for jboss portal. It is just another user called 'admin' and has admin privileges. Obviously this user would go away in prod, but I'm curious why this user is being singled out. The fact that it has a username and password of 'admin' (dev environment only) and fails is suspicious when all the regular users (ckantzer) authenticate just fine.
-----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Monday, June 29, 2009 12:47 PM To: [email protected] Subject: Re: [cas-user] Password changes ignored by CAS > Are there constraints or filters that would prevent an 'admin' user from being authenticated on the CAS side? I took "admin user" to mean the principal you used to establish your initial LDAP connection, e.g. the value of userDN in the following XML snippet you shared previously: <bean id="contextSource" class="org.springframework.ldap.core.support.LdapContextSource"> <property name="pooled" value="true"/> <property name="urls"> <list> <value>ldap://hostname:port</value> </list> </property> <property name="userDn" value="user"/> <property name="password" value="password"/> <property name="baseEnvironmentProperties"> <map> <entry> <key> <value>java.naming.security.authentication</value> </key> <value>simple</value> </entry> </map> </property> </bean> I get the impression that you actually mean "admin user" in a different sense. Can you clarify? M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
