Refactor #390

Ensure that a user account is always selected

Added by Paul Kelly about 4 years ago. Updated about 4 years ago.

Status:ClosedStart date:09/29/2010
Priority:NormalDue date:
Assigned To:Paul Kelly% Done:

100%

Category:Authentication
Target version:0.1-6
Difficulty: Bugzilla link:
Found in release: Pull request:
Story points-
Velocity based estimate-

Description

Later revisions of the foreman code base require that there is always a user account associated with the current session. If logins are enabled then the account is obviously the user's account. If logins are disabled then all activity is associated with the built-in admin account.


Related issues

Blocks Foreman - Feature #332: Provide a notification mechanism Closed 06/25/2010

Associated revisions

Revision f5df7d44
Added by Paul Kelly about 4 years ago

Fixes #390 - A user account is always associated with a session

History

#1 Updated by Paul Kelly about 4 years ago

  • Status changed from New to Feedback
  • Branch set to refactor/390-user-always-selected

#2 Updated by Paul Kelly about 4 years ago

Updated to comply with Ohad's requests and tested some more

#3 Updated by Ohad Levy about 4 years ago

  • Target version set to 0.1-6

#4 Updated by Paul Kelly about 4 years ago

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

#5 Updated by Ohad Levy about 4 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF