Description
As a follow on from #6319, we have a user with a single SSO configuration pointed at keycloak, which then further redirects the user to their own SSO endpoint.
However, that redirect requires the user to click through and select their endpoint to get redirected.
If the original URL the user was trying to access (ie, the URL of the Node-RED instance) was to be included as a query param to the original redirect to keycloak, they can then dynamically route the user to the right endpoint.
The request for us is to provide an option to include the url in the request.
- We will need to confirm that would work with keycloak
- Is there a specific query parameter to use?
- Assuming this will need to be an option on the SSO Config as to whether to include the url in the request
This will likely require more discussion with the customer to ensure any proposed solution will work on their side.
Which customers would this be available to
Other (See comments)
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Description
As a follow on from #6319, we have a user with a single SSO configuration pointed at keycloak, which then further redirects the user to their own SSO endpoint.
However, that redirect requires the user to click through and select their endpoint to get redirected.
If the original URL the user was trying to access (ie, the URL of the Node-RED instance) was to be included as a query param to the original redirect to keycloak, they can then dynamically route the user to the right endpoint.
The request for us is to provide an option to include the url in the request.
This will likely require more discussion with the customer to ensure any proposed solution will work on their side.
Which customers would this be available to
Other (See comments)
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate