When a user navigates to the page to create a new calendar entry given an ATLis ID as a parameter, the user will be redirect to login if not already. The login process should redirect users back to the page they originally requested upon successful authentication (due to SSO user may not even be required to enter credentials). What is happening is user is redirected back from auth service to original page without URL parameters.
For example clicking the link in tasklists.jlab.org:
If the user is not already authenticated to Calendar app, they'll be redirect to login and the URL parameters are lost. Going back to tasklists.jlab.org and trying again will work because the user is then already authenticated to Calendar so no redirect to Keycloak auth service occurs.
slominskir
commented
1 year ago
When a user navigates to the page to create a new calendar entry given an ATLis ID as a parameter, the user will be redirect to login if not already. The login process should redirect users back to the page they originally requested upon successful authentication (due to SSO user may not even be required to enter credentials). What is happening is user is redirected back from auth service to original page without URL parameters.
For example clicking the link in tasklists.jlab.org:
Results in a GET request to a URL such as:
https://ace.jlab.org/calendar/edit-event?taskId=12580&calendar_id=1If the user is not already authenticated to Calendar app, they'll be redirect to login and the URL parameters are lost. Going back to tasklists.jlab.org and trying again will work because the user is then already authenticated to Calendar so no redirect to Keycloak auth service occurs.
This issue is a duplicate of https://github.com/JeffersonLab/presenter/issues/3. We're creating a separate ticket to create a link in this repo, but will follow the original issue there.