mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-18 05:52:51 +00:00
## Which Problems Are Solved There is currently a knowledge gap in the documentation where users are unclear on if or why human accounts cannot have Personal Access Tokens (PATs), which has led to confusion in community channels like Discord and GitHub. ## How the Problems Are Solved Clarified that human PATs are currently not supported in the Personal Access Token documentation and added a direct link to GitHub Issue #10915 so users can track and upvote this capability. ## Additional Changes None ## Additional Context None --------- Signed-off-by: Rajat Singh <[email protected]> Co-authored-by: Rajat Singh <[email protected]>
This commit is contained in:
co-authored by
Rajat Singh
parent
6eafca2872
commit
f0a999bccd
@@ -5,7 +5,10 @@ sidebar_label: Personal access token authentication
|
||||
---
|
||||
|
||||
A Personal Access Token (PAT) is a ready-to-use token that can be used as an _Authorization_ header.
|
||||
At the moment ZITADEL only allows PATs for service accounts.
|
||||
|
||||
<Callout>
|
||||
Human PATs are currently not supported. PATs are available for service accounts only.
|
||||
</Callout>
|
||||
|
||||
It is an alternative to the [private key JWT](./private-key-jwt) and [client credentials](./client-credentials). Read more about the different [authentication methods for service accounts](./authenticate-service-accounts).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user