> For the complete documentation index, see [llms.txt](https://docs.teranode.group/tng-identity-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teranode.group/tng-identity-documentation/tng-identity-sso/why-identity-sso/use-cases.md).

# 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