FrejaEIDInternalAuthenticator
Used acting authenticating to server-internal resources.
Support "on same device" through app switching and "on other device" through QR code.
Only QR-code is available when using other device. No user input required by the user. On the same device (mobile client) the pattern of "app switching" is used.
Read more about Freja eID and integration here:
https://frejaeid.com/rest-api/Authentication%20Service.html
and here regarding authentication:
https://frejaeid.com/rest-api/Authentication%20Service.html#AuthenticationService-Methods
The authenticator only handles Swedish and English localisation.
This will deprecate the FrejaEIDAuthenticator authenticator.
Properties
Example configuration
{ "id": "freja", "alias": "freja", "name": "FrejaEIDInternalAuthenticator", "displayName": "Freja", "configuration": { "pipeID": "64452300-d25d-45ae-bd7a-a6cfb7f0e5e0", "idpID": "da35b801-9894-45b9-9d97-98c336ead5f0", "keystoreId": "c5e0b707-a297-420e-a741-08d3e25df1be", "mode": "test_personal", "successURL":"/ppss" "attributesToGet": "EMAIL_ADDRESS,SSN" } }
Additional information
Only some of the information returned from Freja eID is available to the pipe when executing.
If returned from Freja eID, the attributes are:
- documentType
- documentExpirationDate
- documentCountry
- documentSerialNumber
- registrationLevel
- photo
- userPersonalNumber
- userGivenName
- userSurName
- primaryMail
- organisationIdIdentifier
The executing PIPE MUST return an item property named userName. It will be used as user identifier for the current session.
It may NOT be empty.
Requirements
A keystore with a valid certificate is uploaded to the PAS server.
User enrolled for freja e-id.
Trusting the Freja backend HTTPS/TLS. This is not done by default.