PUMA: Extract SAML Bearer Attributes Within OSB 12c Pipeline Using OWSM Policy
(Doc ID 3070084.1)
Last updated on FEBRUARY 11, 2025
Applies to:
Oracle Web Services Manager - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
While migrating from OSB 11g to 12c. They successfully configured EnterPrise Manager to authenticate and trust SAML Bearer tokens. This setup is allowing virtual users.
In the logs we can see, able to authenticate. Unable to extract SAML Bearer Attributes
weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid:
57e3a75e-6984-4850-ae6d-80c854421b08-0000ce39,0] [APP: Service Bus Kernel]
[partition-name: DOMAIN] [tenant-name: GLOBAL] [FlowId:
0000OPo^xxxxxxx] [oracle.wsm.policy.name:
oracle/wss_saml_token_bearer_service_policy] Virtual user is being propagated
as subject is Subject:[[
Principal: [JpsGenericUserImpl: CN="SSIN=x", OU=xxx-platform
xxxx, OU=NAME, OU="SSIN=x", O=xxxxx Government, C=BE]
Principal: authenticated-role
Private Credential:
Unable to extract SAML Bearer Attributes.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |