We have gotten cas-mfa with CAS 4.1.4 running and configured with an ldap auth
handler and duo authenticating OK and we are getting service tickets generated.
Our next step was to get ehcache configured to use the same cache as our
existing 3.5.0 CAs servers so that ST's would go there and
Hi there,
We have several apps using CAS 4.1.5. Different apps have different idle
session timeout setting, some timeout after 30 minutes, other 1 hour, etc.
Two questions.
1. when user Logout from a web app., it provides best user experience if the
app logs out the user AND logs out
Hi,
I am overlaying 4.1.5 CAS and using JPA service registry. I have had
success with JSON file based service registry. Now I am moving all service
definition into Oracle tables.
How should values be stored in DB table columns? Do I just copy the JSON
data and paste it there?
I have this
Hello,
i'm using CAS 4.1, and i configure memcache for ticket store .
when a configure an application, i log into the cas portal, and i got this
error in my catalia.out :
*2016-03-31 14:27:47,504 DEBUG
[org.jasig.cas.audit.spi.TicketOrCredentialPrincipalResolver] - *
2016-03-31 14:27:47,475
Hi there,
We have several apps using CAS 4.1.5. Different apps have different idle
session timeout setting, some timeout after 30 minutes, other 1 hour, etc.
Two questions.
1. when user Logout from a web app., it provides best user experience if
the app logs out the user AND logs out CAS
On Github: https://github.com/Jasig/cas/issues/new ...
2016-03-31 10:20 GMT+02:00 Uwe Wolfinger :
> Please let me know how and where to open the issue.
>
> Kind regards,
> Uwe
>
> Am Donnerstag, 31. März 2016 09:21:13 UTC+2 schrieb leleuj:
>>
>> Hi,
>>
>> OK. You raise a
Please let me know how and where to open the issue.
Kind regards,
Uwe
Am Donnerstag, 31. März 2016 09:21:13 UTC+2 schrieb leleuj:
>
> Hi,
>
> OK. You raise a use case we don't really think about, but calling the
> /oauth2.0/profile url to get the user profile is already an access token
>
Hi,
OK. You raise a use case we don't really think about, but calling the
/oauth2.0/profile url to get the user profile is already an access token
validation process as if the access token is not valid, you won't get any
user profile.
Can you open an issue for that use case? So we can think how