Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support connecting to ROS using a self-signed certificate #373

Closed
kraenhansen opened this issue Nov 6, 2017 · 1 comment · Fixed by #393
Closed

Support connecting to ROS using a self-signed certificate #373

kraenhansen opened this issue Nov 6, 2017 · 1 comment · Fixed by #393
Labels
Blocked This issue is blocked by another issue

Comments

@kraenhansen
Copy link
Member

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.

@kraenhansen kraenhansen changed the title Connecting ROS using a self-signed certificate Support connecting to ROS using a self-signed certificate Nov 6, 2017
@kraenhansen kraenhansen added the Blocked This issue is blocked by another issue label Nov 6, 2017
@kraenhansen
Copy link
Member Author

@kneth pointed me in a direction that unblocked me from realm/realm-js#1464

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Blocked This issue is blocked by another issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant