Auth integration for 3rd party applications

Third party apps can integrate with BF Launcher via multiple ways to achieve a single sign-on experience. The available options are:

  1. For OIDC providers, SSO via web session cookies using Chrome Custom Tab (CCT) protocol.

  2. MSAL SDK for Entra ID, either session cookies or via brokered authentication in InTune Shared Device mode.

  3. BlueFletch's LauncherProvider SDK — if incorporated within your application, will allow your application to retrieve the currently logged-in user and session/site information.

  4. Intent data or custom URI at Launch — Launcher supports the ability to pass the session information as a URI or intent extras at the time the user launches your application from the home screen.

  5. Enterprise Password Manager (EPM) — can be used if the application is not able to use any of the above methods to auto-fill credentials automatically.

See diagram below for guidance on which integration option to take.

PreviousADFS 3.0/2012 Using ADALNextRelease Notes

Last updated