Checking User Status

CA Strong Authentication uses the user status information before performing some of the credential operations. A user’s status in the database can be either INITIAL, ACTIVE, INACTIVE, or DELETED.
aa821test
2112462
CA Strong Authentication uses the user status information 
before
 performing some of the credential operations. A user’s status in the database can be either INITIAL, ACTIVE, INACTIVE, or DELETED.
For Issuance SDK to perform these checks, you must enable this option when you create configurations using the Administration Console. Refer to the section, "Credential Profiles and Policies" in "Managing Global CA Strong Authentication Configurations" in the
CA Strong Authentication Administration Guide
for more information.
The following table lists all the credential operations and the user checks that are performed depending on the type of operation:
Operation
Checks
User Existence
User Status
User Attribute
Create
Yes
Yes
Yes
Delete
No
No
No
Disable
No
No
No
Enable
Yes
Yes
No
Fetch
No
No
No
Fetch QnA Configuration
No
No
No
Reissue
Yes
Yes
No
Reset
Yes
Yes
No
Reset Custom Attributes
Yes
Yes
No
Reset Validity
Yes
Yes
No
Download Credential
Yes
Yes
No
Delete Unsigned Attributes
No
No
No
Set Unsigned Attributes
No
No
No
Add CA Auth ID Key Bag Elements
No
No
No
Fetch CA Auth ID Key Bag Elements
No
No
No
Delete CA Auth ID Key Bag
Elements
No
No
No