ECO3: OID - Custom Attribute With Integer Type Still Allows Non Numerical Characters
(Doc ID 1636655.1)
Last updated on FEBRUARY 27, 2019
Applies to:
Oracle Internet Directory - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
OID 11.1.1.7
Symptoms
When creating a custom attribute of the Integer type, the attribute value can still hold non alpha-numeric characters.
Example:
Create a custom attribute like the following:
dn: cn=subschemasubentry
changetype: modify
add: attributetypes
attributetypes: ( 99.99.99.99.99.99.99.0 NAME 'oscarID' DESC 'oscarID' EQUALITY integerMatch SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' SINGLE-VALUE )
Add the attribute to an objectclass (existing or custom)
Add the objectclass to a user
Add value to the custom attribute for the user.
You will find the attribute accepts both Numeric and alpha-numeric values.
Cause
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
Symptoms |
Cause |
Solution |
References |