-
Notifications
You must be signed in to change notification settings - Fork 214
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
Discovery for reverse connect #2186
Labels
Milestone
Comments
This might be difficult due to missing capabilities in the ua stack. I will look into this, for now moving to 2.9.6. Any suggestions or contributions welcome. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We are using the reverse connect feature due to the firewalls protecting our OPC UA servers. Due to the firewalls, a discovery (provided by the REST Api) is not possible. But it would be great, if the REST Api would have a possibility to discovery the reverse connect ReverseHello message of the clients and reporting its endpoint url.
Describe the solution you'd like
An additional /discovery route to discover all clients which sends ReverseHello messages and report its hostname and port (preferable the endpointUrl used within the endpointUrl.
The text was updated successfully, but these errors were encountered: