SSL Certificate Add-On - JSON Configuration

[JoeWilks]

Hi all,
I'm trying to add the "key" entry for this for our site but no luck - I've tried emulating the layout in the default json. Does anyone have any pointers on how to add this? I've tried a few combinations.
The site layout is https://gis.<site>/arcgis

So I have tried the key as -

"key": "gis"

"key: "gis.<site>"

as well as anything relating to the SSL certificate. Am I missing something glaringly obvious or do I need to add credentials within Monitor for it to work? As I have tried that as well.

Thanks

[MattD]

Hey Joe,

You might want to check the syntax of your JSON against a JSON validator site such as jsonlint.com

According to the readme pdf included in the application ("SSL certificate.pdf") the URL JSON should be structured like:

{"key":"eslsrv12", "url": "https://eslsrv12:6443}

or

{

   "key":"eslsrv12",

   "url": "https://eslsrv12:6443

}

[JoeWilks]

Hi Matthew,

Thanks for the reply. I've gone over the json layout and see no issues with it, curly Braces, speech marks and commas in the correct place. It works with 1 site which requires no login, but not another which is making me think about either the fault being the key - or maybe credentials held in monitor Administrator to try and login to the portal (which is where I'm trying to check the ssl certificate).

That said, there are also some issues with trying to add a portal counter, so it could be a larger issue. I can login fine with them, the config is correct, so it's a bit of a mystery.

Thank you

Joe

[Anonymous User · Accepted solution]

{
"key": "eslsrv12",
"url": "https://eslsrv12:6443"
},

In the example syntax above, "eslsrv12" is the server name.  Can you ping the server from the ArcGIS Monitor machine using whatever name you are typing in for the key value? Try using a fully qualified name.  If the ArcGIS Monitor machine can't talk to the target server, you may have a DNS issue.

[JoeWilks]

Hi Michael,
Some progress! Just getting a 401 unauthorised error now. All the needed credentials are stored in Monitor and are checked to make sure they are configured correctly. Last hurdle, it seems.

Thank you

[JoeWilks]

Solved it. Required a bit of tweaking with the URL.
Thanks for nudging me in the right direction. Solved! Don't wish to elaborate too much but often times internal URLs are preferred by Monitor.