ian/directus-extension-external-jwt
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: bump (#4)

Browse Source 
docs: add more description to the documentation

Co-authored-by: Krise <krise86@users.noreply.github.com>
This commit is contained in:
Kristoffer
2023-08-02 17:07:23 +02:00
committed by GitHub
parent 4efe2da9e3
commit bd902e99fe
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -5,6 +5,12 @@ The plugin expects to resolve the following new configuration option
The provider must issues Access tokens as JWT since this is used for verification right now. Might add support for general tokens later. The provider must issues Access tokens as JWT since this is used for verification right now. Might add support for general tokens later.
If USEDB are enabled the extension will try to search for the user in the database by looking at the sub in the JWT token. The user must exists and all roles for that use will be used.
When using USEDB you should also enable the caching option to reduce the time spent against the api and reduce the number of db lookups. The cache stores the user object in the cache based on the sub in the token.
USEDB also validates that the issuer is the same as assigned to the user.
## Configuration ## Configuration
all configuration options listed here are an extension to directus default config. all configuration options listed here are an extension to directus default config.