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.

Thiru please let me know in case further clarification is required on the use case. Thank you

Oren Halevi Sascha Rassenfoss 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

I would like to extend this request in the following way:

it should be possible to setup more than one JWT config simultaneously (each with their own set of client id, secret, auth URL, ..). Reason: we do have multiple source systems and in turn would require different auth callback/forward URL's.

Additionally, we do also have more than one organization in each of these systems, and hence would also need a way to set the callback/forward URL for auth (token refresh) dynamically, in the sense that we shall be able to set a path and query params via the JWT token which need to be appended to the configured 'base' url when the session expires

We have a new prospect innovaccer.com is looking for multiple JWT tokens as his customers are from multiple tenent