[Google Workspace] Deprovisioning Failure with error 403

[AM]

Hello

I used Design to create an integration with Google Workspace.
Account import and account provisioning succeed.
But account provisioning fails. It never succeeds.
Scope and custom role privileges are set according to the documentation.
https://docs.saviyntcloud.com/bundle/GoolgeDrive-v24x/page/Content/Creating-an-integration.htm

Provisioning comments from list of pending tasks:
---
Error in Deprovisioning User: 403 Forbidden { "code" : 403, "errors" : [ { "domain" : "global", "message" : "Not Authorized to access this resource/api", "reason" : "forbidden" } ], "message" : "Not Authorized to access this resource/api" }
---

[Question]
Can you help me to deprovision successfully?
If I set it correctly according to the documentation, will deprovisioning really succeed?

Regards,

[rushikeshvartak]

• 403 means service account does not have required access.
• Is it working from postman?

[AM]

Hi Rushikesh

Thank you for your reply.

• Is it working from postman?
  >After following the guide below to get a token via OAuth, Postman successfully deprovisioned the account.
  It's not a service account, though.

Using REST connector for Provisioning and De-provisioning
https://docs.saviyntcloud.com/bundle/GoolgeDrive-v24x/page/Content/Using-the-Connector-Service.htm

Regards,

[rushikeshvartak]

• validate using same account used on connector and postman

[AM]

Hi Rushikesh

Postman (Oauth) successfully deleted accounts that connector (service account) could not.

Regards,

[rushikeshvartak]

• Does postman and saviynt using same user.

[AM]

Hi Rushikesh

I used the same administrator.

The difference is authentication.
Saviynt uses a service account.
Postman uses OAuth.

Regards,

[AM]

Hi @rushikeshvartak 

Could you please let me know if there are any updates on this?

Regards,

[rushikeshvartak]

use same as postman