<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sanjeev Gopinath on Medium]]></title>
        <description><![CDATA[Stories by Sanjeev Gopinath on Medium]]></description>
        <link>https://medium.com/@sanjeevgopinath?source=rss-35d662499637------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*N2jgiearCdnZChk7.</url>
            <title>Stories by Sanjeev Gopinath on Medium</title>
            <link>https://medium.com/@sanjeevgopinath?source=rss-35d662499637------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:42:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sanjeevgopinath/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Demystifying Identity Management in GCP]]></title>
            <link>https://medium.com/cloud-cocktail/demystifying-identity-management-in-gcp-60e1c765c025?source=rss-35d662499637------2</link>
            <guid isPermaLink="false">https://medium.com/p/60e1c765c025</guid>
            <dc:creator><![CDATA[Sanjeev Gopinath]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 12:43:18 GMT</pubDate>
            <atom:updated>2021-07-07T13:17:00.406Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cNmECa-_RIRXQRfofXILuQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sadswim?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">ian dooley</a> on <a href="https://unsplash.com/s/photos/launch?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>“Well begun is half done”. And for a Cloud Migration, that would be setting up identity well :). When you have your identities and governance structures right, you can be on cruise mode throughout your cloud journey.</p><p>In this blog post, I will explain the 101s of Identity Management in the context of setting up user access to Google Cloud Platform (GCP). This can be very useful if you are new to GCP or are planning to migrate soon.</p><p>If you are familiar with the identity setup in another cloud, identity management in Google Cloud should be fairly straightforward. But, depending on whether you managed your users in IAM or the Directory Service, there could be minor differences. I will attempt to clarify those concepts below.</p><p><strong>Google Cloud Identity Service and GCP IAM</strong></p><p>In Google Cloud, the Identity Service is a global, standalone directory service external to Google Cloud Platform. We refer to this service as the <strong>Google Cloud Identity</strong> and it differs from the IAM service in GCP. This service allows you to create and manage your corporate user identities. It is tightly integrated to Google Workspace (erstwhile gSuite) as they share the same SDKs and code base. If your organization uses Google Workspace, you may already be familiar with this service.</p><p>There are two flavors of Google Cloud Identity — Free &amp; Premium. Cloud Identity Premium offers features such as Advanced MDM, Endpoint management. For access to GCP, both of these flavors work.</p><p>The <strong>IAM service in GCP</strong> is predominantly responsible for role based access control (RBAC) of cloud resources. It doesn’t deal with user creation and management, but needs a valid Google Identity to work. Broadly, a valid Google Identity can either be a consumer (Gmail.com) account or a corporate user account managed in Google Cloud Identity. As Google Cloud Identity provides rich features to manage corporate identities, it is the de facto choice for Enterprises.</p><p>To put it in other words, Google Cloud Identity is used for user management &amp; AuthN and GCP IAM Service is used for AuthZ.</p><p>An interesting point to note is that the GCP IAM allows you to add any Google Identity to your GCP Project irrespective of whether your Organization manages them. For example, if you are EnterpriseA, you can add users of EnterpriseB or consumer (gmail.com) users to your GCP projects. This simplifies cross-Enterprise collaboration.</p><p>Another benefit of this capability is that the users from both the Enterprises need to be onboarded to Google Cloud Identity only once. Once their Google Identities are in place, they can collaborate with other Enterprises without requiring to set up a new federation every time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/0*RYtfNC-dMZ8Umdl4" /><figcaption>Source: <a href="https://cloud.google.com/architecture/identity/overview-google-authentication">Google Cloud Documentation</a></figcaption></figure><p><strong>Onboarding users</strong></p><p>Onboarding your users to Google Cloud Identity is a straightforward process. If your Organization uses an existing Identity Provider (IdP), you can simply federate them to let your users use their existing credentials. For medium and large organizations, who have already deployed identity solutions and want to continue leveraging them, this approach would be a quick mechanism to get started. Google Cloud supports <a href="https://cloud.google.com/architecture/identity/best-practices-for-federating">federation</a> to external identity providers such as Okta, Active Directory via <a href="https://cloud.google.com/architecture/identity/federating-gcp-with-active-directory-introduction">ADFS</a> or <a href="https://cloud.google.com/architecture/identity/federating-gcp-with-azure-active-directory">Azure AD</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/0*-MbrsKnTnUcL5iSH" /><figcaption>Source: <a href="https://cloud.google.com/architecture/identity/federating-gcp-with-active-directory-introduction">Federating with ADFS</a></figcaption></figure><p>In the rarest of cases, if you cannot federate (e.g. legacy LDAP systems), you can create parallel identities in Cloud Identity, in which case, your users will use their existing email address, but a separate password for logging into Google Services.</p><p>Google Cloud Identity is tied to your domain name. If your primary domain name is “example.com”, that becomes your Organization name in Google Cloud. And, you can add all users with “@example.com” email addresses to Google Cloud Identity. If say, some of your users have a different domain name in their email address e.g. “@firstexample.com”, Cloud Identity wouldn’t allow that. Here, you need to add the domain “firstexample.com” as a secondary domain under “example.com” Organization. If a domain has been added as a secondary or primary domain in an Organization, we cannot reuse it in a different Organization.</p><p>Sometimes, because of legal reasons, or existing setup, you may want separation between the two entities (example.com &amp; firstexample.com). For such scenarios, you can create two Organizations — one for example.com &amp; another for firstexample.com. And, leverage the flexibility of IAM Service to add both the users to the same GCP Project. Since GCP IAM recognizes any valid Google Identity, this operation is allowed.</p><p>Besides setting up access to Google Cloud Services, administrators can also manage SSH access to virtual machines using IAM. It is a useful feature powered by the OS Login utility that ships with all Google-provided images. The OS Login utility ties Linux user accounts to Google Identity, therefore users can login to the virtual machines using their existing username and password. Administrators can centrally manage the user privileges across the Linux VMs at scale using IAM.</p><p><strong>Groups</strong></p><p>If you are a large Organization, it is quite possible that you will onboard and manage many users, replicate their physical team structures and governance models on GCP too. For such scenarios, leverage Groups in Google Cloud Identity. Groups are a powerful means to manage your GCP IAM policies and permissions at scale. Instead of setting policies and permissions for every user, you can set them against the Groups. You can federate existing groups or create new groups in Cloud Identity for your “devops-team”, “networking-team”, “analytics-team” and so on and set appropriate permissions using IAM service.</p><p>Groups builds on the flexibility that Google Cloud Identity provides. Therefore, you have the ability to add members from other Organizations in your Groups as long as those Organizations are on Google Cloud Identity.</p><p>So now you know how to onboard your users, how to leverage groups and importantly the difference between Google Cloud Identity &amp; GCP IAM. For a deep dive, you can refer to our <a href="https://cloud.google.com/architecture/identity">documentation</a> that takes you through each step.</p><p>We can’t wait to have you on Google Cloud. Get <a href="https://cloud.google.com/gcp/">started</a> today!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60e1c765c025" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloud-cocktail/demystifying-identity-management-in-gcp-60e1c765c025">Demystifying Identity Management in GCP</a> was originally published in <a href="https://medium.com/cloud-cocktail">cloud-cocktails</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>