Hi, recently migrated a version of our Jira instance to a new server. When I go to the instance it's redirecting me to our single sign-on instance & then sending me into our production environment. I just want to disable the redirection so I can confirm our migrated instance is in working order.
Thanks in advance.
It seems like you pointed new JIRA Server to the same database(or clone of the prod database) and that's the reason, you are always redirected to the production instance after SSO.
In case if you are using the third party plugin then you can temporarily disable the SSO plugin on server startup so that you will be able to login using your JIRA Credential and once logged in, enable the SSO plugin and update its configuration.
Here are the commands to disable the plugin.
Linux:
$ ./start-jira.sh --disable-addons=<add-on key (for example com.atlassian.test.plugin).>
Windows:
start-confluence.bat /disableaddon=<add-on key (for example com.atlassian.test.plugin).>
In case, if you are using SSO plugin from miniOrange. Please reach out to atlassiansupport@miniorange.com for further assistance.
Thanks,
Lokesh
Full disclosure: I work for the miniOrange. We are the Atlassian Marketplace top vendor.
Hi!
which 3rd party plugin do you use for SSO or do you use the SAML in DataCenter?
cheers,
Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
that is a networking/configuration issue. All the traffic may be redirected to the SSO server. They are going to have to setup a bypass for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wouldn't there be a local configuration setting to disable SSO & just use the built-in login page?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I haven't setup JIRA for SSO, but other things I have the DNS points to the SSO server and then that server forwards the request and header information to the application. JIRA wouldn't get involved until AFTER the SSO server is hit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.