Feature #145
closed
Provide an internal authorization mechanism
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
Updated by Paul Kelly almost 15 years ago
- Status changed from Assigned to Ready For Testing
fix in 81f679b87050484d9a7ec7ef55688687119993a1 on the new_iscdhcp_from_edge
Updated by Paul Kelly over 14 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
Updated by Paul Kelly over 14 years ago
- Subject changed from Authorization must be enforced when DNS and DHCP editing is enabled to Provide an internal authorization mechanism
Updated by Ohad Levy over 14 years ago
- Target version changed from 0.1-5 to 0.1-6
Updated by Paul Kelly over 14 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.
Updated by Paul Kelly over 14 years ago
switched to using SHA1 and stole some code from dish
Updated by Paul Kelly over 14 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
Updated by Paul Kelly over 14 years ago
- % Done changed from 0 to 100
Applied in changeset 7a4ec5cf7cd482e4adac225312aa02dbe82ff561.
Updated by Paul Kelly over 14 years ago
Update wiki and documentation before release
Updated by Ohad Levy over 14 years ago
- Status changed from Ready For Testing to Closed