shamrickus opened a new issue, #6722: URL: https://github.com/apache/trafficcontrol/issues/6722
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at [email protected] and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request) or the Traffic Control Users mailing list (send an email to [email protected] to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Bug Report affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Control Cache Config (`t3c`, formerly ORT) ## Current behavior: If t3c is running, a cookie has been stored, and then the t3c user changes, t3c will continue using the old cookie even though it's for a different user. Since cookies are refreshed on request, the old cookie will also never expire (assuming t3c is running on a semi-regular cron). <!-- Describe how the bug happens --> ## Expected behavior: A user change to t3c should in someway invalidate the cookie if needed. <!-- Describe what the behavior would be without the bug --> ## Steps to reproduce: Run t3c as a user Change the user it runs as Run t3c again and it uses the old cookie <!-- If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and include the applicable TC version. --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
