Page History

...

Single Sign-On

Yellowfin's Administration Service allows for integrating Yellowfin with essentially all third-party authentication processes. Primarily an authentication bridge will be used when implementing Yellowfin as a standalone application or when implementing Yellowfin as a tightly integrated application where this is required.

...

The purpose of the Bridge is to match this username with an existing user in Yellowfin and perform a Single-Sign-On (SSO) into Yellowfin as that user. Very rarely there will be a password available from the third-party source. The LOGINUSERNOPASSWORD web service will allow for the Bridge to login log in a user using only their Username. Alternatively, alternatively, LOGINUSER can be used to log the user with a password.

The bridge is not necessarily used to determine whether the user is allowed to loginlog in. The fact that the Bridge receives the username is means that the user has already been validated. However, sometimes the Bridge will be responsible for “asking” the third party if the user is valid.

Sometimes there will be a need to auto-create the users if they do not yet exist in Yellowfin. This might require using additional information to create the user, like email address, first and last name, etc. which should be sourced from the third-party authentication source. The Bridge can use the GETUSER or VALIDATEUSER web service function to determine if a user exists in Yellowfin or not and the ADDUSER web service call to create a user. If bulk user creation option is required, ADDUSERS web service function can be called.

...