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
Google Sign-In #1411
Comments
So this feature was added? Or just the label was removed? |
release/future label was converted to milestone Unscheduled. 1.2 will include moving auth out of cattle and into a standalone golang project that will be more pluggable. So we could potentially look at this after that, though TBH it seems like there is minimal community interest (and zero customer interest that I'm aware of). |
I would love to have this feature. All of the team has a Google Apps login but not everyone has a GitHub user. Plus, when a developer leaves the company, they retain their GitHub user -- they would not retain access to their Google Apps login. +1 this feature |
For the same reason as @sjwoodr it would be nice to have, I wouldn't expect permissions to be handed on the Google Apps side, just the oauth and rancher to handle permissions, even if it was just domain locked e.g. @example.com |
Also would be interested in this for customer uses. This biggest issue here is account deprovisioning as you have to remove someone from the GitHub org which in my experience is something that doesn't quite happen in lock step with some leaving. |
+1 We have lots of gapps accounts using rancher, makes account managment much easier! |
+1 We would also like to see this |
Hey guys, do you have plans to release this in the near future? We use g apps for our enterprise and would love to see our rancher cluster integrated with it. |
@vincent99 any status update on this? Been a few months since an update and was curious. |
Nothing new, we still have no plans to add this without a customer driving it... |
Hmm, noted. We are in the process of eval'ing Rancher and noticed it missing. It would make our lives much easier. We may be a customer if we go Rancher. So will definitely request if that happens :-) |
+1 from another potential customer |
Since it's apparently customer driven, is it not possible to just have Universal SAML? We were excited the release notes for 2.1.0 mentioned SAML. However after reading the docs, it's only for Ping Identity and KeyCloak. Which are services I have never heard of before, but some one must be using them enough to warrant the work. G Suite integration would definitely be an easy win for the community, but understand if you are still abiding by only adding Auth providers for a customer request. |
Love to see this feature in a future release. |
If you want to use GSuite SAML you can use AD FS + https://mattslifebytes.com/2018/08/15/using-okta-and-other-saml-idps-with-rancher-2-0/ |
For Google Oauth #10053 |
Backend for this is ready |
Verified this on rancher:master-head
|
@sowmyav27 Testing out the
Also, what should be value of Thanks for the PR though! :D |
@mr-karan There is an issue related to providing more instructions on the UI for the @mrajashree Could you add your comments - as to the exact instructions to set up a Service Account and get the related creds? |
@mrajashree Hi! Can you please let me know the instructions to create a SA, would be really helpful! I am stuck on this and would love to go live with the Google Auth 👍 Again, thanks for the PR |
@sowmyav27 @mrajashree Hi, can I have your attention on this please? :) I upgraded to the latest master release to try this feature, but due to the above mentioned roadblocks, unable to get this rolling. Do you mind documenting the instructions to setup google auth please? |
@mr-karan The docs aren't up yet but this gist contains the instructions https://gist.github.com/mrajashree/9dc4cd8e11a9e813a96e713964c74ca9 Please let us know if that works :) |
Please add support for using google apps accounts for logon.
The text was updated successfully, but these errors were encountered: