-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Current scenario
When using Refined for redirection during login to the JSM Customer Portal, the redirection configured by the Refined application will not be applied during the login phase for portal-only customer users. This is because the login workflow for these users doesn't incorporate the Refined redirection settings.
However, it is important to note that this behavior differs for JSM users with the Agent role, who possess an Atlassian account. The login workflow for these users is distinct, allowing the redirection to function as anticipated.
Expected Outcome
Currently it is an expected behaviour but customer would like to have the redirection possible for portal only customer as well.
[ACCESS-2200] Customer SSO redirect ignores the redirect request
Support reference count | New: 1 |
Description |
Original:
When setting up Refined sites for my organization. We found that using agent SSO (through Entra ID) redirects back to the Refined site correctly, but the customer SSO (through Azure B2C SAML) ignores the redirection request and just serves the JSM portal instead.
Specifically, after a successful authentication, B2C returns to the URL " [https://prod.servicehub.iesve.cloud/servicedesk/customer/sso-redirect?continue=https%3A%2F%2Fiesve.atlassian.net%2Fplugins%2Fservlet%2Fac-redirect%2Fcom.refinedwiki.cloud.refinedsites%2Fservicedesk-portal%3Fac.redirectDomain%3Dies-jsm.refined.site]", however, the continue parameter is ignored and the customer portal is returned (URL "https://prod.servicehub.iesve.cloud/servicedesk/customer"). |
New:
*Current scenario*
When using Refined for redirection during login to the JSM Customer Portal, the redirection configured by the Refined application will not be applied during the login phase for portal-only customer users. This is because the login workflow for these users doesn't incorporate the Refined redirection settings. However, it is important to note that this behavior differs for JSM users with the Agent role, who possess an Atlassian account. The login workflow for these users is distinct, allowing the redirection to function as anticipated. Expected Outcome Currently it is an expected behaviour but customer would like to have the redirection possible for portal only customer as well. |