-
Suggestion
-
Resolution: Unresolved
Problem Definition
Customers might need to disable the crucibleprefs1 and / or remember browser cookies completely, or at least shorten their lifespans.
Currently there is no way to do that in Fisheye.
Suggested Solution
Create JVM System Properties that allow doing that.
Workaround
Please note
This workaround has been tested against Fisheye / Crucible 4.6+
Use Byteman rules to do that. Thus far, we have only found out how to shorten the lifespan of the crucibleprefs1 cookie, we were unable to find out how to do the same for the remember cookie, which then needs to be disabled completely.
Byteman rule to shorten the lifespan of crucibleprefs1 to 1 day:
RULE Change crucibleprefs1 age to one day CLASS com.cenqua.fisheye.web.PreferenceManager METHOD makeCookie AT EXIT IF true DO $cookie.setMaxAge(86400); org.slf4j.LoggerFactory.getLogger("Byteman").info("Cookie 'crucibleprefs1' lifespan has been shortened to: " + $cookie.getMaxAge()); ENDRULE
Byteman rule to disable the remember cookie completely:
RULE com.cenqua.fisheye.user.DefaultUserManager#loginWithSanitizedUserName entry CLASS com.cenqua.fisheye.user.DefaultUserManager METHOD loginWithSanitizedUserName AT ENTRY IF true DO $5 = false; org.slf4j.LoggerFactory.getLogger("Byteman").info("Cookie 'remember' has been disabled"); ENDRULE
Enabling Byteman in Fisheye:
Please see Enable Byteman for additional logging in Fisheye and Crucible
Hi everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.
We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Kind regards
Marek Parfianowicz
Development Team Lead