Web application addresses
A familiar link to your internal web application.
Give your team an HTTPS link to the web application. The connector forwards requests to the server inside your network. Use a BusinessProxy address or connect your own domain.
The addresses used to reach your web application
Example
| Address | Purpose |
|---|---|
app-7c24.business-proxy.com | A unique system address for the published web application. |
app.example.org | A domain you verify: a familiar link for your team. |
http://192.168.10.20:9080 | The server address inside your network, reached by the connector. |
Access is checked before the web application opens
BusinessProxy identifies the web application from the URL and checks whether the administrator has granted the user access. The connector then forwards the request to the internal server.
The system hostname is unique within business-proxy.com. Your own domain can use a shorter web application name, such as app.example.org.
What to check when publishing
Set the external HTTPS URL in the web application when it generates absolute links. Test sign-in, sign-out, assets and WebSocket connections.
Keep it private or restrict direct access. Publishing a managed address does not automatically close other entry points.
Assign access to a user or a supported group. Knowing the URL does not grant permission to open the web application.