<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problems adding a Google Directory Service to CyberArk Identity (Idaptive). Get This app is blocked from Google. in Workforce Identity Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/problems-adding-a-google-directory-service-to-cyberark-identity/m-p/1390229#M1289</link>
    <description>&lt;P&gt;When I click "Authorize," after I log into my Google Workspace tenant to continue to idaptive.app, I get the error message:&lt;/P&gt;&lt;P&gt;This app is blocked&lt;/P&gt;&lt;P&gt;This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I get this with two different Google Workspace tenants.&lt;/P&gt;</description>
    <pubDate>Thu, 15 Dec 2022 19:55:16 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2022-12-15T19:55:16Z</dc:date>
    <item>
      <title>Problems adding a Google Directory Service to CyberArk Identity (Idaptive). Get This app is blocked from Google.</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/problems-adding-a-google-directory-service-to-cyberark-identity/m-p/1390229#M1289</link>
      <description>&lt;P&gt;When I click "Authorize," after I log into my Google Workspace tenant to continue to idaptive.app, I get the error message:&lt;/P&gt;&lt;P&gt;This app is blocked&lt;/P&gt;&lt;P&gt;This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I get this with two different Google Workspace tenants.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Dec 2022 19:55:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/problems-adding-a-google-directory-service-to-cyberark-identity/m-p/1390229#M1289</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-12-15T19:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: Problems adding a Google Directory Service to CyberArk Identity (Idaptive). Get This app is blocked from Google.</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/problems-adding-a-google-directory-service-to-cyberark-identity/m-p/1390230#M1290</link>
      <description>&lt;P&gt;I got some help from a CyberArk SE.  This is apparently a known, though not documented issue:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The customer needs to add CyberArk as a Trusted App.&lt;/P&gt;&lt;P&gt;Have the customer login to Google as an Admin. Head to Security &amp;gt; Access and data control &amp;gt; API control &amp;gt; Add app &amp;gt; OAuth App Name or Client ID.&lt;/P&gt;&lt;P&gt;Then search for CyberArk by using CyberArk’s third-party client code:&amp;nbsp;&lt;A alt="http://736006718218-v15dghc4juspi26qv6f4omas8drqgprj.apps.googleusercontent.com/" href="http://736006718218-v15dghc4juspi26qv6f4omas8drqgprj.apps.googleusercontent.com/" target="_blank"&gt;&lt;B&gt;736006718218-v15dghc4juspi26qv6f4omas8drqgprj.apps.googleusercontent.com&lt;/B&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This can be done from the Google Admin console under Security &amp;gt; API Controls &amp;gt; App access Control.  Click Manage Third-party App Access, then click Add app and enter the above Client ID.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kevin&lt;/P&gt;</description>
      <pubDate>Tue, 20 Dec 2022 16:14:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/problems-adding-a-google-directory-service-to-cyberark-identity/m-p/1390230#M1290</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-12-20T16:14:58Z</dc:date>
    </item>
  </channel>
</rss>

