c26ac31816
- The current architecture is inherently insecure, because you can construct the 'secret' cookie value with values that are available in the database. Thus provides zero protection when a database is dumped/leaked. - This patch implements a new architecture that's inspired from: [Paragonie Initiative](https://paragonie.com/blog/2015/04/secure-authentication-php-with-long-term-persistence#secure-remember-me-cookies). - Integration testing is added to ensure the new mechanism works. - Removes a setting, because it's not used anymore. (cherry picked from commit |
||
---|---|---|
.. | ||
auth_token.go | ||
main_test.go | ||
oauth2.go | ||
oauth2_test.go | ||
session.go | ||
source.go | ||
source_test.go | ||
token.go | ||
token_scope.go | ||
token_scope_test.go | ||
token_test.go | ||
twofactor.go | ||
webauthn.go | ||
webauthn_test.go |