# Use Cases ## Login to a web application When authenticating end-users for the purpose of login, the users are asked to present specific verifiable credentials instead of a standard username and password. For that the web application must: * Set up a verifier account and enable SSO. * In the SSO dashbord configure an application client * Configure itself as an OIDC client using the data from the SSO Dashboard * Provide the option to select Identity SSO as means of authentication to end-users. * Redirect end-users to SSO * Download shared data *** ## Passing KYC When requesting end-users to pass the KYC process, a standard way is to share videos, photos or make live calls presenting physical credentials like national IDs, drivers licences and passports. Having proper verifiable credentials, the process becomes as simple as a lgin For that the web application must: * Set up a verifier account and enable SSO. * In the SSO dashbord configure an application client with credentials required for the KYC * Configure itself as an OIDC client using the data from the SSO Dashboard * Provide the option to select Identity SSO. * Redirect end-users to SSO * Download shared data to complete the KYC --- # 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.teranode.group/tng-identity-documentation/tng-identity-sso/why-identity-sso/use-cases.md?ask= ``` 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.