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