[cas-user] CAS 6.1.5 - Exception in log after Service Access Enforcement

[Sven Specker]

Hi!








Any hints?

Best regards,

Sven Specker
--
__________________________________________________________________
*** Sven Specker -- University of Frankfurt Computing Center   ***
*********** UNIX System Administration (Auth/IDM) ****************
***** spec...@rz.uni-frankfurt.de [Phone (+49)-69-798-15188] *****
******************************************************************
__________________________________________________________________              
                Johann Wolfgang Goethe Universitaet
                   - Hochschulrechenzentrum -
                 Theodor W. Adorno-Platz 1 (PA-1P16)

                   D-60323 Frankfurt/Main
__________________________________________________________________
______________ TeX-users do it in {groups}________________________

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG

To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/c8f428fe-9b82-1400-b0a1-d2a7c0cc6da2%40rz.uni-frankfurt.de.

I do not know if I misconfigured something, but if a user runs afoul of an access strategy, i get a stack trace ERROR [org.apereo.cas.web.flow.login.CreateTicketGrantingTicketAction] - <screen.service.error.message> org.apereo.cas.authentication.PrincipalException: screen.service.error.message I do not mind, since it works but it makes the log messy. Have not found any option to prevent that particular effect. --- You received this message because you are subscribed to the Google Groups "CAS Community" group.

smime.p7s
Description: S/MIME Cryptographic Signature