> For the complete documentation index, see [llms.txt](https://patterns.opendialog.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://patterns.opendialog.ai/the-pattern-library/authentication/components.md). # Components ### User authentication status * User is authenticated, accomplished behind the scenes via an integration (an action, not an intent) * User is authenticated, just tried to authenticate conversationally and succeeded * User is not authenticated and confronts an authentication trigger * User is not authenticated, just tried to authenticate conversationally and failed ### Triggers for authentication * Whole experience requires authentication, so this is triggered at the start of the interaction. * Just-in-time authentication trigger examples * Entering secure chat * Asking for protected info * Initiating a transaction * Checking balances/due dates/credits ### Authentication conversation * Explanation to user for why they need to authenticate * Options if the user doesn’t want to authenticate. * Exit * Subset: only offer an experience not requiring authentication * Repair * Persuade: try to convince them it is worth authenticating * Authentication procedure * Collect user info conversationally (e.g. username and password) * ​​If no account, then register * Link to external authentication page * Secret questions * Voice biometrics * Optional: Explanation of authentication success or failure ### Embedded authentications (aka double authentication) * You might authenticate at multiple levels. For example, a user could authenticate with the Alexa service, and then also authenticate with a skill within the Alexa service. A CapitalOne banking skill within Alexa might need to do this. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://patterns.opendialog.ai/the-pattern-library/authentication/components.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.