Page History

Overview

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.

...

Part of the Bridge process may also be to modify the user's Yellowfin role or group membership as part of the login process.   If Yellowfin is integrated with a product where access to different content may change, it may be required to update this group membership during the login process.   This would require sourcing information from the third-party source about what groups a user should be added to/removed from. The UPDATEUSER web service call will allow a user’s role to be modified and the INCLUDEUSERINGROUP / EXCLUDEUSERFROMGROUP web service calls can be used to add/remove from groups that determine what Yellowfin content they can access.

The Bridge can be implemented in many ways. It could be integrated:

• as part of Yellowfin itself (as a JSP, Servlet or Filter within the Yellowfin web application);
• a standalone application (GUI, console or web application) that communicates with the third-party source and Yellowfin;
• Or part of the third-party application itself.

...

Here is an image that describes the basic process of what a Yellowfin Authentication Bridge needs to do:

Image Added

Note. If your authentication provider supports SAML, Yellowfin SAML bridge can be used to SSO users.

Administration API Directory