When the Save & Test Connection actually tests connectivity

[IAM]

So I noticed that for AD connection, when I click Save & Test Connection, it will actually test the connection and let me know if it is successful or failed. But with REST connections, I can have the completely wrong hostname and as long as the JSON is formatted correctly, it will tell me it is successful.

In order to accurately rely on this button, I would like to know which connection types actually test the connection, and which just check to see the JSON is formatted correctly.

[stevemcg9899]

Yes, the inconsistency in behaviour is incredibly frustrating and you have question whether anyone is performing any UX testing on this product.

What's interesting is that after adding in a valid ConnectionJSON string, and after hitting the 'Save & Test Connection' button,  I can see from my target endpoint logging that Saviynt is hitting the resource correctly, but even then I receive 'Error While Test connection: Connection Failed'.

It's very frustrating.

[SB · Accepted solution]

For REST connector, you will need to define a testConnectionParams block in your connection JSON to be able to validate the connectivity. The same has been mentioned in REST documentation as well. You can refer the below link for the same. (search for testConnectionParams)

https://docs.saviyntcloud.com/bundle/REST-v23x/page/Content/Examples-for-JSON-Construction.htm

[Saathvik · Accepted solution]

For REST connection, By default Save & Test connection button will only validate JSON format if you don't implement testConnectionParams block in your connectionJSON. Below is sample block

      "testConnectionParams": {
        "http": {
          "url": "https://<domain name>/api/v2/users.json",
          "httpHeaders": {
            "Authorization": "${access_token}"
          },
          "httpContentType": "application/json",
          "httpMethod": "GET"
        },
        "successResponse": [],
        "successResponsePath": "",
        "errors": [
          "Couldn't authenticate you"
        ],
        "errorPath": "error"
      }

 For details refer Rest Developers Handbook 

[stevemcg9899]

Having the answer squirreled away in your documentation provides some clarity, but don't you guys think it would be useful to add some UI affordance to the button (or vicinity) so this is made clear to the user?

You could even add some validation to the form so that if the testConnectionParams block is added, then the option to test the connection becomes visible.

Conflating both 'Save & Test Connection' to the same button leads to confusion and neither of you guys acknowledge this as the core problem.

No doubt you'll ask me to raise an ideas request for this.

[SB]

Displaying on the UI would definitely provide a better user experience. Creating an Idea would be more viable approach as the Product team has direct access to those ideas and for any additional feedback/inputs for improvement, they can reach out to you over the same. It provides visibility to other Saviynt users as well on improvements being discussed and a platform to also share their inputs.

[stevemcg9899]

The thing is, you are employed by Saviynt, and if you spot an opportunity to fix something or acknowledge a usability issue surely it's in your interest (and Saviynt's interest) to report this back to the product team on behalf of your customers? 

Why can't you submit an ideas request and put the idea ID on this thread for the benefit of everyone? The feedback loop seems broken 😞

I have reported this to our CSM too.