Integration JIRA and Citrix Netscaler

[Ulrika Eriksson]

Hi,

Maybe you can come up with any idea how to configure JIRA, so the page is reloading to loginpage when logout is triggered without a user reload the page?

This case:
1. User timed out from JIRA.
2. The page is still the same (where the user was when leaving the computer/JIRA) until the user click somewhere in the JIRA Window. The user can be away from computer a long time, then cookies are not cleaned.
3. The user reloads the page and are logged out (gets permission violation). But when clicking on Agile menu (JIRA Agile) or Test Sessions (JIRA Capture), the user are still logged in to JIRA i.e. If JIRA is timed out, and a user is clicking on "Agile" after timeout, before reload. The user is still logged in to JIRA (without login to JIRA again).

---- What we want is that the page is changed to logout page automaticly and directly after timeout. And it is the first time netscaler is logged out and cookies are cleaned!

We want the step "reload page"/change to logout page/back to login page be triggered directly, without user doing anything after timeout, since the user will be away from computer for a long time.

Another way of describing the problem:
If the user keeps the browser open until the session expires and then clicks
any of the portal links like (Agile, TestSessions), he/she should be redirected to the login page.
Instead, the link is followed and, depending on security, certain portlets are
now shown with "You have no view permission" message. The user should be
redirected to login page and message "Session expired, please login again"
should be displayed.

[Ronan O'Brien · Accepted solution]

You need to look at what the request looks like when the session has expired. I am not familiar with the JIRA platform, but if it uses a cookie with an expiry time set, then the browser should not send the cookie once it has expired. You can tell NetScaler that if this cookie doesnt exist, then redirect the users request to the login page.

The config below will do just that.

add responder action redirect-to-login redirect "\"http://www.site.com/login.htm\""

add responder policy If-JIRA-session-Expires "http.REQ.COOKIE.CONTAINS(\"JIRA-Cookie\").NOT" redirect-to-login

[Andreas Petzel]

your netscaler logon time-out needs to be shorter then your jira logon timeout. then your NetScaler cookie will be gone before the backend is already loging out.

but you will need to tell the backend that you are loging out when NetScaler reaches its timeout.

[Ulrika Eriksson]

It was a good start, but does not solve the problem. Need to delete cookies a certain time (when time out is happening).