patternMinor
Using GSuite or Github to Manage who can log into Linux or Windows VMs on Azure
Viewed 0 times
canlogwhogithubgsuiteintomanagevmsazureusing
Problem
I want to manage the members of our team who are able to log into our cloud-hosted VMs, both Linux and Windows. We currently use G Suite and GitHub, to manage access to our code and documentation etc. I would really prefer to not have to also manage a separate Active Directory Domain within our VNets or deal with revoking ssh keys or updating multiple usernames/passwords on every single VM we deploy.
Are there ways to use either GSuite or Github to control login access to our VMs?
If there isn't, what are the best practices to deal with 20+ developers who are all empowered with DevOps responsibilities?
Are there ways to use either GSuite or Github to control login access to our VMs?
If there isn't, what are the best practices to deal with 20+ developers who are all empowered with DevOps responsibilities?
Solution
I would really prefer to not have to also manage a separate Active Directory Domain within our VNets
You've already found the answer: centralized authentication.
If you use a tool like Okta, you can indirectly tie GSuite to AD (or an LDAP server). And then of course you can tie OpenSSH there as well.
or deal with revoking ssh keys
Centralized authentication solves this.
or updating multiple usernames/passwords on every single VM we deploy.
And this as well.
You've already got the answer, even if you don't like it.
You've already found the answer: centralized authentication.
If you use a tool like Okta, you can indirectly tie GSuite to AD (or an LDAP server). And then of course you can tie OpenSSH there as well.
or deal with revoking ssh keys
Centralized authentication solves this.
or updating multiple usernames/passwords on every single VM we deploy.
And this as well.
You've already got the answer, even if you don't like it.
Context
StackExchange DevOps Q#2807, answer score: 3
Revisions (0)
No revisions yet.