Identity Management (MOSC)

MOSC Banner

OAM & OAAM Advanced integration with TAP failed with Error decoding the DAPToken

edited Apr 4, 2019 5:48AM in Identity Management (MOSC) 5 commentsAnswered

Hello everyone,

we have both OAM & OAAM installed on the same weblogic domain and configured with OAM & OAAM advanced integration with TAP.. We are on the 11.1.2.3 with BP 180116 further more we are using taptokenversion 2.0 during the configuration. We have been getting this error for the last three weeks and we have a Sev-1 SR for the last three weeks however we are still not able to resolve the issue.

We actually develop custom code to print out AES cipher key from keystore created during registerThirdPartyTAPPartner and verify that the same key is used in oaam.oam.credential.tapkey.

Have anyone experience something similar.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center