You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because chromes native fetch API does not trust self-signed certificates, Studio is unable to use Realm JS to authenticate with ROS if it's using an untrusted self-signed certificate.
Alternatively, this issue could be fixed by implementing authentication, using a different HTTPs client (possibly node-fetch - which Realm JS actually also uses if fetch is not available natively) to issue the requests with an agent that does not validate certificates or trusts this particular untrusted certificate.
The text was updated successfully, but these errors were encountered:
kraenhansen
changed the title
Connecting ROS using a self-signed certificate
Support connecting to ROS using a self-signed certificate
Nov 6, 2017
Because chromes native
fetch
API does not trust self-signed certificates, Studio is unable to use Realm JS to authenticate with ROS if it's using an untrusted self-signed certificate.This is blocked by realm/realm-js#1464.
Alternatively, this issue could be fixed by implementing authentication, using a different HTTPs client (possibly
node-fetch
- which Realm JS actually also uses if fetch is not available natively) to issue the requests with an agent that does not validate certificates or trusts this particular untrusted certificate.The text was updated successfully, but these errors were encountered: