Project

General

Profile

Feature #145

Provide an internal authorization mechanism

Added by Paul Kelly over 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Paul Kelly
Category:
Authentication
Target version:
0.1-6
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Before DHCP and DNS management is enabled a login mechanism is required for those sites that do not have LDAP

Add AuthSourceInternal and store passwords in the database

Related issues

Blocks Foreman - Feature #62: Add a Generic DHCP libraryClosed2010-03-152010-03-15

Associated revisions

Revision 7a4ec5cf (diff)
Added by Paul Kelly about 12 years ago

Fixes #145 - Added AuthSourceInternal

Added a password setting facility to the user class for AuthSourceInternal
Switched to SHA1
Changed :ldap to :login
Applied numerous fixes from Ohad Levy
Fixed malformed user page
Switched attr_accessible to attr_protected
Swiched prepare_password to a before_validation, otherwise validations will fail
Lots of test fixes!

Revision 686cb440 (diff)
Added by Ohad Levy about 12 years ago

requireing the sha1 library, refs #145

Revision 185db7c5 (diff)
Added by Ohad Levy about 12 years ago

refs #145, cleanup test

History

#1 Updated by Ohad Levy over 12 years ago

  • Target version set to 0.3

#2 Updated by Paul Kelly over 12 years ago

  • Status changed from Assigned to Ready For Testing

fix in 81f679b87050484d9a7ec7ef55688687119993a1 on the new_iscdhcp_from_edge

#3 Updated by Paul Kelly over 12 years ago

  • Target version changed from 0.3 to 0.1-5
  • Branch set to feature/145-AuthSourceInternal

I have ported the edge code to develop
Tested the migrations, on-the-fly registration and password changing.
This is not made mandatory and is not used if settings lDAP is not enabled
Creates an internal "root" account

#4 Updated by Paul Kelly over 12 years ago

  • Subject changed from Authorization must be enforced when DNS and DHCP editing is enabled to Provide an internal authorization mechanism

#5 Updated by Ohad Levy about 12 years ago

  • Target version changed from 0.1-5 to 0.1-6

#6 Updated by Paul Kelly about 12 years ago

Fixed the code for 1.5 compatibility
Added some tests

I suggest that we change the name of SETTINGS[:ldap] to SETTINGS[:login] as it is currently misleading.

#7 Updated by Paul Kelly about 12 years ago

switched to using SHA1 and stole some code from dish

#8 Updated by Paul Kelly about 12 years ago

Added many improvements from Ohad
Many test fixes
Fixed issue where attr_accessible was breaking the logic
Switched to using attr_protected
Swiched prepare_password to a before_validation, otherwise validations will fail

#9 Updated by Paul Kelly about 12 years ago

  • % Done changed from 0 to 100

#10 Updated by Paul Kelly about 12 years ago

Update wiki and documentation before release

#11 Updated by Ohad Levy about 12 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF