This authentication method supports Secure Computing SafeWord hardware tokens, which generates an OTP.
See SafeWord Template for reference.
This authentication method supports RSA SecurID tokens that generate an OTP.
See SecurID Template for reference.
This authentication method performs normal LDAP bind.
See LDAP Template for reference.
The Active Directory authentication method is an LDAP bind authentication method with the possibility to offer the user to change password. This functionality is only supported towards Microsoft Active Directory (AD) servers. The directory service must be configured for SSL communication since this functionality is only allowed over SSL.
The User Certificate authentication method uses user/certificate attribute mapping. If and only if there is an exact, unique match between the configured certificate attribute and the user attribute, the user is authenticated.
See also Manage Certificates
Using a certificate, the client can authorize an order or a document by creating a non-repudiation signature.
The NTLM authentication method is an authentication protocol used in various Microsoft network protocol implementations.
See NTLM Template for reference.
This authentication method performs a basic authentication according to RFC 2617, “HTTP Authentication: Basic and Digest Access Authentication”.
See Basic template for reference.
The general RADIUS authentication method is an authentication protocol that can be used with any RADIUS-compliant authentication server.
The Extended User Bind authentication method adds an extended form of user data retrieval, parsing and matching with user presented certificate and the LDAP user object.
A consortium of Scandinavian banks has agreed on a standard service for electronic authorization and signing over the Internet.
The eID software is Java-based, and no client installations are required.
Using eID, the client can authorize an order or a document by signing.
Swedish BankID, the client can authenticate over the Internet from a mobile phone, tablet or PC with the BankID security application installed and configured.
Swedish Mobile BankID, the client can authenticate over the Internet from a mobile phone or tablet with the BankID security application installed and configured.
The IBM Tivoli authentication method is an LDAP bind authentication method that integrates with the password-policy of IBM Tivoli and enables user to change password. This functionality is only supported towards IBM Tivoli servers. SSL communication is optional. For more information, please refer to the technical note.
The IBM RACF authentication method is an LDAP bind authentication method that enables user to change password when expired. This functionality is only supported towards IBM RACF servers. SSL communication is optional. For more information, please refer to the technical note.
The Novell eDirectory authentication method is an LDAP bind authentication method that enables user to change password. This functionality is only supported towards Novell eDirectory servers. SSL communication is optional. For more information, please refer to the technical note.
Create, or edit existing, HTML forms for authentication. Credentials submitted to the Access Point are then, for example, posted to a Web server (configured as the authentication method server). When the credentials are accepted by the Web server, users are authenticated and allowed access by the Access Point.
Windows Integrated Login authentication enables Windows domain credentials to be reused.
For example, users do not have to log on to the Portal when it is protected by Windows Integrated Login authentication. User credentials are retrieved from the client, and not entered by the user.
The Tupas identification service allows businesses and corporations that provide electronic business services to identify their customers using Tupas certificates. See Tupas for reference.
Norwegian Bank ID (NBID) authentication enables users to authenticate via the Norwegian Bank ID services. See NBID for reference.
Nexus Go authentication enables users to authenticate via the Nexus Go services. See Nexus Go for reference.
Freja eID authentication enables users to authenticate via the Freja eID services. See Freja eID for reference.
OpenID Connect authentication enables users to authenticate via the Authentication Code Based authorization of any OpenID Connect Provider. See OpenID Connect for reference.
With a custom-defined authentication method, you can define an arbitrary number of additional extended properties.