# Authn / Authz

### 1. Just let me log in

Using OAuth 2.0, specifically OpenID Connect is a good way to handle authentication for your app. Having personal identifiable data and having to protect the privacy of the users' data is a liability which is better left to third parties.

{% embed url="<https://openid.net/connect>" %}

### 2. Maybe I need just one more thing

OAuth 2.0 has other capabilities beyond those supported by OpenID Connect.

{% embed url="<https://oauth.com>" %}

### 3. OK, I need some custom third-party info

If developing software for developers and you want specific integrations it is better to use specific capabilities provided by the third party.

{% embed url="<https://developer.github.com/apps/building-oauth-apps/>" %}

### 4. In this particular case, I'm going to use a site username/password

{% embed url="<https://JWT.io>" %}

### 5. Authentication/Authorization provider services can do more

{% embed url="<https://Auth0.com>" %}

{% embed url="<https://okta.com>" %}


---

# 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://blog.keithkim.org/code-patterns/authn-authz.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.