canvasdata cli fails with TLS Error

[raj_veeravalli]

Hi all,

Canvasdatacli failed with a TLS error on our instance. See error message below

Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: api.inshosteddata.com. is not in the cert's altnames: DNS:portal.inshosteddata.com

I was able to get things working with a quick change to the apiUrl section of config.js

from

apiUrl: 'https://api.inshosteddata.com/api',

to

apiUrl: 'https://portal.inshosteddata.com/api',

Just me or anyone else run into this? Thought I would mention in case someone's on the same boat.

Edit, update:

Looks like api.inshosteddata.com is configured using the cert for portal.inshosteddata.com

Thanks,

Raj

[James]

 @raj_veeravalli ,

The certificate was updated July 21, 2019, and does indeed point to portal.inshosteddata.com instead of api.inshosteddata.com. I last fetched API data before the certificate was adopted, so I haven't hit the error yet. It would happen in a couple of hours for me, so thank you for pointing it out.

I did check the latest version of the canvasdata cli and it still lists api.inshosteddata.com when you generate a sample configuration, so it would seem to be an oversight / error.

You should probably report this to Canvas support so they can get it taken care of. I have a feeling there will be a lot more noise about it tomorrow if they don't get it fixed.

[raj_veeravalli]

 @James , thanks for checking and confirming it.

I have just notified Canvas support!

[a1222252]

Guys,

I also saw this problem this morning and raised a support request. No response yet.

Regards,

Stuart.

[joshua_lee]

I'm seeing the same issue and have reported it too. 

As noted by James earlier, changing your config file to define the API url as https://portal.inshosteddata.com/api seems to work but the default value is not working.

[millerjm]

Thanks for posting this.  It all worked fine yesterday but not today.  They really need to notify users about this change.  

[raj_veeravalli]

Probably an accident.

dig api.inshosteddata.com

<snip>

;; QUESTION SECTION:
;api.inshosteddata.com. IN A

;; ANSWER SECTION:
api.inshosteddata.com. 244 IN CNAME portal.inshosteddata.com.

I was notified few hours ago that the issue is fixed and was able to run the cli tool by reverting back to the api.inshosted.com domain.