-
Notifications
You must be signed in to change notification settings - Fork 333
SQSERVICES-1375-block-bot-api-if-2-fa-is-enabled #2207
New issue
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
SQSERVICES-1375-block-bot-api-if-2-fa-is-enabled #2207
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer using the team end-point (GET /i/teams/:tid/features/sndFactorPasswordChallenge
). You could easily get the team id from the user id or bot id in the handlers; ie. checkAllowed
would be something like :: UserId -> Handler r ()
and be called first thing inside the handler, not from outside of it.
The only arguable downside I can see is that the block is buried inside the handler logic rather than in being visible in the routing table. But the big advantage is that the block will be effective for all situations in which the feature is enabled.
f8ff0bc
to
9076196
Compare
9076196
to
0eb744c
Compare
7ea8edc
to
ea23c3e
Compare
ea23c3e
to
1fef757
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! (I don't need to re-approve the upcoming integration test if you and concourse agree that it's good.)
https://wearezeta.atlassian.net/browse/SQSERVICES-1375
Checklist
changelog.d
.