The orcl* Attributes ( e.g. orclIsEnabled, orclActiveEndDate ) Do Not Affect OAM SSO Federation (SAML) Environment
(Doc ID 2944989.1)
Last updated on APRIL 27, 2023
Applies to:Oracle Access Manager - Version 220.127.116.11.0 and later
Oracle Internet Directory - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
SP side issue. The orcl* attributes ( e.g. orclIsEnabled, orclActiveEndDate ) do not affect OAM SSO Federation (SAML) environment.
Incidentally, the (Doc ID 266709.1) says this functionality ( orclActiveEndDate attribute ) is only available in versions 10gR3 (10.1.4) and higher.
However, actually the orclActiveEndDate is not available for SSO federation.
3. 'User Identity Store' created in step 1 is mapped in the following location.
OAM console > Federation > Service Provider Management > [select any Idps] > Mapping Options > User Mapping > User Identity Store.
4. Check if the SSO federation environment works, you should see the mapped OID user is available to login the OAM managed app.
5. Disable the specific OID account using orclActiveStartDate/orclActiveEndDate or orclIsEnabled attributes.
6. Try to login the SSO app using the account, you should see the account is still available.
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