Supporting dynamic paths for application launch

[gupta-mayank]

We are using OpenSearch and OpenSearch dashboards. For Open search Dashboards (OSD),

1. We use the spaces to support multiple tenants.
2. As we have our authentication application, we use proxy authentication of OpenSearch dashboards (OSD) to launch respective tenants using headers.
3. We use NGINX as a reverse proxy from our application to proxy pass OSD. The NGINX URL is launched from our authentication application.
4. There is a new ask to support URLs containing a tenant-unique ID in our main application. /tenant1 , /tenant2
5. As we use a single instance of OSD ( with spaces for multi-tenant support), we want the OSD to return the tenant ID like tenant1/tenant2 in calls or give a way to dynamically append the base path in the OSD application.
   Is there a way to support this use case?

Describe the solution you'd like

A dynamic way of supporting different mount points or a way to return data from OSD ( headers or otherwise)

A clear and concise description of what you want to happen.

We want to launch OSD using a proxy from different URLs like application/tenant1 or application/tenant2 so that in our NGINX we can pass on the right headers.

A clear and concise description of any alternative solutions or features you've considered.

An alternative, we are still discussing like maintaining a session or storage to check tenant-based launch.

Additional context