Last updated on MARCH 08, 2017
Applies to:COREid Access - Version 10.1.4.0.1 and later
Information in this document applies to any platform.
Location (IP) can be set in ObUserSession object using setLocation. This modified Location appears to be saved in the ObUserSession and can be retrieved. When IsSetLocationAllowed is false (default), the IP can be set in an ObUserSession user object using setLocation. No error or warning is returned when setLocation is used. This modified Location appears to be saved in the ObUserSession, where it can be retrieved.
It is only when generating a token from the ObUserSession that the set Location is lost. Creating a new ObUserSession from the generated token will have the old Location. Why is this happening?
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