Commit Graph

169 Commits

Author SHA1 Message Date
Khanh Ngo
3457d9214a Adding Operator role 2018-08-31 11:57:06 +07:00
Khanh Ngo
07e1bcdc47
Bug fixes. Adjustment in user input validation 2018-08-25 14:53:10 +07:00
Khanh Ngo
b338b64795
Update basic help for setting section 2018-08-22 17:45:37 +07:00
Khanh Ngo
421ea627d8
#237. Allow LDAP user to use OTP 2018-08-22 09:43:33 +07:00
Khanh Ngo
9506315a46 manage records_allow_to_edit setting in DB 2018-08-22 08:36:53 +07:00
Khanh Ngo
74a7b5a3b7 Migrate more config values to db 2018-08-21 13:26:27 +07:00
Khanh Ngo
8af7a6ac9e
Adjustment in travis ci configs. Fix importing during first time running db upgrade 2018-08-20 17:21:32 +07:00
Khanh Ngo
0b7580c82f
Read powerdns api setting from DB 2018-08-20 09:59:19 +07:00
Khanh Ngo
f8f4ddcc85
Add validation for authentication setting form 2018-08-19 22:08:14 +07:00
Khanh Ngo
babf62bae0
Fix Github/Google oAuth 2018-08-19 15:29:50 +07:00
Khanh Ngo
ada6f844ff
Read LDAP config from DB instead of file. Adjustment in site titles 2018-08-18 22:42:18 +07:00
Khanh Ngo
4b9349c83e
Create DB config for pdns and authentication setting 2018-08-18 18:41:59 +07:00
Khanh Ngo
7b5c74cc7d
Merge pull request #330 from tmuncks/add-user-edit
Add option to edit users from the comfort of the UI
2018-08-14 08:52:20 +07:00
Thomas M Steenholdt
fe4616d609 Do user.otp_secret check properly 2018-08-13 01:33:29 -02:00
Thomas M Steenholdt
539e6bc562 Fix double refresh when activating 2FA
When toggling Two Factor Authentication, it often takes a few tries to get it to work.
The toggle function ends up reloading the page in two different places, effectively creating a race condition.

This fixes that problem

(cherry picked from commit 6b9fc897bc02ff857a968e76ed49f1b0f2108bb5)
2018-08-12 07:48:34 -02:00
Thomas M Steenholdt
0ac33aa3c4 Add option to edit users from the comfort of the UI
Update user management feature to allow editing user details directly in the admin user interface.

Also added an option to reset the two factor authentication data of a user, for when that's needed (lost device, technical issues etc).

(cherry picked from commit 3139616282a18c11463c6ecf78888417b2ac1c35)
2018-08-12 07:47:37 -02:00
Khanh Ngo
178e25f8f7
Fix domain table modal to prevent removing several record at the same time 2018-07-05 13:58:27 +07:00
Khanh Ngo
d9baaa4d60 Fix #302 2018-07-05 09:57:08 +07:00
Thomas M Steenholdt
31305a3048 Add setting to allow/disallow quick editing of records
Adds an `allow_quick_edit` setting, using the improved setting handling logic from PR #287 to toggle whether records are editable by simply clicking the row or not.

Aims to fix #288
2018-06-24 00:25:33 -02:00
Thomas M Steenholdt
6c8a3ac36c Move setting definitions into code (rather than database).
For a setting to be useful, the code has to be able to make sense of it anyway. For this reason it makes sense, that the available settings are defined within the code, rather than in the database, where a missing row has previously caused problems. Instead, settings are now written to the database, when they are changed.

So instead of relying on the database initialization process to create all available settings for us in the database, the supported settings and their defaults are now in a `defaults` dict in the Setting class. With this in place, we can stop populating the `setting` table as a part of database initialization and it will be much easier to support new settings in the future (we no longer need to do anything to the database, to achieve that).

Another benefit is that any changes to default values will take effect automatically, unless the admin has already modified that setting to his/her liking.

To make it easier to get the value of a setting, falling back to defaults etc, a new function `get` has been added to the Setting class. Call it as `Setting().get('setting_name'), and it will take care of returning a setting from the database or return the default value for that setting, if nothing was found.

The `get` function returns `None`, if the setting passed to the function, does not exist in the `Setting.defaults` dict - Indicating that we don't know of a setting by that name.
2018-06-21 22:06:38 -02:00
Khanh Ngo
c2df132040 Merge remote-tracking branch 'kaechele/use-webassets' 2018-06-13 09:58:15 +07:00
Khanh Ngo
aa6909065d Merge remote-tracking branch 'tmuncks/initial-accounts' 2018-06-12 16:17:55 +07:00
Felix Kaechele
1bf869f508 Add webassets support
Also updates AdminLTE to latest stable version.

Signed-off-by: Felix Kaechele <felix@kaechele.ca>
2018-06-11 21:16:28 +02:00
Jeroen Boonstra
689b25817c Add action to dialog 2018-06-08 13:25:43 +02:00
Jeroen Boonstra
e334749382 Add dialog for refresh status 2018-06-08 13:25:21 +02:00
Jeroen Boonstra
9732961854 Add refesh button 2018-06-08 13:23:04 +02:00
Khanh Ngo
6f54b1a9de Merge remote-tracking branch 'tmuncks/dnssec-admin-only' 2018-06-07 08:53:01 +07:00
Thomas M Steenholdt
ccec6c37b4 Restrict certain admin changes on the current user
Disable the admin toggle and delete operations from the current user, to avoid accidents.

(cherry picked from commit b0f5ac6df5d31f612dc833a88cfca8936c4137d7)
2018-06-06 09:15:25 -02:00
Thomas M Steenholdt
10f47039ec Add config option to allow DNSSEC changes only for admins
DNSSEC requires changes to the parent domain, which in many cases requires special access to a registry or the like.
For that reason, especially the option to disable DNSSEC can be dangerous - if DNSSEC is disabled in PowerDNS but not in the registry, the domain stops working.

For this reason, adding an option to disable DNSSEC changes for non-admins seems reasonable.

(cherry picked from commit 5cdfc0263b07f4658d51cf7c038fea9a8911152a)
2018-06-06 08:53:44 -02:00
Thomas M Steenholdt
a4af4ad4b3 Implement per account domain access
Added the possibility for assigning users to an account, providing access to all domains associated with that account automatically.

This makes management easier, especially in installations with lots of domains and lots of managing entities.

The old style per-domain permissions are still there and working as usual. The two methods work perfectly side-by-side and are analogous to "user" (per-domain) and "group" (account) permissions as we know them from Active Directory and such places.

(cherry picked from commit 34fbc634d2848a7f76dc89a03dd8c0604068cc17)
2018-06-05 16:42:44 -02:00
Thomas M Steenholdt
a3a58f16a5 Initial support for Accounts
This adds initial support for accounts a concept meant to signify a customer, a department or any other entity that somehow owns or manages one or more domains.

The purpose is to be able to assign an account to any number of domains, making it easy to track who owns or manages a domain, significantly improving manageability in setups with a large number of domains.

An account consists of a mandatory, unique `name` and optional `description`, `contact` name and `mail` address. The account `name` is stripped of spaces and symbols, and lower cased before getting stored in the database and in PowerDNS, to help ensure some type of predictability and uniqueness in the database.

The term *account* is actually taken from the PowerDNS database, where the `domains.account` column is used to store the account relationship, in in the form of the account `name`.

The link to a domain in PowerDNS-Admin is done through the `domain.account_id` FOREIGN KEY, that is linked to the `account.id` PRIMARY KEY.

(cherry picked from commits 4e95f33dfb0676d1c401a033c28bca3be7d6ec26, da0d596bd019a339549e2c59630a8fdee65d0e22, 7f06e6aaf4fd8011c784f24b7bbbba5f52aef319, 1c624dad8749024033d1d15dd6242ca52b39f135)
2018-06-04 13:10:02 -02:00
Thomas M Steenholdt
a7e91b6f40 Fix SOA-EDIT-API options
The options for SOA-EDIT-API included was actually the options used for SOA-EDIT, which is a very different beast.
Those options have been swapped out for the options allowed in SOA-EDIT-API and SOA-EDIT-DNSUPDATE.
2018-05-24 16:12:12 -02:00
Khanh Ngo
3d8d94f280 Validate registration process. Change copyright year. 2018-04-18 13:16:02 +07:00
Khanh Ngo
bd45c4ef87 Adjustment to have History sorts by oldest first. Fix #245 2018-04-18 12:11:00 +07:00
chinkung
be7e012faf
Display history date/time using local timezone 2018-04-17 13:30:08 +07:00
chinkung
34d8e7392c
Display history date/time using local timezone 2018-04-17 13:28:54 +07:00
chinkung
d466a5dd3e
Load moment.js in base.html 2018-04-17 13:26:18 +07:00
Khanh Ngo
01a5528c4a Merge remote-tracking branch 'mind04/template-relative' 2018-04-13 09:25:23 +07:00
Khanh Ngo
52b6966c83 Check zone serial before allowing user to submit their change. #183 2018-04-12 11:18:44 +07:00
Kees Monshouwer
a12af5345d
fix clear history 2018-04-12 02:11:34 +02:00
Khanh Ngo
5354d27f88 Fix #234 2018-04-08 09:09:08 +07:00
Khanh Ngo
ca1290d1ac Change license information 2018-04-02 14:01:35 +07:00
Khanh Ngo
17a892b18d Resolve the conflicts for #228 2018-04-02 13:38:53 +07:00
Khanh Ngo
6fa8ae37f0 Fix #180. Adjustment in table style. 2018-04-01 15:48:08 +07:00
Khanh Ngo
b7aefc57b2 Fix 169: enabling/disabling Two Factor Authentication doesn't work 2018-04-01 14:49:40 +07:00
Khanh Ngo
f172a64ddd Remove DNSSEC modal. Adjustment in domain table css 2018-04-01 14:45:13 +07:00
Khanh Ngo
5df7fe445f Emphasis on zone name 2018-04-01 14:32:20 +07:00
Khanh Ngo
29d1cf4117 Adjustment in domain template feature to work with python3 2018-03-31 08:21:02 +07:00
Khanh Ngo
ce6c3c21f1 Show user email address in user management table 2018-03-31 06:53:57 +07:00
Khanh Ngo
c668c21fc9 Adjustment to prevent exception in Google/Github authentication when local user cannot be created 2018-03-30 17:43:34 +07:00