-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add option to allow client redirects from IPs in specified CIDR ranges in SSO client logins #44556
Conversation
1b68ba6
to
595d09d
Compare
ac1563a
to
73c651f
Compare
48fe0fe
to
816b776
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.
There's still maybe a point to ignoring invalid CIDRs (and invalid regexps, too, which utils.SliceMatchesRegex
already hard fails on) since the rules are purely additive and there's no chance of potentially failing open, but as long as "standard" logins are guaranteed to not break, it's probably fine
e3fd04e
to
fa59038
Compare
I opted to log errors when dealing with invalid CIDRs and while I was at it regexes as well |
101e14c
to
45cce5c
Compare
🤖 Vercel preview here: https://docs-dxanxmz4a-goteleport.vercel.app/docs/ver/preview |
waiting for the client-side change to --callback
…s in SSO client logins
a7ca727
to
2e2cc41
Compare
🤖 Vercel preview here: https://docs-m7xvqj2rr-goteleport.vercel.app/docs/ver/preview |
@capnspacehook See the table below for backport results.
|
…s in SSO client logins (#44556) Co-authored-by: Andrew LeFevre <Andrew LeFevre>
Fixes #44535.
changelog: Add option to allow client redirects from IPs in specified CIDR ranges in SSO client logins