The Internal Flow Option Was Deprecated In OAG 18.104.22.168.0
Last updated on JANUARY 27, 2017
Applies to:Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.
In OAG 22.214.171.124.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 126.96.36.199 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 188.8.131.52.0 as was seen in 184.108.40.206.0?
"user_id" : "cn=21981131479,dc=user,dc=corporate,cn=users,dc=tim,dc=com,dc=br",
"user_id" : "21981131479"
Steps required to reproduce the problem:
220.127.116.11 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 18.104.22.168 upgrade
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