6 Commits

Author	SHA1	Message	Date
Vish (Ishaya) Abrams	4e2013e6ba	fix: update code_verifier to use recommended method (#2620) ... The [RFC](https://datatracker.ietf.org/doc/html/rfc7636#section-4.1) says that a code verifier just uses unreserved characters, but the recommended method is that it is a base64-urlencoded 32-octet url. Some implementations of PKCE (most notably the one used by salesforce) require that this is a valid base64 encoded string[1], so this patch switches to using the recommended approach to make it more compatible. [1]: https://help.salesforce.com/s/articleView?id=sf.remoteaccess_pkce.htm&type=5	2024-11-06 15:16:39 +01:00
t-katsumura	d107d885e4	Session-Cookie Support (#1713) ... * Create session cookie when cookie-expire set 0 * Fix format * add test * fix lint error * fix test code * fix conflicted test case * update test case of cookie expiration * update tests of csrf cookies * update docs * Update docs/docs/configuration/overview.md Co-authored-by: Joel Speed <Joel.speed@hotmail.co.uk> --------- Co-authored-by: tanuki884 <morkazuk@fsi.co.jp> Co-authored-by: Joel Speed <Joel.speed@hotmail.co.uk>	2023-08-16 12:23:02 +01:00
Braunson M	f4f5b7756c	Fix PKCE code verifier generation to never use UTF-8 characters ... - This could result in intermittent/random failures of PKCE enabled IdP's	2022-11-18 20:37:14 -05:00
Nick Meves	56f199a24f	Stop accepting legacy SHA1 signed cookies	2020-09-24 10:31:34 -07:00
Nick Meves	1c8c5b08d7	Handle cookie signing errors	2020-08-09 07:55:40 -07:00
Nick Meves	f60e24d9c3	Split non-cipher code to utils.go out of ciphers.go	2020-06-12 14:36:58 -07:00