Google Identity-Aware Proxy
cloud.google.com
Google Identity-Aware Proxy
1–10 of 51 posts
Re: Google Identity-Aware Proxy
#2We use mutually-authenticated TLS (ie, the proxy presents a client cert to your backend) so that you know the entire request is valid, including the username header. IAP only signs the header, which could be replayed because it's not bound to the session (eg, a debug page exposes request headers). But it's probably easier to grab a library that can validate JWT than worry about your TLS termination layer (eg, in a rails app behind nginx terminating TLS & serving asssets)
Re: Google Identity-Aware Proxy
#3Re: Google Identity-Aware Proxy
#4Re: Google Identity-Aware Proxy
#5Re: Google Identity-Aware Proxy
#6Can anyone recommend this? https://github.com/bitly/oauth2_proxy
Re: Google Identity-Aware Proxy
#7How does this compare/relate with LastPass?
Re: Google Identity-Aware Proxy
#8Re: Google Identity-Aware Proxy
#9It's really an amazing way to think about security for a company. If you deploy it universally across your company, VPNs become obsolete. This solves a popular attack vector where bad-actors just need to get onto a corporate network to do damage. If you can authenticate at every service your employees connect to, it closes down that vector.