Ping Federate SSO and BOX Group Provisioning Not working (yet)

Hi all,

I'm having trouble getting Group Provisioning to work between Ping Identity / PingFederate and our Box instance. I've gone through creating an APP on the BOX Side, obtaining Client ID, Secret, and Access and Refresh Tokens, etc, for it, and have followed the directions for setting up a "Target" on the PING side that uses these details, etc.

However, when I try to connect to BOX via Ping, I'm seeing the following error message on the PING side:

09:37:49,266 ERROR [GenericUserProvisioningChannel] Exception during dirty group records cleanup phase! [] Channel: channel1
com.pingidentity.provisioner.sdk.SaasPluginException: Exception failed due to Service Level Error. Provided error message: Service is Unavailable. [prov_exception_msg] [SBOX004] There was a problem refreshing the Box Oauth token: Unable to refresh access token

Darned if I can figure out what the configuration issue is on either side...

Does anybody have experience getting group provisioning in PING and BOX to work, that can suggest what I might be missing?

Thanks!!

Murtza

December 08, 2017 13:17

I am not familiar with Ping Federate, but after some research I came across this documentation page on Ping Federate. Based on that page, you might have to update the OAuth token and refresh token within the adapter-config file to get the integration working again. I would also suggest reaching out to Ping Identity to get their advice on how to debug this error since they built the Box integration.

mtbrown

December 11, 2017 07:22

Thank you for your reply. My issues were in fact due to some mis-configuration that I had on the PING side. Specifically, we have a multi-node cluster of PING Federate servers, and the version of Ping's BOX connector that we were trying to use did not support a clustered architecture. We're now on our way... Thanks again!

December 11, 2017 15:08

Thanks for updating the thread with the solution!

Comments