The POST /Security/Claims operation creates a new security claim in Keyfactor Command. On success, the operation returns HTTP 200 OK with the details of the new security claim.
Tip: The following permissions (see Security Roles and Claims) are required to use this feature:
/security/modify/
The user must hold a role containing this permission in the Global Permission Set (see Permission Sets).
Table 750: POST Security Claims Input Parameters
| Name | In | Description |
|---|---|---|
| Description | Body | Required. A string indicating a description for the security claim. |
| Claim Type | Body |
Required. An integer indicating the type of claim. |
| Claim Value | Body | Required. A string containing the identifying information for the entity specified in the claim. For implementations authenticated using Active Directory, this will be in NetBIOS format (DOMAIN\account-name). For example, group KEYEXAMPLE\PKI Administrators or for a computer, machine account KEYEXAMPLE\MyServer$. For implementations authenticated using OAuth, this will be in the format defined by the Name Claim Type. |
| Provider Authentication Scheme | Body | Required. A string indicating the provider authentication scheme (for example, Active Directory or the OAuth authentication scheme name). |
Table 751: POST Security Claims Response Data
| Name | Description |
|---|---|
| Id | An integer containing the Keyfactor Command reference ID for the security claim. |
| Description | A string indicating a description for the security claim. |
| Claim Type |
A string indicating the type of claim. |
| Claim Value | A string containing the identifying information for the entity specified in the claim. For implementations authenticated using Active Directory, this will be in NetBIOS format (DOMAIN\account-name). For example, group KEYEXAMPLE\PKI Administrators or for a computer, machine account KEYEXAMPLE\MyServer$. For implementations authenticated using OAuth, this will be in the format defined by the Name Claim Type. |
| Provider |
An object containing information about the provider assigned to the security claim. |
Tip: See the Keyfactor API
An API is a set of functions to allow creation of applications. Keyfactor offers the Keyfactor API, which allows third-party software to integrate with the advanced certificate enrollment and management features of Keyfactor Command. Reference and Utility, which allows you to call API operations and view results. It is primarily intended for validation, testing, and workflow A workflow is a series of steps necessary to complete a process. In Keyfactor Command, it refers to the workflow builder, which allows you to automate event-driven tasks such as when a certificate is requested, revoked or found in a certificate store. development, and also serves as an interactive supplement to this API documentation. You can access it from the help menu (
) in the Management Portal.
An API is a set of functions to allow creation of applications. Keyfactor offers the Keyfactor API, which allows third-party software to integrate with the advanced certificate enrollment and management features of Keyfactor Command. Reference and Utility, which allows you to call API operations and view results. It is primarily intended for validation, testing, and workflow A workflow is a series of steps necessary to complete a process. In Keyfactor Command, it refers to the workflow builder, which allows you to automate event-driven tasks such as when a certificate is requested, revoked or found in a certificate store. development, and also serves as an interactive supplement to this API documentation. You can access it from the help menu () in the Management Portal.Was this page helpful? Provide Feedback