Martin,
Looking on github, the current 5.3.x version id 5.3.9 from 04 March.
Ray
On Sat, 2019-05-11 at 06:12 -0700, Martin Böhmer wrote:
I can reproduce the following NPE when logging into Service A via CAS and then
trying to access Service B by calling B's URL.
2019-05-10 22:50:34,980 WARN
[org.apereo.cas.web.flow.resolver.impl.InitialAuthenticationAttemptWebflowEventResolver]
- <null>
java.lang.NullPointerException: null
at
org.apereo.cas.web.flow.resolver.impl.InitialAuthenticationAttemptWebflowEventResolver.determineRegisteredServiceForEvent(InitialAuthenticationAttemptWebflowEventResolver.java:126)
~[cas-server-core-webflow-api-5.3.10.jar:5.3.10]
at
org.apereo.cas.web.flow.resolver.impl.InitialAuthenticationAttemptWebflowEventResolver.resolveInternal(InitialAuthenticationAttemptWebflowEventResolver.java:86)
~[cas-server-core-webflow-api-5.3.10.jar:5.3.10]
at
org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver.resolve(AbstractCasWebflowEventResolver.java:410)
~[cas-server-core-webflow-api-5.3.10.jar:5.3.10]
at
org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver.resolveSingle(AbstractCasWebflowEventResolver.java:415)
~[cas-server-core-webflow-api-5.3.10.jar:5.3.10]
The NPE refers to this
line<https://github.com/apereo/cas/blob/8c97a6a1556337a6c8f58b943ff81baeb3ca01f4/core/cas-server-core-webflow-api/src/main/java/org/apereo/cas/web/flow/resolver/impl/InitialAuthenticationAttemptWebflowEventResolver.java#L126>:
LOGGER.debug("Enforcing access strategy policies for registered service [{}]
and principal [{}]", registeredService, authn.getPrincipal());
The only thing to cause an NPE here could be authn.getPrincipal() when the
authn Object is null.
So, what is wrong here?
a) should there be a check for authn == NULL or
b) is this case not supposed to happen and there is something wrong with my CAS
configuration
The error I experience may point to a problem somewhere else in CAS 5.3.10.
Before I deployed the release version I ran a snapshot version from April 1st
2019. With that snapshot version, the error does not occur.
So, a change made between April 1st (date of my working snapshot) and April
19th (release date) must somehow cause the malfunction.
Any clues on how to fix this would be greatly appreciated.
Regards,
Martin
--
Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | [email protected]
--
- 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/dead57c5d4aa6ead3cec55b3da68a1abd66c66cf.camel%40uvic.ca.
