Search Results
-
PhenixID web apps authentication – BankID
Updated on: Jun 22, 2020
This authenticator is used to authenticate users with BankID (desktop or mobile BankID). -
PhenixID web apps authentication – Username and password
This authenticator is used for username-password authentication. User stores can be LDAP or SQL. -
PhenixID web apps authentication – Internal Authenticator
This authenticator is used to authenticate users against the PhenixID internal user store (USERS entity in store). This authenticator type is by default used for authentication to Configuration Manager. -
PhenixID web apps authentication – Windows SSO
Updated on: Feb 15, 2021
The purpose of this document is to describe how to configure PhenixID server internal web applications for authentication using Windows SSO (Kerberos or NTLM) authentication. -
PhenixID web apps authentication – SAML SP
Updated on: Nov 03, 2021
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 authentication is performed on an SAML Identity Provider. -
PhenixID web apps authentication and SAML – Selector
This authenticator is used to present authentication options to the end user. -
PhenixID web apps authentication – One Touch
Updated on: Oct 03, 2019
This authenticator is used to authenticate users with PhenixID One Touch -
PhenixID web apps authentication - Freja eID
Updated on: Oct 03, 2019
This document describes how to configure FrejaEIDAuthenticator. A keystore should have been received from Freja eID and imported into PhenixID Server before configuration of the authenticator. Please follow this document to import the keystore. In the example below Freja eID is used to login to myapps. -
PhenixID web apps authentication – Username, password and OTP
This authenticator is used for username-password-otp authentication. -
PhenixID web apps authentication – Header based authentication
This authenticator is used in a scenario where you have another security front end, such as a reverse proxy, that stands in front of PhenixID server. The front end server is also responsible of validating the user. The front end proxy needs to pass the username (or other attribute identifying the user) to the back end server (PhenixID server)