SAML Authentication Properties
The following properties are available for SAML Authentication objects, grouped by the categories shown in the authentication service editors.
Behavior
| Property | Type | Default | Description |
|---|---|---|---|
bool |
false |
Whether to turn on additional debug logging on the server’s Java SAML library. |
|
bool |
false |
Whether the service provider should sign authentication requests to the identity provider. |
|
bool |
false |
Whether the server should reject unsigned or unencrypted messages. |
|
bool |
false |
Whether the service provider wants assertions from the identity provider signed. |
Configuration
| Property | Type | Default | Description |
|---|---|---|---|
string |
A unique value shared between the Service Provider (Dodeca) and Identity Provider (JumpCloud, Okta) which is used to establish two-way trust. |
||
string |
The Identity Provider (JumpCloud, Okta) endpoint that receives single sign-on authentication requests for launch via the Service Provider (Dodeca). |
||
string |
The public key of Identity Provider (JumpCloud, Okta) that is used by the Service Provider (Dodeca) to verify assertions and responses. |
||
string |
The service provider endpoint which is redirected to after the Identity Provider authenticates the user. |
||
string |
The unique service provider entity identifier that must be shared between the Service Provider (Dodeca) and Identity Provider (JumpCloud, Okta). |
||
string |
The service provider endpoint which is accessed when the Identity Provider logs out the user. |
||
string |
The assertion attribute whose value becomes the authenticated username. A blank value uses the SAML NameID; a login fails when the configured attribute is not present in the assertion. This is resolved on every login under every PrincipalResolutionPolicy, including Principal, so a missing attribute fails login even for an already fully-provisioned user. |