OWSM Oracle/http_jwt_token_service_policy Doesnt Work When Attached To OSB Proxy Service
(Doc ID 2390815.1)
Last updated on AUGUST 12, 2024
Applies to:
Oracle Service Bus - Version 12.2.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
OWSM oracle/http_jwt_token_service_policy not working when attached to a OSB Proxy Service
Error seen in the logs:
[oracle.wsm.security.policy.scenario.executor.HttpJwtSecurityScenarioExecutor][tid: [ACTIVE].ExecuteThread: '33' for queue: 'weblogic.kernel.Default(self-tuning)'] [userId: <anonymous>] [ecid:7dxb,0] [APP: Service Bus Kernel][partition-name: DOMAIN] [tenant-name: GLOBAL] [FlowId:000x007] [oracle.wsm.policy.name:oracle/http_jwt_token_service_policy] [SRC_CLASS:oracle.wsm.security.policy.scenario.executor.HttpJwtSecurityScenarioExecutor][SRC_METHOD: authenticate] The Http Authorization header is :- null[2018-02-05T20:48:17.829-08:00] [soa_server1] [NOTIFICATION] [WSM-00327][oracle.wsm.resources.security] [tid: [ACTIVE].ExecuteThread: '33' for queue:'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid:x5b,0] [APP: Service Bus Kernel][partition-name: DOMAIN] [tenant-name: GLOBAL] [FlowId:000x00007] [oracle.wsm.policy.name:oracle/http_jwt_token_service_policy] Incoming request did not have a valid authentication token. Service will send a 401 Challenge in response to the client with WWW-Authenticate header.
Changes
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 |
Changes |
Cause |
Solution |
References |