We can click the link and launch jira from okta, but users clicking links from email or chat are getting 404 before they're authenticated. I need them to authenticate automatically.
<param-name>login.url</param-name>
<param-value>http://domain.okta.com/login?redirectTo=${originalurl}</param-value>
<param-name>link.login.url</param-name>
<param-value>/login.action</param-value>
<param-name>logout.url</param-name>
<param-value>https://domain.okta.com</param-value>
We had it configured previously before updating the server. the new admin (me) didn't backup the seraph-config.xml file. And no i cannot recover from the old backup, i have to set it up new and document the process to pay my penance.
The 404 link: https://domain.okta.com/login?redirectTo=https://connect.domain.com/browse/Ticket-223
I should have been more clear in my original post. in the script i have my domain 'company name' filled in. i redacted that information because it didn't want to broadcast it to the internet.
<param-value> http://[Redacted}.okta.com/login?redirectTo=${originalurl}</param-value>
I am looking for is the proper syntax to get the SSO working.
I think this is what you need to get up and running again: https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Jira-On-Premise-SAML.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.