steve-chavez
d4f82919f7
docs: external authentication page in explanations
...
- Move page from External JWT generation
2025-05-30 18:08:40 -05:00
Laurence Isla and Wolfgang Walther
8531c502d7
docs: JWK kid parameter validation
2025-05-30 14:35:58 +02:00
Taimoor Zaeem and Wolfgang Walther
91814cd4f8
docs: add note in JWT Role Extraction section
...
Add a note describing that the used JSPath DSL does not
strictly follow the JSONPath as described in RFC 9535
2025-05-21 21:02:00 +02:00
steve-chavez
e20dc60e83
docs: jwt role extraction link to config
...
The feature section was missing a link to its config.
Also shorten the section name.
2025-05-09 20:47:30 -05:00
Laurence Isla
e0c5b3a314
correct: handle array values in JWT aud claim correctly
2025-05-07 21:54:32 +00:00
Taimoor Zaeem and Steve Chavez
36b6a2c86b
fix: improve jwt errors
2025-03-13 00:20:54 +01:00
Taimoor Zaeem and GitHub
560c511f81
docs: add missing jwt claims and clock skew ( #3908 )
2025-02-12 15:38:20 -05:00
M. Taimoor Zaeem and Steve Chavez
af6b79d4d7
feat: support string comparison for jwt-role-claim-key
2024-12-12 08:47:06 -05:00
Wolfgang Walther and Wolfgang Walther
944b02fbb8
docs: Rename Stored Procedures to Functions consistently
...
This avoids confusing our RPCs with actual CREATE PROCEDURE, which we don't
support.
References https://github.com/PostgREST/postgrest-docs/issues/147
2024-02-21 09:40:11 +01:00
Wolfgang Walther and Wolfgang Walther
3d95c41115
docs: Remove note about risk of asymmetric keys for JWT auth
...
The obviously wrong statement is, that PostgREST does not support asymmetric keys, while it
does. Extending on this type of attack is not necessary, because it is in fact covered by
the paragraph before - reading the algorithm from the JWT header is the problem in that case,
too. We don't do that.
This leaves us with the sentence about how the chosen library is the most important part. While
that is correct, the hint about high quality libraries for use on the *client* side is mis-
leading: The important part here is the library we choose to implement PostgREST with, not the
client-side lib. Thus, removing the whole paragraph is the best thing to do here.
Resolves https://github.com/PostgREST/postgrest-docs/issues/123
2024-02-19 21:54:15 +01:00
Laurence Isla and GitHub
cb5d80aff8
Remove HTTP Snippets
2024-01-17 09:07:37 -05:00
steve-chavez
b04a7f0080
fix server-timing header section
...
Also link it to jwt caching
2023-12-02 01:41:26 -05:00
steve-chavez
475b4601ca
split role settings from function settings
...
Also add doc for GRANT SET ON PARAMETER, see
https://github.com/PostgREST/postgrest/pull/3058 .
2023-11-21 17:49:35 -05:00
Taimoor Zaeem and Steve Chavez
49e3d2c4b4
add documentation for statement_timeout set on functions
2023-11-21 17:49:35 -05:00
Taimoor Zaeem and GitHub
bae8dc3283
add documentation for JWT caching ( #683 )
2023-10-10 23:22:41 -03:00
Steve Chavez and GitHub
93f2b0093c
references: remark NOLOGIN impersonated roles
2023-10-07 19:20:48 -03:00
steve-chavez
daad21e9ec
add note to impersonated role settings
2023-08-10 08:49:55 -05:00
steve-chavez
5e19594ea4
auth: explain why jwt is used
2023-05-27 22:23:44 -05:00
steve-chavez
911634ed32
move impersonated settings
2023-05-12 01:14:19 -03:00
steve-chavez
dec1e03a0e
add v11 release notes with docs improvs
2023-05-11 01:37:50 -03:00
steve-chavez
79620396ed
remove manual inclusion of pages on index
...
* drop unavailable doc pages from release notes
* rename releases pages so they order in TOC
2023-05-08 08:58:09 -03:00
steve-chavez