End user

There are multiple ways to login Safewhere*Identify. Exactly how the users of your company are required to login will depend on how your implementation of Safewhere*Identify was configured.
The first page that you will meet, if not being automatically logged in to Safewhere*Identify, will either be the ‘Selector’ page or a ‘Login’ page.

Identify supports multiple logins in the same browser session. In other words, Identify makes it possible for each Relying Party (RP) to login to a different Identify Provider (IdP) without overwriting other existing sessions. In addition, when multiple sessions exist, Identify will pick up the one that has top priority.

For example, if RP1 allows authentication via IdP Auth1, RP2 allows authentication via IdP Auth2, and RP3 allows authentication via both IdPs Auth1 and IdP Auth2. Then RP1 can login to Auth1 in the first tab of the browser, RP2 can login to Auth2 in second tab of the browser and if the user performs login to RP3 in the third tab, it will be authenticated with Auth1.

Test login

Yubico test login page In order to make it easier to test setups with  authentication, the system offers a test mode that will bring up a login screen similar to below: Simply enter the Yubikey. Yubikeys typically have a length […]

Login via Social network

Google login page  supports logging in using Google accounts. Below is an example of how the login page for Google looks.   When logging in for the first time, an additional screen will be shown to require permission from the user […]

Web page to shows all endpoints exposed by Identify

Sometimes, we need to know the endpoints which are supported by Identify, access to your tenant with this URL: https://[tenant_domain]/Runtime/

NemID login page

is a popular authentication method in Denmark, which requires users to insert a unique key. Depending on how the plugin was set up, the log in page will be similar to the figure below   The plugin can also handle […]

Consent page

When a client asks for access to some scopes/protected resource and a user has not been given consent to the scopes yet, he or she will be asked to give consent. The consent module supports the following functionality: Allows a […]

Two-factor Authentication and OTP (One Time Password)

when logging in – a user will be asked to provide additional authentication information. This is known as . is a security process in which the user provides two means of identification. The advantage of is a marked reduction of […]

The LDAP login page

also supports users logging in using accounts. Below is an example of how the log in page for looks.   User also has the ability to change his/her AD password if it is enabled by clicking on the “Reset your […]

The Username and Password login page

The login page that the user will actually see will depend on his chosen authentication method. The above image shows the ‘Username & Password’ connection type. The system also allows us to set up this page to use other types of […]

Selector page

If more than one authentication method () is available, user will need to specify which one he wants to use to log in on the selector page, but only on the first time when user requests access. Upon first time […]