SCIM provisioning "Test Connection" error

Oleh 26 Reputation points
2021-06-02T09:31:46.747+00:00

I'm trying to configure SCIM application to sync users/groups with our test sever. Our test application is code from https://github.com/AzureAD/SCIMReferenceCode. Also we were able to test it from external locations with postman and can see that our test application works correctly. But, when we trying to setup provisioning in Azure AD and press "Test Connection", we get the next error message:

You appear to have entered invalid credentials. Please confirm you are using the correct information for an administrative account.
Error code: SystemForCrossDomainIdentityManagementCredentialValidationUnavailable
Details: We received this unexpected response from your application:
Message: An error occurred while sending the request.
Please check the service and try again.
Request-id: b7f7971e-4dfb-4f53-ab9d-8a5bc6d380d6

As we can there is no much details in the message, also as we checked on our web server - it doesn't receive any http request from Azure at all.

We use https://our_domain_name/scim/ as a Tenant URL and Secret token field is populated with pure token value.

Microsoft Security | Microsoft Entra | Microsoft Entra ID
{count} votes

Accepted answer
  1. Siva-kumar-selvaraj 15,721 Reputation points
    2021-06-04T16:17:34.557+00:00

    Hello @Oleh ,

    Thanks for reaching out.

    I would recommend you to check, if SCIM solution is compliance with TLS Protocol standard per this guidance also if possible, could you please provide us with recent Request-id along with timestamp which would help me to get more insight from longs. Thanks.

    Hope this helps.

    ------
    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Oleh 26 Reputation points
    2021-06-07T10:18:46.113+00:00

    Hi @sikumars-msft,

    Thank you for pointing us into this direction. We have disabled all SSL/TLS versions bellow TLS1.2, but the main issue, we believe, was with our server SSL certificate - it expired recently and we somehow missed that.

    Now connection works, thanks.

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.