Delinea Platform Configuration
Depending on the credential type that you are validating make sure you are using the appropriate secret template as per the table bellow:
Credential Type | Template Name | Template Type | Note |
---|---|---|---|
Active Directory Account | Active Directory Account | Built-in | Used for domain authentication. |
JDBC | JDBC Credential | Built-in | Used for database connections. |
SNMPv3* | SNMPv3 | Custom |
Requires custom template with SLUGs. |
SSH | Unix Account (SSH) | Built-in | Default SSH password-based login template. |
SSH PrivateKey | SSH Key | Built-in | May appear separately or within Unix Account. |
Windows | Windows Account | Built-in | Available by default in most configurations. |
JMS* | JMS Credential | Custom | For Java Messaging Service access. |
SNMP Community* | SNMP Credential | Custom | Must create custom template manually. |
VMware* | VMware ESX/ESXi | Custom | Credentials used to authenticate and manage VMware's virtualization software running on physical servers |
Kubernetes Credentials * | Kubernetes Credentials | Custom | Used to authenticate and manage access to Kubernetes clusters, typically using tokens. |
Azure Service Principal Servicenow * | Azure Service Principal Servicenow | Custom | Used to authenticate with Azure services via a Service Principal, often for integrations like ServiceNow automation. |
*Creating Custom Templates
* For Azure Service Principal Servicenow, you must create a custom template with the following fields and SLUG mappings:
Field | Slug | Type |
---|---|---|
Tenant ID | tenant-id | Text |
Client ID | client-id | Text |
Secret key | secret-key | Password |
Auth Method | auth-method | Text |
* For JMS and VMware, you must create a custom template with the following fields and SLUG mappings:
Field | Slug | Type |
---|---|---|
Username | username | Text |
Password | password | Password |
* For SNMP Community, you must create a custom template with the following fields and SLUG mappings:
Field | Slug | Type |
---|---|---|
Username | username | Text |
Password | password | Password |
* For Kubernetes Credentials (sn_itom_pattern_kubernetes), you must create a custom template with the following fields and SLUG mappings:
Field | Slug | Type |
---|---|---|
username | username | Text |
password | password | Password |
bearer token | bearer-token | Text |
*For SNMP V3, you must create a custom template with the following fields and SLUG mappings:
Field | Slug |
---|---|
Username | Username |
Authentication protocol | authentication-protocol |
Authentication Key | authentication-key |
Privacy protocol | privacy-protocol |
Privacy key | privacy-key |
Delinea includes both default templates (e.g., Windows, MySQL, SSH) and custom templates for specialized use cases). To learn more about secret templates, go here Built-in Secret Templates.
Once created, the template will appear in the Choose Secret Template dropdown during secret creation.
For full instructions on how to create or edit secret templates, refer to Creating or Editing Secret Templates.
Create a Service User in the Delinea Platform
To create a service account in Delinea Platform, do the following:
-
Log in to the Delinea Platform with admin credentials.
-
Navigate to Access > Users.
-
Select the More dropdown and select the Add service user option on the Users page.
-
In the Add service user page, enter the required details, select Next and then on the Add user to groups page select Add.
-
Go to the Roles tab. Select Assign Roles. The Assign Roles page opens.
-
Select the Platform User role name. Select Assign.
Create a Secret in Delinea Platform
-
Log in to the Delinea Platform.
-
Navigate to Secret Server > All Secrets. The All secrets page opens.
-
Select the Create secret button. The Create new secret page opens.
-
In the Choose a Secret Template box, choose one of the supported secret templates, and then select Create secret.
-
Once the secret is created, go to the Sharing tab of the created Secret, select Edit > Add, and select the previously created service account.