Internal Plugins Not Launching From Within P6 Professional When Configured for Cloud Connect and SAML/SSO. Claim Digger Log Generates Error "com.primavera.common.exceptions.InvalidCredentialsException: Invalid user name and/or password" (Doc ID 2205513.1)

Last updated on NOVEMBER 22, 2016

Applies to:

Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 15.2.0.0 to 15.2.0.0 [Release 15.2]
Primavera P6 Enterprise Project Portfolio Management - Version 15.2.0.0 to 15.2.0.0 [Release 15.2]
Information in this document applies to any platform.

Symptoms

When P6 Professional is configured for a) Cloud Connect, b) SAML/SSO Authentication using the Remote Mode API for Internal Plugin applications, an attempt to launch Claim Digger from within P6 Professional, results in a generic login window, preventing the application from launching.

In the Claim Digger log file ($P6Professional_WorkingDirectory\EPPM\Java\logs\Claim Digger.log), the following error occurs:

ERROR

com.primavera.common.exceptions.InvalidCredentialsException: Invalid user name and/or password.
at com.primavera.bo.common.a.a(LoginHelper.java:291)
at com.primavera.bo.common.a.a(LoginHelper.java:176)
at com.primavera.bo.remotable.SessionLifetime.login(SessionLifetime.java:57)
at sun.reflect.GeneratedMethodAccessor954.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.primavera.infr.q.AbstractQProxyObject.performAction(AbstractQProxyObject.java:492)
at com.primavera.infr.q.AbstractQProxyObject.execute(AbstractQProxyObject.java:547)
at com.primavera.integration.web.APIAppsServlet.service(APIAppsServlet.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:346)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3432)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3402)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2285)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2201)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1572)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:255)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure P6 EPPM with Cloud Connect and Remote Mode API deployment.
2. Configure P6 EPPM for SSO.
3. Configure P6 Professional for Cloud Connect & SAML/SSO.
4. Configure P6 applications settings for Internal Plugins with Remote Mode API URL.
5. Login to P6 Professional using cloud connect with SSO/SAML.
6. Select Tools, Claim Digger.
7. Note the issue which occurs.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms