Security Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

OAM error in communication with OAAM

KaialMar 30 2016 — edited Mar 30 2016

Hi all,

I was trying to protect an application with TAPScheme, but when i test the URL, the OAM error page is displayed. I get the following error in OAM´s log:

[2016-03-30T15:17:38.780-03:00] [oam_server1] [ERROR] [OAM-00009] [oracle.oam.binding] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 005BoWd4ZhYC^qM5mN0FyZ0000tY00004f,0:1] [APP: oam_server#11.1.2.0.0] [DSID: 0000LF8jdAq7q2MLmM_AiZ1Mz0vw000007] Unable to parse the redirection URL

[2016-03-30T15:17:38.781-03:00] [oam_server1] [ERROR] [OAM-00002] [oracle.oam.binding] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 005BoWd4ZhYC^qM5mN0FyZ0000tY00004f,0:1] [APP: oam_server#11.1.2.0.0] [DSID: 0000LF8jdAq7q2MLmM_AiZ1Mz0vw000007] Error occurred while handling the request.[[

oracle.security.am.common.utilities.exception.AmRuntimeException: OAM-00009

at oracle.security.am.pbl.protocol.plugin.credcollect.DefaultRedirectionStrategy.constructRedirectUrl(DefaultRedirectionStrategy.java:421)

at oracle.security.am.pbl.protocol.plugin.credcollect.DefaultRedirectionStrategy.getRedirectUrl(DefaultRedirectionStrategy.java:355)

at oracle.security.am.pbl.protocol.plugin.credcollect.DefaultCredCollectResponseExecutor.process(DefaultCredCollectResponseExecutor.java:127)

at oracle.security.am.pbl.protocol.plugin.credcollect.CredentialCollectionResponseHandler.process(CredentialCollectionResponseHandler.java:99)

Caused by: java.net.MalformedURLException: Stream handler unavailable due to: For input string: "10201https:"

at java.net.URL.<init>(URL.java:623)

Caused by: java.lang.IllegalStateException: Stream handler unavailable due to: For input string: "10201https:"

at org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:431)

I think that the communication configuration between OAM and OAAM is incorrect. Do you guys have any solutions to this problem? If there is an tutorial showing how to configure this, it would be great.

Thanks for the help.

Locked Post

New comments cannot be posted to this locked post.

Locked on Apr 27 2016

Added on Mar 30 2016

#identity-management, #identity-manager

1 comment

737 views