Document toolboxDocument toolbox

(sv) Using Default Login Provider

Owned by Maciej Zabielski
Last updated: Sept 12, 2024
2 min read

Translation needed

The content of this page was copied from another page tree and needs to be translated or updated.

When you finish translation, make sure to

  • Replace the label NEEDS-TRANSLATING with TRANSLATED

  • Remove this macro from the page

 

A default login provider will be used when enters application. If the user is already logged in, a prompt-less login will be performed. 

If a user is not logged in, a login prompt from a specific provider will be shown. 

 

Setting default provider

Go to Identity Providers to find the provider that should be used as a default. 

,

Copy Alias for provider - it will be needed in next step

Go to Authentication section and select Login flows, select a flow that is used for browser login, typically "Browser".

If unsure, check the flow selected in Bindings section for Browser Flow.

 

You should see an optional step for handled by Identity Provider Redirector - select Actions - Config:

On the edit form, set default provider by Alias - paste the name copied from Identity Provider Alias field. 

Bypass default provider

When a default provider is set it will be impossible to login with other providers without using specific link. 

Application will always attempt to authenticate via preset provider. In certain failure scenarios an attempt to fallback to other providers might be made. 

The URL disabling redirect should look like this:

https://test.bim.cloud/client/?idp_hint

 

Note that both /client part is added to base address, as well as ?idp_hint query parameter.

The URL might also include a specific provider. In such case a valis provider alias must be given, e.g.:

https://test.bim.cloud/client/?idp_hint=hyperhouse_adfs

 

This type of URL can also be used if you would like to launch application with a specific provider, even when a default is not set.