Shraya Ramani

Thanks for opening this @aiman-alsari, this is something we'd be happy to support if you'd like to contribute a pull request!

Thank you for opening this issue @jwhitcraft. While we are definitely open to adding variations to our quick start, we don't have any experience with Helm in our organization, so...

Thanks for opening this issue @zilman. This seems like something that could be useful. If you'd like to open a PR we can work on getting it merged in!

This is specifically to remove the provider interface (or consolidate both provider interfaces into one) in `sso-proxy`. This was something that we have yet to clean up from when we...

Hi @epot, we currently only support Google Groups based authorization. To set that up you would need to set up a Google service account. Instructions can be found [here](https://github.com/buzzfeed/sso/blob/master/docs/google_provider_setup.md#3-set-up-a-service-account-for-google-groups-based-authorization). Please...

To clarify, the quickstart itself does not have support out of the box to use google groups without having a user set up and enable the Google Admin SDK. After...

@takeda, the `GOOGLE_ADMIN_EMAIL` field would be different from the contents of json file. It would be an administrative email address on your organization's domain, the identity of which can be...

Thank you for finding this bug @bertjwregeer, this is most likely a feature that existed in oauth2_proxy that we did not end up keeping in sso, and never prioritized implementing....

Since in its current state having this field is confusing since it doesn't actually do anything we think it makes sense to remove it, but I'm going to rename this...

Hi @BigbigY, thank you for opening this. This would require the addition of a provider specific for Active Directory or LDAP. We are unable to prioritize working on something like...