POST Security Identities
The POST /Security/Identities method is used to create a new security identity in Keyfactor Command. For Active Directory, use the GET /Security/Identities/Lookup method (see GET Security Identities Lookup) before creating the new identity to confirm that the identity you plan to create is valid. This method returns HTTP 200 OK on a success with the details of the new security identity.
The user must hold a role containing this permission in the Global Permission Set (see Permission Sets).
Table 646: POST Security Identities Input Parameters
| Name | In | Description |
|---|---|---|
| AccountName | Body | Required. A string containing the account name for the security identity. For Active Directory user and groups, this will be in the form DOMAIN\\user or group name. For example: KEYEXAMPLE\\PKI Administrators |
Table 647: POST Security Identities Response Data
| Name | Description |
|---|---|
| Id | An integer containing the Keyfactor Command identifier for the security identity. |
| AccountName | A string containing the account name for the security identity. For Active Directory user and groups, this will be in the form DOMAIN\\user or group name. For example: KEYEXAMPLE\\PKI Administrators |
| IdentityType | A string indicating the type of identity—User or Group. |
| Roles |
An array of objects containing information about the security roles assigned to the security identity. For new security identities, this will be blank. |
| Valid | A Boolean that indicates whether the security identity's audit XML is valid (true) or not (false). A security identity may become invalid if Keyfactor Command determines that it appears to have been tampered with. |