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
It would be nice if, e.g. in the adapter's configuration message, it would contain a link to the actual service, so we could visit it from the admin's interface (open in new tab).
It would also require an update of the configuration message and adapter configuration (in order to share the link).
The text was updated successfully, but these errors were encountered:
For example, when we attach a COP tool, and I would like to go there and see for myself that it is up and running. Since many solutions will receive a dynamic IP address, it is not easy to find them, so adding a link (if it is available or makes sense) is practical.
In addition, by sharing the adapter's IP address, it allows us to infer which client is using certain services. For example, when a COP tool requests a WMS layer, all the WMS service provider receives is the IP address of the COP tool, not the actual name of the solution. So if the AAR wants to be able to say that the COP tool accessed the WMS service, it needs to infer the service from the IP address. And currently, it does not know the IP address(-es) of the adapters, so it cannot create the link.
It would be nice if, e.g. in the adapter's configuration message, it would contain a link to the actual service, so we could visit it from the admin's interface (open in new tab).
It would also require an update of the configuration message and adapter configuration (in order to share the link).
The text was updated successfully, but these errors were encountered: