About the configOAMLoginPagePref feature ? And How to interpret the OAM_LANG_PREF Cookie and How to Decode it ?
(Doc ID 1574518.1)
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
In OAM R2 PS1 (release of 184.108.40.206.0), there is the new feature for configuring the Access Manager Login Page User Preferences as documented at:
While one can expect the "ConfigOAMLoginPagePref" parameter to be configured as a non-english language.
But after login to oamconsole, the webpage language is still and will remain in English.
This can be strange to end users, But it is actually the expected behavior, and that is how it works and should work.
In fact, the configOAMLoginPagePref is there only to configure the Access Manager LOGIN PAGE user preferences.
The oamconsole application has its own rules for language preference, and so there is NO reason to believe it (the configOAMLoginPagePref feature) would affect the behaviour of the oamconsole.
It's just a login page - and so no ones would expect it to change the language preference of any other application.
The feature is provided to allow the customer to "force" the language of the login page .... the idea is that the behaviour will be consistent, rather than OAM picking up language from browser, OS or whateve.
Now, after clarifying on the real purpose of this command and what it really does and how it is expected to work, one might be interested to know further on it, as for example on :
1) How to use/interpret the cookie of oam_lang_pref for instance ?
2) As the value of this cookie is being encrypted, so then How can we to decode it to see its content ?
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