The Internal Flow Option Was Deprecated In OAG 22.214.171.124.0
(Doc ID 2224876.1)
Last updated on AUGUST 05, 2019
Applies to:Oracle API Gateway - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
In OAG 188.8.131.52.0 the "Authorization Code Flow" filter can be used in the "Authorize Transaction" filter when "Use internal flow" is selected. When using the internal flow after user registration for the application, using an HTML form and OVD LDAP, OAG extracts the "username" only. In the same filter, the OAG 184.108.40.206 version uses the subject.id field and this returns the full DN of that user.
How is it possible to get the same result in 220.127.116.11.0 as was seen in 18.104.22.168.0?
"user_id" : "cn=<COMMON NAME>,dc=<DOMAIN COMPONENT>,dc=<DOMAIN COMPONENT>,cn=users,dc=<DOMAIN COMPONENT>,dc=<DOMAIN COMPONENT>,dc=<DOMAIN COMPONENT>",
"user_id" : "<COMMON NAME>"
Steps required to reproduce the problem:
22.214.171.124 Authorize Resource Owner:
Select one of the following:
Use internal flow
This uses the internal API Gateway flow to authorize the Resource Owner. This is the default setting.
Note: Previous versions of the API Gateway enabled a user to call a policy to authorize the resource owner, and store the subject in a message attribute. This field is used to provide backwards compatibility with configurations using that option. If an authenticated user is not found in the message, the filter automatically uses the internal flow and returns the specified login form.
### Recent changes to the environment ###
OAG 126.96.36.199 upgrade
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