BindLdapAuthenticationHandler logs the complete stacktrace if a user provides
the wrong pwd. I think it does not make sense to flood the log files with
stacktraces for each typo in pwd ...
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, c
is there any way to use LPPE with two cascading BindLdapAuthenticationHandler?
we have a chained login: first testing ldap with regular users, on failure
testing ldap with guest users. UserIds are distinct in both ldaps.
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch..
we recently upgraded from CAS 3.4.5 to 3.4.8 and now have quite often
NoSuchConversationException, which we did never see in 3.4.5:
org.springframework.webflow.conversation.NoSuchConversationException: No
conversation could be found with id '1' -- perhaps this conversation has ended?
Any ideas
release notes for 3.4.6 say new feature is "Flag to disable single log out
during ticket clean up", but I don't find any documentation about this flag.
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, s