Hi,
I have once got this error too. User A logged in and saw User B's profile.
They were of different organisations, but both were using delegated
authentication using pac4j and their own Identity Providers. This problem
has never been seen when users use local LDAP.
I followed the suggestion
Reposting essentially again as I just cannot make this go. My heartfelt
apologies that I'm circling to the list again on this.
As before. I want to be able to specifically require an exclusive
Authentication Resource per Service definition. I cannot seem to make
this work.
CAS 6.2.3
LDAP
Michele,
Are you saying that this service will periodically send the user back to cas to
get updated attributes/re-authenticate (that is the service has a very short
session, say 20m)?
Perhaps you could turn off attribute caching,
Stewart,
I would recommend double checking the contents of the assertion that is
captured through the SAML tracer.
You’ll want to verify that you’re providing the correct attributes as well:
Name ID Immutable ID (objectGUID)
IDPEmail UPN
You’ll also
Hello.
I'm using cas 5.3, succesfully configured it with SAML2 support.
For every service I have a specialized groovy script that rewire the
attributes for the specific endpoint.
Until now the authentication query gave me all I needed to build SAML2. The
authentication query is done via Sql
Hello,
There's only one user-visible difference between 6.2.2 and 6.2.[34] : the
alert message is not displayed.
Otherwise, everything works as expected and we are redirected to the app
after login.
Yes, I have checked the source code, and the warning message is still
supposed to be
