Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Tuesday, September 13, 2011

GRC An error occurred during the login process

On a freshly installed Oracle EGRC(Enterprise Governance Risk and Compliance) 8.6.3 on OEL 5.6, I got this error in front end:

An error occurred during the login process.

On checking $MW_HOME/grc863/grc/log/grc.log, I found this error:

2011-09-13 14:27:25,529 ERROR [el.Default (self-tuning)'] LoginServiceImpl:233 Error during User Authentication : No Configuration was registered that can handle the configuration named JdbcAuth
java.lang.IllegalArgumentException: No Configuration was registered that can handle the configuration named JdbcAuth
at com.bea.common.security.jdkutils.JAASConfiguration.getAppConfigurationEntry(JAASConfiguration.java:130)
at oracle.apps.grc.security.AuthenticationEnforcer.authenticate(AuthenticationEnforcer.java:77)
at oracle.apps.grc.ui.login.server.LoginServiceImpl.isLogin(LoginServiceImpl.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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 oracle.apps.grc.ui.common.server.context.AACGRemoteServiceServlet.processCall(AACGRemoteServiceServlet.java:73)
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:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.apps.grc.ui.webapp.servlet.ApplicationResourceRequestFilter.doFilter(ApplicationResourceRequestFilter.java:262)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)


I checked startManagedWeblogic.sh script and found that there was a space before jaas.conf

JAVA_OPTIONS="-Xms8192m -Xmx16384m -Xss512k -XX:MaxPermSize=512m -Doracle.security.jps.auth.debug=true -Doracle.security.jps.auth.debug.verbose=true -Djava.security.debug=access,failure -Djava.security.auth.login.config="/GE/erpgrca1/grcapp/weblogic/grc863/grc/WEB-INF/ jaas.config" -Djava.awt.headless=true -Dweblogic.security.SSL.trustedCAKeyStore="/GE/erpgrca1/grcapp/weblogic/wlserver_10.3/server/lib/cacerts" ${JAVA_OPTIONS}"
export JAVA_OPTIONS

I started Weblogic again and a new error showed up in grc.log:

2011-09-13 14:43:05,456 ERROR [el.Default (self-tuning)'] LoginServiceImpl:233 Error during User Authentication : No Configuration was registered that can handle the configuration named JdbcAuth
java.lang.IllegalArgumentException: No Configuration was registered that can handle the configuration named JdbcAuth
at com.bea.common.security.jdkutils.JAASConfiguration.getAppConfigurationEntry(JAASConfiguration.java:130)
at oracle.apps.grc.security.AuthenticationEnforcer.authenticate(AuthenticationEnforcer.java:77)
at oracle.apps.grc.ui.login.server.LoginServiceImpl.isLogin(LoginServiceImpl.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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 oracle.apps.grc.ui.common.server.context.AACGRemoteServiceServlet.processCall(AACGRemoteServiceServlet.java:73)
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:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.apps.grc.ui.webapp.servlet.ApplicationResourceRequestFilter.doFilter(ApplicationResourceRequestFilter.java:262)

I went through the documentation again and realized that I needed to do this:

If you are installing EGRCC to perform analysis in Oracle EBS or PeopleSoft instances:
1. Stop the Administration Server.
2. Open the file StartWebLogic.sh in a text editor. The file resides in the /user_projects/domains//bin directory.
3. Add the following line to the file, replacing with the full path to the grc863 directory you created earlier (see step 5 of ―Preparing Additional Files‖ on page 2-7).

SAVE_JAVA_OPTIONS="-Xms512m -Xmx4096m -Xss512k -XX:MaxPermSize=512m -Doracle.security.jps.auth.debug=true -Doracle.security.jps.auth.debug.verbose=true -Djava.security.debug=access,failure -Djava.security.auth.login.config="/grc/WEB-INF/ jaas.config" -Djava.awt.headless=true -Dweblogic.security.SSL.trustedCAKeystore="/wl server_10.3/server/lib/cacerts" ${JAVA_OPTIONS}"

You may use a maximum memory setting (-Xmx) larger than 4096m if your server has enough memory to support the larger value.
4. Start the Administration Server

Once I did the abve steps, I was able to login to GRC with the default username/password : admin/admin

3 comments:

Mafatlaal said...

Thank you for posting the solution. We are getting the same error, and your solution was very helpful in resolving our issue.

Anonymous said...

Hi
I have same issue and this update I have done also.
But the problem not resolved
I have the same error in grc.log file

Prashanth said...

Thanks for putting up the solution. I had the exact problem and your solution helped me in resolving my issue. Appreciatiate your help...
thanks,
Prashanth