The property AuthorizationManager is null exceptions and NPE on SimpleSecurityManager when connecting firstly from a remote client ---------------------------------------------------------------------------------------------------------------------------------- Key: WFLY-904 URL: https://issues.jboss.org/browse/WFLY-904 Project: WildFly Issue Type: Bug Components: Security Environment: Eclipse Juno SR2 with JBoss Tools, Mac OS X, Sun JDK 6 Reporter: Fernando Nasser Assignee: Darran Lofthouse Labels: eap6, investigation_required Fix For: 9.0.0.CR1 Attachments: NPEinSimpleSecurityManager, PBOX000075, QSecuredEJB.jar, QSecuredEJB.zip, SecurityRelatedSettings Description of problem: If one tries and use security enabled EJBs from a remote client (authenticated connection) before connecting first from a servlet both a Server NPE and an erroneous exception are thrown. However, if one uses some servlet-based authentication first, the missing field is "primed" and from that point on the remote application can use the secure EJBs normally, proper Role authorization is checked and enforced etc. With absolutely no changes in configuration, code (incl. annotation) whatsoever. Any number of remote client connections will succeed until you restart the server. Then the errors are back, until you "prime" the Server by connecting using a Servlet. More complete data is attached, but here are some info: NPE is thrown at: org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:394) Bean method invocation fails with exceptions containing the message: JBAS011048: Failed to construct component instance I am using the "other" security context for testing. I am running the Server in standalone mode. When I say remote I mean not in the Server, but I am running my client from localhost. Version-Release number of selected component (if applicable): Seen on EAP 6.1.0 alpha (apparently present on AS 7.1.1 as well).