mirror of
https://github.com/livekit/livekit.git
synced 2026-05-24 19:05:36 +00:00
Updated access token doc link
This commit is contained in:
@@ -56,7 +56,7 @@ LiveKit is published to Docker Hub under livekit/livekit-server
|
||||
### Creating API keys
|
||||
|
||||
LiveKit utilizes JWT based access tokens for authentication to all of its APIs.
|
||||
Because of this, the server needs a list of valid API keys and secrets to validate the provided tokens. For more, see [Authentication](docs/authentication.md).
|
||||
Because of this, the server needs a list of valid API keys and secrets to validate the provided tokens. For more, see [Access Tokens](https://docs.livekit.io/guides/access-tokens).
|
||||
|
||||
Generate API key/secret pairs with:
|
||||
|
||||
|
||||
@@ -1,12 +0,0 @@
|
||||
# Authentication
|
||||
|
||||
LiveKit uses access tokens (JWT) to authenticate clients. A pair of API key and secret key is used to authenticate each API holder.
|
||||
|
||||
An access token encapsulate a few pieces of information:
|
||||
|
||||
- Grants: what permissions does this token have
|
||||
- Issuer: which api key issued the token
|
||||
- Expiration: how long should it be valid for
|
||||
- Identity: the participant's identity (when joining a room)
|
||||
|
||||
Access tokens can be created with `livekit-cli`, or any of the livekit server SDKs
|
||||
Reference in New Issue
Block a user