Hide Forgot
securitylevel_name: Public I was unable to (simply) reference the <Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/> It looks looks like we will have to document creating a new JAAS realm for deploying BRMS on EWS. See the server.log fragment below - is "jmx-console" hard-coded for BRMS? INFO 23-11 15:01:43,227 (SecurityServiceImpl.java:login:78) Logging in user [admin] ERROR 23-11 15:01:43,230 (SecurityServiceImpl.java:login:98) Unable to login. javax.security.auth.login.LoginException: No LoginModules configured for jmx-console at javax.security.auth.login.LoginContext.init(LoginContext.java:273) at javax.security.auth.login.LoginContext.<init>(LoginContext.java:382) at javax.security.auth.login.LoginContext.<init>(LoginContext.java:459) at org.jboss.seam.security.Identity.getLoginContext(Identity.java:406) at org.jboss.seam.security.Identity.authenticate(Identity.java:324) at org.drools.guvnor.server.security.SecurityServiceImpl.login(SecurityServiceImpl.java:96) at org.drools.guvnor.server.SecurityServiceServlet.login(SecurityServiceServlet.java:73) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:562) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:188) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.ContextFilter$1.process(ContextFilter.java:42) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:859) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1555) at java.lang.Thread.run(Thread.java:636)
Link: Added: This issue is related to BRMS-344
There is no JAAS LoginModule defined at all in EWS. You have to follow the tomcat docs on how to define one manually. Otherwise to get this working in /webapp/jboss-brms/WEB-INF/components.xml change the authentication to either: <!-- bypasses security login screen completely --> <security:identity authenticate-method="#{nilAuthenticator.authenticate}"/> OR <!-- default (will take any username, useful if you want to keep track of users but not authenticate <security:identity authenticate-method="#{defaultAuthenticator.authenticate}" />
Don't forget to delete $ews_home/work/Catalina/localhost/jboss-brms/ directory after making changes to components.xml :)
This Jira is specific for $ews_home/tomcat6..for tomcat5 there are more changes needed btw.
Link: Added: This issue depends JBPAPP-5724
See: https://access.redhat.com/kb/docs/DOC-43162
Resolved in KBase article: https://access.redhat.com/kb/docs/DOC-43162