The purpose of this document is to describe how to configure PhenixID server internal web applications for authentication using SAML Service Provider Authentication. This is used when the user...
Used when internal applications should be a part of a SAML federation.
Properties
Name
Description
Default value
Mandatory
sp
The entity ID of the Service provider. Must be same value as entityID....
Used when internal applications should be a part of a SAML federation.
Properties
Name
Description
Default value
Mandatory
sp
The entity ID of the Service provider. Must be same value as entityID....
Used when internal applications should be a part of a SAML federation.
Properties
Name
Description
Default value
Mandatory
sp
The entity ID of the Service provider. Must be same value as entityID....
Prerequisite is a pkcs12 file containing a single keypair. The p12 file must contain a friendly name and the keypair must have an alias value set.
Start by clicking the plus sign. A new view will...
Prerequisite is a pkcs12 file containing a single keypair. The p12 file must contain a friendly name and the keypair must have an alias value set.
Start by clicking the plus sign. A new view will...
Prerequisite is a pkcs12 file containing a single keypair. The p12 file must contain a friendly name and the keypair must have an alias value set.
Start by clicking the plus sign. A new view will...
Performing this scenario will produce a SAML IdP that can be used for user authentication. Be sure to have configured "Keystore" & "SAML meta upload" scenarios, as well as...
Performing this scenario will produce a SAML IDP with Username & Password authentication using either Active Directory, LDAP or SQL database as the primary userstore. Be sure to have configured...
Performing this scenario will produce a SAML IDP using the PhenixID One Touch token as primary identification mechanism.
No user input is required. Identification is done through either QR code...