pomerium/internal/authenticateflow
Kenneth Jenkins fb9eb31be9
authenticateflow: change how sessions are deleted (#4893)
The identity manager expects to be able to read session ID and user ID
from any deleted databroker session records. The session.Delete()
wrapper method is not compatible with this expectation, as it calls
Put() with a record containing an empty session. The stateful
authentication flow currently calls session.Delete() from its
RevokeSession() method.

The result is that the identity manager will not correctly track
sessions deleted by the the stateful authentication flow, and will still
try to use them during session refresh and user info refresh.

Instead, let's change the stateful authentication flow RevokeSession()
method to perform deletions in a way that is compatible with the current
identity manager code. That is, include the existing session data in the
Put() call to delete the revoked session.
2024-01-03 09:48:11 -08:00
..
authenticateflow.go authenticateflow: move stateless flow logic (#4820) 2023-12-06 16:55:57 -08:00
identityprofile.go authenticateflow: move stateless flow logic (#4820) 2023-12-06 16:55:57 -08:00
request.go authenticateflow: add stateful flow (#4822) 2023-12-07 09:54:42 -08:00
request_test.go authenticateflow: move stateless flow logic (#4820) 2023-12-06 16:55:57 -08:00
stateful.go authenticateflow: change how sessions are deleted (#4893) 2024-01-03 09:48:11 -08:00
stateful_test.go authenticateflow: change how sessions are deleted (#4893) 2024-01-03 09:48:11 -08:00
stateless.go move events.go out of internal/authenticateflow (#4852) 2023-12-11 19:42:56 -08:00