Bug #4776

Accessing API does not seem to refresh cookie expiration

Added by Justin Sherrill over 3 years ago. Updated over 3 years ago.

Status:Closed
Priority:High
Assigned To:Brad Buckingham
Category:API
Target version:Sprint 22
Difficulty:easy Bugzilla link:
Found in release: Pull request:
Story points-
Velocity based estimate-
Release1.5.0Release relationshipAuto

Description

Browsing around and staying on katello pages seems to cause the cookie expiration to not be extended, ignoring the idle timeout


Related issues

Related to Foreman - Bug #4895: API should check for the presence of a CSRF token when th... Closed 03/26/2014

History

#1 Updated by Mike McCune over 3 years ago

  • Triaged set to Yes

#2 Updated by Mike McCune over 3 years ago

  • Triaged deleted (Yes)

#3 Updated by Mike McCune over 3 years ago

  • Status changed from New to Assigned
  • Assigned To set to Brad Buckingham
  • Triaged set to Yes

#4 Updated by Dominic Cleal over 3 years ago

  • Project changed from Katello to Foreman
  • Category changed from Web UI to API
  • Status changed from Assigned to Ready For Testing
  • Target version set to Sprint 22
  • Release set to 1.5.0

#5 Updated by Dominic Cleal over 3 years ago

  • Subject changed from Accessing katello controllers does not seem to refresh cookie expiration to Accessing API does not seem to refresh cookie expiration

#6 Updated by Dominic Cleal over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#7 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #4895: API should check for the presence of a CSRF token when there is a session user added

Also available in: Atom PDF