We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After implementing the redis part to write user's login activity, we need to be able to actually store the data.
The goal here would be to implement a new Authenticator on Tmail, like TMailUserRepositoryAuthenticator that would:
Authenticator
TMailUserRepositoryAuthenticator
We could then just call the method of the underlying Authenticator, and if auth is successful, we store the user login info in redis.
We can get the info from the MDC / context :
org.slf4j.MDC.get("ip") clock.instant() org.slf4j.MDC.get("protocol") org.slf4j.MDC.get("user-agent")
We might need to do a little addition on James side beforehand though to propagate the MDC context upon login.
DoD: Integration tests.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After implementing the redis part to write user's login activity, we need to be able to actually store the data.
The goal here would be to implement a new
Authenticator
on Tmail, likeTMailUserRepositoryAuthenticator
that would:We could then just call the method of the underlying Authenticator, and if auth is successful, we store the user login info in redis.
We can get the info from the MDC / context :
We might need to do a little addition on James side beforehand though to propagate the MDC context upon login.
DoD: Integration tests.
The text was updated successfully, but these errors were encountered: