Search Results
-
SAML Scope and Scoped Attributes
Updated on: Aug 24, 2023
This document describes how to declare a scope for your SAML IdP and how to enable attribute scoping, as well as general information about how SAML SP will interpret scoped attributes. Requires PAS 4.7 or higher.
-
SAML SP metadata upload
Updated on: Aug 24, 2023
In oder getting PhenixID server act as an IDP trust needs to be established with the SAML Service provider, SP. This is done by uploading the SP's metadata. Metadata can either be consumed as a static file or from an URL. When retrieved from an URL caching and reloading is handled by the system based on the SAML standard. When using a static file updates of the metadata must be handled manually.
-
SAML SP metadata upload
Updated on: May 26, 2021
In oder getting PhenixID server act as an IDP trust needs to be established with the SAML Service provider, SP. This is done by uploading the SP's metadata. Metadata can either be consumed as a static file or from an URL. When retrieved from an URL caching and reloading is handled by the system based on the SAML standard. When using a static file updates of the metadata must be handled manually.
-
SAML SP metadata upload
Updated on: Jan 17, 2022
In oder getting PhenixID server act as an IDP trust needs to be established with the SAML Service provider, SP. This is done by uploading the SP's metadata. Metadata can either be consumed as a static file or from an URL. When retrieved from an URL caching and reloading is handled by the system based on the SAML standard. When using a static file updates of the metadata must be handled manually.
-
SAML SP metadata upload
Updated on: Sep 21, 2022
In oder getting PhenixID server act as an IDP trust needs to be established with the SAML Service provider, SP. This is done by uploading the SP's metadata. Metadata can either be consumed as a static file or from an URL. When retrieved from an URL caching and reloading is handled by the system based on the SAML standard. When using a static file updates of the metadata must be handled manually.
-
SAML SP metadata upload
Updated on: Nov 25, 2021
In order getting PhenixID server act as an IDP trust needs to be established with the SAML Service provider, SP. This is done by uploading the SP's metadata. Metadata can either be consumed as a static file or from an URL. When retrieved from an URL caching and reloading is handled by the system based on the SAML standard. When using a static file updates of the metadata must be handled manually.
-
SAML SP metadata upload
Updated on: Dec 22, 2023
In oder getting PhenixID server act as an IDP trust needs to be established with the SAML Service provider, SP. This is done by uploading the SP's metadata. Metadata can either be consumed as a static file or from an URL. When retrieved from an URL caching and reloading is handled by the system based on the SAML standard. When using a static file updates of the metadata must be handled manually.
-
SAML SP metadata upload
Updated on: Mar 20, 2024
In oder getting PhenixID server act as an IDP trust needs to be established with the SAML Service provider, SP. This is done by uploading the SP's metadata. Metadata can either be consumed as a static file or from an URL. When retrieved from an URL caching and reloading is handled by the system based on the SAML standard. When using a static file updates of the metadata must be handled manually.
-
SAML Username, Password & SMS
Updated on: Mar 20, 2024
Performing this scenario will produce a SAML IDP with Username, Password & second factor (via text message sent to users mobile phone) authentication 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 requirement is also a message gateway account with PhenixID message gateway.
This article will use LDAP as the primary user store.
-
SAML Username, Password and token
Updated on: Mar 20, 2024
Performing this scenario will produce a SAML IDP with Username, Password and MFA through a token. 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 soft tokens such as PhenixID Pocket pass.
This article will use LDAP as the primary user store.