Special Characters Are Encoded Causing OAM 10g Workflow Validation Errors
Last updated on JUNE 07, 2017
Applies to:COREid Identity - Version: 10.1.4.3 to 10.1.4.3
Information in this document applies to any platform.
Oracle Access Manager (OAM) 10.1.4.3 Bundle Patch 8 (BP08) includes the fix for <
After installing BP08 and configuring fields to be excluded from encoding, if an OAM workflow contains mandatory fields and by mistake one of the mandatory fields is not entered then a pop-up warning is shown and all special characters in fields before the missing mandatory field get encoded.
Another symptom of this problem is error "User Password and User Password confirmation do not match" when setting a user password if the password contains a special character (for example an ampersand) and the User Password field is excluded from encoding.
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