# 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.

<figure><img src="/files/X9oyYaNS4ExsIzT7DNYq" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/authentication-and-sso/technical-guide/auth-integration-for-3rd-party-applications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.