# Generating OAuth 2.0 Authentication Credentials

**URL:** <https://developer.sailpoint.com/discuss/t/generating-oauth-2-0-authentication-credentials/60898>\
**Category:** Connectivity Documentation Feedback\
**Tags:** va-con-docs\
**Created:** [June 3, 2024, 12:36pm UTC](https://developer.sailpoint.com/discuss/t/generating-oauth-2-0-authentication-credentials/60898 "2024-06-03T12:36:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DocsTeam](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@DocsTeam](https://developer.sailpoint.com/discuss/u/DocsTeam)\
**Post date:** [June 3, 2024, 12:36pm UTC](https://developer.sailpoint.com/discuss/t/generating-oauth-2-0-authentication-credentials/60898/1 "2024-06-03T12:36:12Z")

</div>

The Google Workspace SaaS connector uses the OAuth 2.0 protocol for authentication and authorization of the Google Workspace APIs. It supports the following OAuth 2.0 scenarios:

* * *
This is the companion discussion topic for the documentation at [https://documentation.sailpoint.com/connectors/saas/googleworkspace/help/saas\_connectivity/google\_workspace/prereqs\_for\_oauth\_2\_0.html](https://documentation.sailpoint.com/connectors/saas/googleworkspace/help/saas_connectivity/google_workspace/prereqs_for_oauth_2_0.html)

---

<div class="post-metadata">

**Author:** ![M\_rtenH](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/m_rtenh/32/429_2.png) [@M\_rtenH](https://developer.sailpoint.com/discuss/u/M_rtenH)\
**Post date:** [December 3, 2024, 10:24am UTC](https://developer.sailpoint.com/discuss/t/generating-oauth-2-0-authentication-credentials/60898/2 "2024-12-03T10:24:06Z")

</div>

The listing of Scopes within this documentation is needlessly complex + the scopes listed here: [Generating OAuth 2.0 Authentication Credentials](https://documentation.sailpoint.com/connectors/saas/googleworkspace/help/saas_connectivity/google_workspace/prereqs_for_oauth_2_0.html#Service) is incomplete and missing [https://www.googleapis.com/auth/admin.directory.group](https://www.googleapis.com/auth/admin.directory.group) so both account/entitlement aggregation will fail.

For overall visibility it’s good to list which scopes are required for which operation so users can pick and choose but I’d propose keeping a single list of required scopes for full basic functionality + scopes required for CIEM.