Page History
...
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 even a tightly integrated application. But to integrate with a third-party authentication process, a custom bridge needs to be created. This bridge will match a user's credentials from a third-party source with those of a user in the Yellowfin system. Usually the authentication source will provide a username, but at times a password and other user attributes are also sent , to authenticate the user.
...
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 which 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 or EXCLUDEUSERFROMGROUP calls can be used to add or remove from groups that determine what which Yellowfin content they can access.
...
- Get details via cookie, file, or network connection.
- Check if the user already exists?
- Creates If user doesn't exist, then create user with the details provided.
- If required, updates update user's details (such as, role, group, etc.)
- Perform a SSO call to log the user in.
...