SSO (Form-Login) - Paths in seraph-config.xml

[Patrick Patrick]

I want to use our SSO for JIRA 4.3.4.

Therefore i've customized login.url, link.login.url, logout.url in the seraph.xml.

But it doensn't work in all cases. For URL's with jira/browse/... it works. For jira/secure/Dashboard.jspa it does'nt work.

Is there any detailed description for this? The documentation under http://docs.atlassian.com/atlassian-seraph/latest/ does'nt help.

- - - - -

SSO works, it's a problem with the Login-Page.

Works means:

For URL's with jira/browse/... our own login-Page were shown.

For URL's with jira/secure/ (e.g. Dashboard.jspa) the JIRA-Login-Page (and not our own) were shown.

We want our own Login-page for all URL's and therefore we changed the login.url, link.login.url, logout.url in the seraph-config.xml.

[Jan-Willem Veldhuis]

Although not a complete solution, I figured out it is possible to disable the display of the login form.

This will prevent users from logging in using the internal authenticator.

<tt>In $JIRA_DATA/jira-config.properties </tt>add

jira.disable.login.gadget = true

In <tt>$JIRA_HOME/atlassian-jira/WEB-INF/classes/jpm.xml</tt>

Change the property to be "user-editable":

<property>
  <key>jira.disable.login.gadget</key>
  <default-value>false</default-value>
  <type>boolean</type>
  <user-editable>true</user-editable>
</property>

[childnode]

perhaps related to https://jira.atlassian.com/browse/CONF-35884

[Melek Jebnoun_Vectors_]

Hi all,

Does any one of you found a solution for this?

We found that even URLs with "/issues" don't redirect to custom authentification. It's not only the /secure/dashboard.jsp that don't work.

Still it's possible to redirect /secure/ to the custom login page by editing the "default.jsp" on the secure directory of your Jira instance.

[Jan-Willem Veldhuis]

Old question, though having the same issue.

Implemented custom SSO, changed the login.url and is working for "/browse" and when clicking explicitly on the Login link at the top-right: it redirects to the custom URL so the users logs in through the SSO solution.

But for /jira/secure pages (for example when a user browses to jira.myserver.com/) the Login Gadget at the Dashboard is shown instead of a redirect to the login page.

How to avoid the display of the Login Gadget at the Dashboard and to force login using the defined login URL?

[Patrick Patrick]

You're right, my explanation isn't clear. SSO works, it's a problem with the Login-Page.

Works means:

For URL's with jira/browse/... our own login-Page were shown.

For URL's with jira/secure/ (e.g. Dashboard.jspa) the JIRA-Login-Page (and not our own) were shown.

We want our own Login-page for all URL's and therefore we changed the login.url, link.login.url, logout.url in the seraph-config.xml.

[twong_atlassian]

Ciould you clarify what you mean by "Works"?

Do you mean you get to the destination URL not logged in, or it just doesn't go anywhere, or etc?

It may be useful to know which SSO solution (as each solution may have interesting characteristics as far as implementation style that could affect the answer) you're trying to implement.