-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: OpenIDM 6.0.0
-
Fix Version/s: OpenIDM 5.5.1.1, 6.0.0.1
-
Component/s: Module - OSGi Container / Framework integration
-
Labels:
-
Target Version/s:
-
Verified Version/s:
From an environment in AWS this stack trace was thrown.
, service.vendor=ForgeRock AS., service.pid=org.forgerock.openidm.authentication, openidm.router.prefix=/authentication, connectionFactory.target=(service.pid=org.forgerock.openidm.router.internal), _rev=000000001d596b92, component.id=9, _id=org.forgerock.openidm.authentication, service.description=OpenIDM Authentication Service} May 24, 2018 9:10:19 PM org.forgerock.openidm.config.logging.LogServiceTracker logEntry SEVERE: Bundle: org.forgerock.openidm.authnfilter [29] [org.forgerock.openidm.authentication(9)] The activate method has thrown an exception java.lang.NullPointerException at org.forgerock.openidm.auth.AuthenticationService.lambda$new$5(AuthenticationService.java:315) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) at java.util.stream.IntPipeline$4$1.accept(IntPipeline.java:250)
Which is caused because the activate method inside of the authentication service attempts to register an identity provider to the identity provider service but the service is not up and ready yet.
The @Reference on the IdentityProviderService is Dyanmic, UNARY_OPTIONAL perhaps it should be required..
- is a backport of
-
OPENIDM-11024 NPE can be thrown if the authentication service comes up before the identityService
-
- Closed
-
- is duplicated by
-
OPENIDM-11531 org.forgerock.openidm.authentication is not activated after upgrade with using AM authentication module.
-
- Closed
-