Perhaps this might be of help:
https://github.com/Unicon/cas-addons/wiki/Role-Based-Services-Authorization
Cheers,
Dmitriy.
Sent from my iPhone
> On Jan 8, 2014, at 20:26, Joe Osowski wrote:
>
> Is there a best practice for allowing certain users (being a
> principal) access to certain servi
Is there a best practice for allowing certain users (being a
principal) access to certain services?
Thanks!
-Joe
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/J
So hey guys. Thanks the help a month back or so on how to best
authenticate a user via a one time token.
Here is my implentation:
https://github.com/PLOS/ambra-cas/tree/dev-token-authorization
If anyone else wants to use it as a template!
--
You are currently subscribed to cas-user@lists.jasig
Hi,
I've got two cas servers behind a load balancer, in active/passive mode, doing
SSL offload so that the load balancer uses plaintext 8080 to talk to the cas
servers.
I got cas to listen on port 8080 with this in server.xml:
My cas.properties looks like this:
# Services Management Web UI
Hi
I have finally found the solution why the attribute was not added. The
reason was I forgot to add the allowedAttributes property:
svn diff WEB-INF/deployerConfigContext.xml
Index: WEB-INF/deployerConfigContext.xml
===
--- WEB-INF/
great, thanks
Michael
Am 08.01.14 09:31, schrieb Jérôme LELEU:
> Hi,
>
> Right, it's a bit confusing. I don't think we had a reason.
> It has been fixed in 4.0:
> https://github.com/Jasig/cas/blob/master/cas-server-core/src/main/java/org/jasig/cas/authentication/principal/AbstractWebApplicationSe
Hi,
Right, it's a bit confusing. I don't think we had a reason.
It has been fixed in 4.0:
https://github.com/Jasig/cas/blob/master/cas-server-core/src/main/java/org/jasig/cas/authentication/principal/AbstractWebApplicationService.java#L39
.
Best regards,
Jérôme
2014/1/8 Michael Wechner
> Hi
>
Hi,
You see this message when a CAS logout is performed and when the logout
requests fails to be sent properly to the service [1].
So, in your case, it means that the user has accessed the url :
https://canvas.highline.edu/login/cas and a logout has then been processed.
Best regards,
Jérôme
[1] :