pomerium/authenticate
Kenneth Jenkins 6efef022af
authenticate: rework CORS headers log entry (#4900)
Currently most requests to the authenticate service will result in a log
entry with the message "authenticate: origin blocked". This may be
confusing, as the request is not in fact blocked; instead, what happens
is that no special CORS headers are added to the response.

Let's reverse the logging behavior, and instead log a message only for
those requests with a valid signature, where we do add CORS headers to
the response.

Add a unit test case exercising the CORS middleware.
2024-01-10 10:39:25 -08:00
..
events move events.go out of internal/authenticateflow (#4852) 2023-12-11 19:42:56 -08:00
authenticate.go authenticateflow: move stateless flow logic (#4820) 2023-12-06 16:55:57 -08:00
authenticate_test.go options: support multiple signing keys (#3828) 2022-12-22 09:31:09 -07:00
config.go move events.go out of internal/authenticateflow (#4852) 2023-12-11 19:42:56 -08:00
handlers.go authenticate: rework CORS headers log entry (#4900) 2024-01-10 10:39:25 -08:00
handlers_test.go authenticate: rework CORS headers log entry (#4900) 2024-01-10 10:39:25 -08:00
identity.go move directory providers (#3633) 2022-11-03 11:33:56 -06:00
middleware.go authenticateflow: move stateless flow logic (#4820) 2023-12-06 16:55:57 -08:00
state.go support both stateful and stateless authenticate (#4765) 2023-12-07 14:24:13 -08:00