401 Error Keeps Showing In The Log File When Using HTTP Basic Authentication filter
Last updated on NOVEMBER 01, 2017
Applies to:Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.
In OAG 11.1.2.x, a policy has been set up which contains a HTTP Basic Authentication filter. When using the policy to communicate to a service, for every request a message; 401 "Authentication Required" is seen in the trace log, followed by a " 200 ok " message.
The flow is:
client - > OAG -> service -> OAG -> service
Even though the 401 error is seen, the request still executes and provides the expected results.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms