Hi
We have two services which a user has access to, whereas as login ID we
use the email address of the user.
Since the email address of a user can change, the user can change the
email address inside the service as follows:
- First the user signs in to the first service (service1) with
Hi! I'm new with this plataform and need help.
I configured Cas (over Tomcat) with x.509 certificate authentication about
documentation (https://wiki.jasig.org/display/CASUM/X.509+Certificates), adding
the root CA to .keystore and java/securty.
I have added my personal certificate in my web
Hi! I'm new with this plataform and need help.
I configured Cas (over Tomcat) with x.509 certificate authentication about
documentation (https://wiki.jasig.org/display/CASUM/X.509+Certificates),
adding the root CA to .keystore and java/securty.
I have added my personal certificate in my web
Your browser is remembering which certificate to use, and so long as it
has not been 'locked' (as in the case of a hardware token, lockable
[software] keychain, encrypted key, etc) will continue to simply use it
for as long as the browser as open. Other browsers like Apple's Safari
will even
Hi,
Sorry for bugging on this one.
But if no one answering I assume there is a bug?
Thanks.
- Reply message -
From: ray id...@cellebrite.commailto:id...@cellebrite.com
To: cas-user@lists.jasig.orgmailto:cas-user@lists.jasig.org
cas-user@lists.jasig.orgmailto:cas-user@lists.jasig.org
Hi,
We decided to force users to logout as the safest and simplest solution
for us.
Best regards,
Jérôme
2014/1/13 Michael Wechner michael.wech...@wyona.com
Hi
We have two services which a user has access to, whereas as login ID we
use the email address of the user.
Since the email
Hi,
The documentation for OAuth client support in CAS 4.0 is here:
https://wiki.jasig.org/pages/viewpage.action?pageId=56164890.
It's pretty similar between 3.5 and 4.0, except that the classes has been
renamed from *Provider to *Client. Here is the Javadoc for clients:
Hi Jérôme
Thanks very much for your feedback.
I guess we will logout the user from CAS, but keep the user signed in at
the service where he/she changed the ID.
But I am not sure yet whether this will have some unexpected
side-effects and need to sleep over it :-)
Michael
Am 13.01.14 14:47,
Hi,
Our way : everytime a user change something in his management application,
we display a message like Your change will be taken into account only
after logout. Please click this link to logout. And the user is logged out
from all applications including the management one.
Best regards,
Jérôme
The problem is when y go again to https://my.cas.com/login the web browser
don't ask me for confirm the personal certificate, and Cas send directly to
Log In Successful. The Cas log show, ACTION: AUTHENTICATION_SUCCES and
ACTION: TICKET_GRATING_TICKET_CREATED.
That is the expected default
Hello,
I'm upgrading our CAS server from 3.3.5 to 3.5.2 and I've hit a snag.
I've used the following docs to configure the cas system:
https://wiki.jasig.org/display/CASUM/Trusted
http://www.usask.ca/docs/cas/trusting.html
https://wiki.jasig.org/display/CASUM/Building+and+Deploying
Hi Jérôme
How do you notify the other applications that the user got logged out
from the management application?
Thanks
Michael
Am 13.01.14 16:09, schrieb Jérôme LELEU:
Hi,
Our way : everytime a user change something in his management application,
we display a message like Your change will
I looked over the LPPE implementation and didn't see anything specific
to ppolicy. So I wouldn't say it's a bug, it's just not there yet.
Marvin and I will set aside some time this week to document the
configuration and will supply any necessary patches to 4.0-RC3 to
support ppolicy. You shouldn't
Hi Daniel,
So you basically saying that CAS does using using the ppolicy request control
in order to generate different result code for user locked account?
Thanks.
-Original Message-
From: Daniel Fisher [mailto:dfis...@vt.edu]
Sent: Monday, January 13, 2014 7:41 PM
To:
Hi,
Thanks for your response.
So you saying with the current cas release(3.*) ppolicy not working well?
Did you manage with CAS 4.0?
-Original Message-
From: Andres [mailto:afolg...@gmail.com]
Sent: Friday, January 10, 2014 10:09 AM
To: cas-user@lists.jasig.org
Subject: Re:[cas-user]
Hi, it's CAS 4.0 where I tested it. It uses a different LDAP library (ldaptive)
which works better. If you use the configuration I exposed, the binding
response to LDAP will include the information you need: accound expired,
password expired, time remaining to password expiration and grace
Hi,
I afraid to move onto 4.0 until it will be an official release.
About Daniel news. Yes it's great. We kind of stuck here without having CAS
supporting ppolicy or any instructions how to use it with all the supporting
response codes.
Waiting for it.
Thanks.
-Original Message-
17 matches
Mail list logo