authentication per page?

[lance_lyons]

Hi, It seems like every page that we migrate to after authenticating with Jira on the login page, requires us to enter in authentication information again. Almost like every page has its own authentication cookie.

We would prefer to authenticate the first time and any page beneath the jira site, use that initial authentication.

Is there a way to turn this off or have we configured something incorrectly?

[JamieA]

You've configured something incorrectly... difficult to know what without more information. Eg what version of jira do you have, have you customised any files named seraph*, do you have any custom SSO, are you proxying through apache...?

[lance_lyons]

We have customized seraph as recommended by Atlassian, since we are doing SSO via Crowd. We also have proxying happening through apache.

It doesnt seem to happen with all people and if I clear my cookies in the browser, that seems to help as well.

It seems like each page has its own authentication cookie.

[lance_lyons]

Thanks Jamie,

Any other information would be helpful. It seems like right after a user changes their active directory password, we have this problem more (for that user). They will login and then migrate to another page and have to login again. It seems like the login that comes up has pre populated with the user / pw but the password is wrong.

Its almost like different pages have auth data stored in a cookie causing mutliple pages to ask for credentials again even after loging in to Jira at the very beginning of the session.

[JamieA]

Hi... I don't use Crowd. But seems to me that this configuration should be supported by Atlassian...

I've never heard of a different cookie per page, but from your description it sounds somehow feasible.