'There was a problem activating identity management' when setting up SCIM with JumpCloud

[leighgallagher]

When trying to set up SCIM on JumpCloud, I get a message saying 'there was a problem activating identity management'. I reached out to JumpCloud support and they said they had a customer with a similar issue previously which was resolved by the Snipe-IT support.

I have tried various renditions of the API key, including the bearer prefix etc, but nothing works. I noticed someone else had the same issue on discord, but couldn't find the solution

[snipe]

Can you show us a screenshot of your Jumpcloud settings (with only the actual bearer token and your Snipe-IT url hidden, but leave in the Bearer part). (Also I assume you've already checked the SCIM configuration page in the docs.)

[uberbrady]

Make sure your api token is for a superuser. It won't work otherwise.

[leighgallagher]

I have checked the documentation yes, the API token is also from a super user.

So far everything i've tried:
API key copied from snipe and https://your_servername/scim/v2
API key copied from snipe and https://your_servername/scim/v2/ (forward slash on the end)
API key with "Bearer " prefix and https://your_servername/scim/v2
API key with "Bearer " prefix and https://your_servername/scim/v2/ (forward slash on the end)
API key with "Authorization: Bearer " prefix and https://your_servername/scim/v2
API key with "Authorization: Bearer " prefix and https://your_servername/scim/v2/ (forward slash on the end)

I also had a call with JC where I was screen sharing with their support, they said that the response on their backend was showing something of the ilk of an incorrect character error, but we tried every combination above, even pasting the api key into a notepad and copying from there, but still no luck

Let me know if this screenshot is what you were looking for or if i misunderstood

[uberbrady]

They seem to have some docs for how to integrate with us - https://jumpcloud.com/support/integrate-with-snipe-it - It seems pretty straightforward? Seems.

Their docs seem to imply you don't need to prepend "Bearer".

Another thing you can try is to set SCIM_TRACE to true in your .env - and then see if you get any output in storage/logs/scim.log - or in storage/logs/laravel.log. Might also be smart to take a look at your webserver's logs (Apache or nginx most commonly) - to see what URL is actually coming in, or what responses are being sent.

This normally is pretty easy to do - I'm wondering if something else is wrong in your Snipe-IT installation? Maybe something with your APP_URL in your .env is somehow getting in the way?

JumpCloud

Integrate with Snipe-IT

Browse the JumpCloud Help Center by category, search for a specific topic, or check out our featured articles.

[leighgallagher]

This has now been resolved, it was a firewall issue

[uberbrady]

Great news! Glad you got it figured out.