G Suite and RingCentral Provisioning Errors

  • 0
  • 1
  • Question
  • Updated 1 month ago
  • Acknowledged
I have SSO between RingCentral and G Suite working, but I am unable to get  Google G Suite Auto Provisioning working, as referenced here, https://success.ringcentral.com/knowledge/TOCArticleRendererPkb.apexp?_ga=2.254948104.123364451.1513985743-148508428.1513985743&id=kA2340000008dWz&pubstatus=o&refURL=http%3A%2F%2Fsuccess.ringcentral.com%2Farticles%2FRC_Knowledge_Article%2F9268

It sort of worked and initially created a few accounts. Now it just constantly throws out the following error, which I can find no reference to anywhere on the Internet, Error code: 45003,

StatusCode: 403 : Forbidden : {    schemas  : [  urn:ietf:params:scim:api:messages:2.0:Error  ]     status  :  403      detail  :  Feature [Bulk Assign] is not available  }


It says this for every account it tries to add and fails. More recently, it started giving this error for my own account,

StatusCode: 409 : Conflict : { schemas : [ urn:ietf:params:scim:api:messages:2.0:Error ] status : 409 detail : Email address has already been used by another user }

It's my administrator account, it says that email address already exists in RingCentral. It's my account, not sure why it doesn't recognize it. It never gave that error before today, no matter how many attempts I made at getting this setup.

I've deleted and added back in the SAML RingCentral app on Google multiple times. I've tried it on different browsers and different operating systems. I've tried it for "On for everyone" to limiting it to groups. I've tried "Re-authorize app" many times. I've tried removing extra attribute mappings and deprovisioning config. It simply will not create a single account in RingCentral after my first few initial attempts over a month ago.

I put in a ticket to RingCentral and a little over a month later level 2 support called me and told me that it wasn't working because I didn't first implement SSO. I have SSO working without issue for about a week now and it hasn't provisioned a single user. I've tried everything I can possibly think of. I feel like I'm the only person on the planet trying to do this as I can find zero information on the web regarding any of this.

If there is anyone on this forum who has had success with this, please give me some hints at what it might be that's causing it. I'm happy to go into more detail if needed.
Photo of ELLIS

ELLIS

  • 142 Points 100 badge 2x thumb

Posted 11 months ago

  • 0
  • 1
Photo of Saadet - Community Support

Saadet - Community Support, Official Rep

  • 43,876 Points 20k badge 2x thumb
Hello Ellis,

I'm doing some research on this. In the meantime, can you open a new case with us?
  
Photo of Saadet - Community Support

Saadet - Community Support, Official Rep

  • 43,876 Points 20k badge 2x thumb
Hello Ellis,

Did you still need help with this? 
Photo of ELLIS

ELLIS

  • 142 Points 100 badge 2x thumb
I contacted support and went through all the steps multiple times. It never ended up working.
Photo of Saadet - Community Support

Saadet - Community Support, Official Rep

  • 41,798 Points 20k badge 2x thumb
Hello ELLIS,

We have an Integrations team that should be able to assist you on this. Please open a new case (feel free to reply back here with the case number) and request to have the Integrations team assist you. Once you open the case, I'll be sure to let our team know to expect it.
Photo of Ivan Wright

Ivan Wright

  • 60 Points
If anyone else find this page while searching for the quoted error, the solution for me was to enable “Directory Integration” as an admin.
Provisioning from Okta worked afterwards. The help text regarding Active Directory is a bit misleading, but this feature seems to be required for provisioning to work at all from an IdP.