Search Results
-
Configuration of SAML ticket for solicitor role
Updated on: Dec 08, 2023
This document describes how to configure the authority attribute to define the user role in Signing Workflow.
Signing Workflow has one role called solicitor. The solicitor role is allowed to create new Signing Workflow errands and assign the errand to multiple requested signers.
Non-solicitors are able to login to Signing Workflow. They will only see the Signing Workflow errands where they are part of the list of requested signers.
-
SAML Identity Provider (internal or external)
Updated on: May 26, 2021
Performing this scenario will produce an OpenID Connect Provider, relaying the authorization step to a SAML Identity Provider. PhenixID will act as a SAML Service Provider against the IdP.
Be sure to have configured "Relying party", "Keystore" and "Identity Provider" scenarios prior to executing this scenario.
The "Keystore" scenario can be found under the FEDERATION tab.
The "Identity Provider" scenario can be found under the FEDERATION - SAML metadata upload tab.
-
SAML Identity Provider (internal or external)
Updated on: Jan 17, 2022
Performing this scenario will produce an OpenID Connect Provider, relaying the authorization step to a SAML Identity Provider. PhenixID will act as a SAML Service Provider against the IdP.
Be sure to have configured "Relying party", "Keystore" and "Identity Provider" scenarios prior to executing this scenario.
The "Keystore" scenario can be found under the FEDERATION tab.
The "Identity Provider" scenario can be found under the FEDERATION - SAML metadata upload tab.
-
SAML Identity Provider (internal or external)
Updated on: Sep 21, 2022
Performing this scenario will produce an OpenID Connect Provider, relaying the authorization step to a SAML Identity Provider. PhenixID will act as a SAML Service Provider against the IdP.
Be sure to have configured "Relying party", "Keystore" and "Identity Provider" scenarios prior to executing this scenario.
The "Keystore" scenario can be found under the FEDERATION tab.
The "Identity Provider" scenario can be found under the FEDERATION - SAML metadata upload tab.
-
SAML Identity Provider (internal or external)
Updated on: Sep 01, 2021
Performing this scenario will produce an OpenID Connect Provider, relaying the authorization step to a SAML Identity Provider. PhenixID will act as a SAML Service Provider against the IdP.
Be sure to have configured "Relying party", "Keystore" and "Identity Provider" scenarios prior to executing this scenario.
The "Keystore" scenario can be found under the FEDERATION tab.
The "Identity Provider" scenario can be found under the FEDERATION - SAML metadata upload tab.
-
Configuration of SAML ticket for solicitor role
Updated on: Jun 15, 2022
This document describes how to configure the authority attribute to define the user role in Signing Workflow.
Signing Workflow has one role called solicitor. The solicitor role is allowed to create new Signing Workflow errands and assign the errand to multiple requested signers.
Non-solicitors are able to login to Signing Workflow. They will only see the Signing Workflow errands where they are part of the list of requested signers.
-
Configuration of SAML ticket for solicitor role
Updated on: Mar 07, 2022
This document describes how to configure the authority attribute to define the user role in Signing Workflow.
Signing Workflow has one role called solicitor. The solicitor role is allowed to create new Signing Workflow errands and assign the errand to multiple requested signers.
Non-solicitors are able to login to Signing Workflow. They will only see the Signing Workflow errands where they are part of the list of requested signers.
-
Configuration of SAML ticket for solicitor role
Updated on: Sep 26, 2022
This document describes how to configure the authority attribute to define the user role in Signing Workflow.
Signing Workflow has one role called solicitor. The solicitor role is allowed to create new Signing Workflow errands and assign the errand to multiple requested signers.
Non-solicitors are able to login to Signing Workflow. They will only see the Signing Workflow errands where they are part of the list of requested signers.
-
SAML Identity Provider (internal or external)
Updated on: Dec 22, 2023
Performing this scenario will produce an OpenID Connect Provider, relaying the authorization step to a SAML Identity Provider. PhenixID will act as a SAML Service Provider against the IdP.
Be sure to have configured "Relying party", "Keystore" and "Identity Provider" scenarios prior to executing this scenario.
The "Keystore" scenario can be found under the FEDERATION tab.
The "Identity Provider" scenario can be found under the FEDERATION - SAML metadata upload tab.
-
SAML Username, Password and One Touch
Updated on: Mar 20, 2024
Performing this scenario will produce a SAML IDP with Username, Password and MFA through PhenixID One Touch. Authentication is done using either Active Directory, LDAP or SQL database as the primary userstore. Be sure to have configured "Keystore" & "SAML meta upload" scenarios prior to executing this scenario. A good idea is to enable either MFA admin or Selfservice for activating PhenixID One Touch tokens.
This article will use LDAP as the primary user store.