kclifford20

I've reduced our attributes down to the below and still getting the same error, however not seeing any stack trace in laravel.log this time. userPrincipalName -> userName jobTitle -> title...

I've just updated to 6.0.1, each time I attempt a provisional sync, it rejects the attempt with the same error. We are not able to deserialize the resource received from...

> We have tested this with Azure AD SCIM. There are some fields we had to pull because _Azure_ is not adhering to the SCIM protocol standards, but we have...

Unsure if doing the below will bring your changes over to my staging instance, but I'm still getting errors updating existing people in Snipe via SCIM. git checkout develop git...

Not sure if you've fixed your issue yet, however try the below URL for your HEC URL (Not the dash not dot between http-inputs and __customertenant__ to fix the SSL...

@spalessandro Did you find a fix for this? We've got the same issue. I can see in the logs on the azure function side that the queue is getting call...

> @kclifford20 No, we still haven't found a fix. Still no data on Splunk. Could you please share where did you find the logs on azure about the queue getting...

> Were you able to successfully create and list the subscription on the Azure side? https://github.com/splunk/azure-functions-splunk/tree/master/graph#3-create-a-microsoft-graph-subscription I have a feeling it's to do with Splunk having invalid certificates on the...

@spalessandro With some help from our Splunk reps, we've found a fix. The problem is that the default HEC inputs URL has a SSL certificate issue. This blocks the scripts...

@JasonConger Could you please update the docs with the example HEC URL?