Last updated on SEPTEMBER 02, 2016
Applies to:Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.
When HTTP BASIC authentication credentials are passed to an inbound call on Oracle API Gateway (OAG), the values cannot be stored in local variables to be used for other purposes.
A simplified example of what is to be accomplished is to use a policy that accepts an HTTP BASIC authentication header to an endpoint and displays the username and password before performing a local store lookup and after.
It is observed that before the HTTP Basic lookup, the attributes 'authentication.subject.id' and 'authentication.subject.password' are not populated, nor is any attribute that would contain the desired values.
By using the HTTP BASIC Authentication filter against the local store, the two attributes become populated.
The desire is to not have to check against the local store since the requirement is to perform a callout to a REST API which will authenticate the user itself.
To do this, attributes need to be populated with the username and password values that can then be made available to the callout.
How can this functionality be achieved?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms