Our CAS installation is sat in front of multiple services (current count of 
about 50) and the users who authenticate may not be able to access all of 
them.

We have used the attribute merging to make a rest call to populate an 
attributes with a list of valid services for a given user but I'm not 
struggling to figure out how to enforce it.

I thought I could define a GroovyAuthenticationHandler and get the script 
to check and also define a Required policy (that required the 
GroovyAuthenticationHandler) but I can't get it to trigger (or even notice 
that I've attempted to define it!).

Also I don't think the Groovy script gets passed into it the service, so I 
suspect we can't even check whether the service is valid for the attribute?

Does anyone have any examples of how to define the 
GroovyAuthenticationHandler and/or the Required handler to point us in the 
right direction?

I also thought about defining RequiredAttributes in the service - but 
whilst I can validate that our "userServices" attribute is present, I need 
to know whether it has a value (and ideally a specific entry in a list).  
Also having to define that for each and every service seems rather 
time-consuming?

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/d7a200ec-2b1b-4c65-bde0-98fc031d8b8an%40apereo.org.

Reply via email to