Multiple JWT tokens
planned
Ravishankar Ananthapadmanabhan
There any many customers who have similar products related to each other and they want these products to be documented as part of the same KB. Thus clients are expecting to use multiple JWT tokens. Kindly facilitate this
Log In
D
D360 Product Management
marked this post as
planned
D
Dusk blue Perch
Our product runs across multiple environments that use different domains for production and non production. Document360 allows only one JWT Sign In URL, so we can authenticate users from only one environment at a time. This limits our ability to make documentation accessible across QA and development environments.
We also use a sandbox workspace, and there is no automated way to keep configuration and reusable items aligned with production. This increases the impact of the single URL limitation.
Support for multiple JWT Sign In URLs is important for ensuring consistent documentation access across all environments. An ETA would help us plan accordingly.
W
Wheat Armadillo
Multi-Tenant JWT settings for KB: I really need this feature, as I manage multiple customers across different domains. It’s essential that JWT logins also support user group's access permissions.
G
Global Crab
My organization needs this feature. It would ensure we can successfully utilize Doc360 across our product suite. Otherwise, we won't be able to deploy across our different applications and justify the value.
D
D360 Product Management
Merged in a post:
Support for Multiple JWT Login Endpoints for Customer Tenants Across Custom Domains
Akash Sivaraman
We need a way to support JWT-based login for customers hosted on separate domains or subdomains. The current login model assumes a single endpoint, which limits flexibility in tenant-specific authentication workflows.
We propose a feature that introduces multi-endpoint JWT authentication support, driven by automatic tenant detection and intelligent fallback behavior.
Expectation
-> Enable customer-specific JWT login endpoints based on tenant/domain.
-> Provide a seamless login experience via automatic tenant detection.
-> Avoid prompting the user for tenant information unless necessary.
Proposed Functionality:
- Automatic Tenant Detection via Referrer URL
-> Detect the origin domain of the login request using the HTTP Referer header.
-> Use the domain to determine the appropriate tenant and corresponding JWT authentication endpoint.
- Query String-Based Tenant Hinting
-> Support a query string parameter (e.g., ?tenant=hype1) to pre-select the tenant.
- Fallback to Manual Tenant/Domain Input
-> If both referrer and query string are unavailable
-> Present a manual input field for the user to specify their tenant domain (e.g., yourdomain.document360.io).
-> Upon validation, redirect to the appropriate tenant login flow.
Mohamed Shakheen
Hi Akash
Thank you for sharing your detailed requirements around supporting JWT-based login for customers hosted on separate domains or subdomains.
To ensure we fully understand your use case and the technical nuances - especially around tenant detection and fallback behaviors - it would be helpful to schedule a call with customer. This will allow us to discuss your expectations in depth and explore the best possible approach to address your needs.
Ramesh Lokesh
One of our customers is using JWT. They want their users to login to their application and then access the KB site. However, they have multiple clients. And they have different URLs for accessing the application in which JWT is configured.
Currently we can configure only one login URL in JWT.
But for the customer's use case, they need the ability to configure multiple Login in URLs in JWT configuration because multiple clients will use different URLs to log into their application and access the KB site.
Kindly check and share your thoughts.
Ravishankar Ananthapadmanabhan
Ramesh Lokesh Yes this is the same requirement
Ramesh Lokesh
Honest Hummingbird Retired Piranha
D
D360 Product Management
Merged in a post:
Support multiple logins in JWT SSO
R
Realistic Galliform
We have multiple customers. In order to validate that the user is valid, we need to receive the organization ID of the customer in the auth URL. We can send this ID in the link that the customer uses to open the document360 page
M
Magenta Jaguar
Magnificent Grasshopper please let me know in case further clarification is required on the use case. Thank you
M
Magnificent Grasshopper
Realistic Galliform Magenta Jaguar thanks for writing us and sharing your valuable suggestions. We need to ensure technical analysis is thoroughly performed on this request before we consider this for implementation.
Appreciate your understanding and patience. Thank you
Load More
→