From 0e94e1848569e7c3f4e626a4c0988a23b12d1ffb Mon Sep 17 00:00:00 2001 From: Matt Scott Date: Mon, 20 Feb 2023 11:25:25 -0500 Subject: [PATCH] Working on first-round updates for the authentication settings view. --- .../admin_setting_authentication.html | 1070 +++++++++-------- 1 file changed, 586 insertions(+), 484 deletions(-) diff --git a/powerdnsadmin/templates/admin_setting_authentication.html b/powerdnsadmin/templates/admin_setting_authentication.html index 9705169..a3060fd 100644 --- a/powerdnsadmin/templates/admin_setting_authentication.html +++ b/powerdnsadmin/templates/admin_setting_authentication.html @@ -53,7 +53,7 @@ OAuth
  • - Github + GitHub OAuth
  • @@ -68,31 +68,48 @@
    -
    - - -
    -
    -

    Basic Settings

    -
    -
    -
    - - +
    +
    + + + +
    +
    +

    Basic Settings

    +
    +
    +
    + + +
    +
    + + +
    + +
    -
    - - + +
    +
    +
    +
    +

    Settings Help

    +
    +
    +

    Fill in all the fields in the left form.

    -
    - +
    @@ -117,7 +134,6 @@
    - GENERAL
    -

    LDAP Settings Help

    +

    Settings Help

    @@ -532,7 +548,6 @@ keep their existing associations and their current Role. -
    • @@ -546,15 +561,17 @@
    -
    -
    -
    -
    - - +
    + + + +
    +
    +

    Google OAuth Settings

    +
    +
    - GENERAL
    Save
    - +
    -
    +
    -
    +
    -

    Help

    +

    Settings Help

    Fill in all the fields in the left form.

    @@ -655,89 +672,107 @@
    -
    +
    -
    - GENERAL -
    - - +
    +
    +

    GitHub OAuth Settings

    -
    - - - +
    +
    +
    + + +
    +
    + + + +
    +
    + + + +
    +
    +
    + ADVANCE +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    +
    + +
    -
    - - - -
    -
    -
    - ADVANCE -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    -
    -
    -
    - Help -

    Fill in all the fields in the left form.

    +
    +
    +
    +

    Settings Help

    +
    +
    +

    Fill in all the fields in the left form.

    +
    +
    @@ -745,243 +780,287 @@
    -
    +
    -
    - GENERAL -
    - - +
    +
    +

    Microsoft OAuth Settings

    -
    - - - -
    -
    - - - -
    -
    -
    - ADVANCED -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    -
    - GROUP SECURITY -
    - -
    - -     - +
    +
    +
    + + +
    +
    + + + +
    +
    + + + +
    +
    +
    + ADVANCED +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    +
    + GROUP SECURITY +
    + +
    + +     + +
    +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    +
    + AZURE GROUP ACCOUNT SYNC/CREATION +
    + +
    + +     + +
    +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    +
    +
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    -
    - AZURE GROUP ACCOUNT SYNC/CREATION -
    - -
    - -     - -
    -
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    -
    -
    -
    - Help -

    Fill in all the fields in the left form.

    -

    You first need to define an Application Registration in your Azure - Active Directory, with the appropriate HTTPS URL for this endpoint, - and with the appropriate rights, as explained in the - documentation.

    -

    -

      -
    • Under the Azure Active Directory, select App Registrations, and - create a new one. Give it any name you want, and the Redirect - URI shoule be type 'Web' and of the format https://powerdnsadmin/azure/authorized - (replace the host name approriately). -
      • -
    • Select the newly-created registration
      • -
    • On the Overview page, the Application ID is your new Client ID - to use with PowerDNS-Admin -
      • -
    • On the Overview page, make a note of your Directory/Tenant ID - - you need it for the API URLs later -
      • -
    • Ensure Access Tokens are enabled in the Authentication section -
      • -
    • Under Certificates and Secrets, create a new Client Secret. Note - this secret as it is the new Client Secret to use with - PowerDNS-Admin -
      • -
    • Under API Permissions, you need to add permissions. Add - permissions for Graph API, Delegated. Add: email, openid, - profile, GroupMember.Read, User.Read and possibly User.Read.All. - You then need to grant admin approval for your organisation. -
      • -
    • For the Scope, use User.Read openid mail profile
      • -
    • Replace the [tenantID] in the default URLs for authorize and - token with your Tenant ID. -
      • -
    -

    -

    If AZURE GROUP ACCOUNT SYNC/CREATION is enabled, Accounts will - be created automatically based on group membership. If an Account - exists, an authenticated user with group membership is added to the - Account

    - +
    +
    +
    +

    Settings Help

    +
    +
    +

    Fill in all the fields in the left form.

    +

    You first need to define an Application Registration in your + Azure + Active Directory, with the appropriate HTTPS URL for this + endpoint, + and with the appropriate rights, as explained in the + documentation.

    +

    +

      +
    • Under the Azure Active Directory, select App + Registrations, and + create a new one. Give it any name you want, and the + Redirect + URI shoule be type 'Web' and of the format https://powerdnsadmin/azure/authorized + (replace the host name approriately). +
      • +
    • Select the newly-created registration
      • +
    • On the Overview page, the Application ID is your new + Client ID + to use with PowerDNS-Admin +
      • +
    • On the Overview page, make a note of your + Directory/Tenant ID - + you need it for the API URLs later +
      • +
    • Ensure Access Tokens are enabled in the Authentication + section +
      • +
    • Under Certificates and Secrets, create a new Client + Secret. Note + this secret as it is the new Client Secret to use with + PowerDNS-Admin +
      • +
    • Under API Permissions, you need to add permissions. Add + permissions for Graph API, Delegated. Add: email, + openid, + profile, GroupMember.Read, User.Read and possibly + User.Read.All. + You then need to grant admin approval for your + organisation. +
      • +
    • For the Scope, use User.Read openid mail profile +
      • +
    • Replace the [tenantID] in the default URLs for authorize + and + token with your Tenant ID. +
      • +
    +

    +

    If AZURE GROUP ACCOUNT SYNC/CREATION is enabled, + Accounts will + be created automatically based on group membership. If an + Account + exists, an authenticated user with group membership is added + to the + Account

    +
    +
    @@ -989,158 +1068,181 @@
    -
    +
    -
    - GENERAL -
    - - +
    +
    +

    OpenID Connect OAuth Settings

    -
    - - - +
    +
    +
    + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    +
    + CLAIMS +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    + + + +
    +
    +
    + ADVANCE +
    + + + +
    +
    + + + +
    +
    +
    + +
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    -
    - CLAIMS -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    - - - -
    -
    -
    - ADVANCE -
    - - - -
    -
    - - - -
    -
    -
    -
    -
    - Help -

    Fill in all the fields in the left form.

    +
    +
    +
    +

    Settings Help

    +
    +
    +

    Fill in all the fields in the left form.

    +
    +