We're running an on-prem instance of Jira and are using Centrify for IdP initiated SAML SSO.
Prior to implementing SSO the embedded links in email notifications worked without issue. The URL users would use to access the system was, for example, http://servername:port and the generated embedded hyperlink for notifications, for example, http://servername:port/browse/etc.
That URL changed when implementing SSO to a Centrify generated appkey that redirects to http://servername:port. With SSO up, if the user already has an authenticated Jira session running and clicks on a hyperlink in an email they will resolve to the target location without issue. However, if the user does not have a Jira session running and they click on a hyperlink in an email it fails, because it's attempting to authentication to the old URL of http://servername:port/browse/etc, circumventing the SSO / new URL.
How/where can I configure the construction of the links to edit it from http://servername:port/browse/etc to http://centrifyappkey/logic/browse/etc.?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event