summary

Host > SuperUser still shows as Unauthorized after creation

Description

Install latest 7.3.2 build as FQDN site w/remote SQL db
Log in as HOST
Go Host > Advanced Settings > SuperUser Accounts
Click on "Add User"
Enter User Name; Display Name; Email Address
Enter Password (x2)
Leave "Authorize" and "Notify" checked
Click "Add New User"
Now click "edit" to the left of the new SuperUser
View the details in the edit pop up

Actual Result:
At the bottom of the center details column the button reads "Authorize User"

This user is able to sign in with zero issues

Expected Result:
The button should read "Unauthorize User" as this new SuperUser was already authorized when created.

This user is able to sign in with zero issues

Notes:
This behavior works in 7.2.2
It is broken in 7.3.1 and later releases

QA Test Plan

None

Activity

Show:

Ken Grierson

December 1, 2014, 8:28 PM

Ben's code fix merged in 7.3.3

Sebastian Leupold

September 20, 2014, 8:33 PM

we should finally agree to create userportal records for superusers for every portal, this would make database access easier, more efficient and avoid those strange effects

Ben Zhong

September 19, 2014, 1:24 AM

Edited

DNN-5724: host users should always verified.(https://github.com/dnnsoftware/Dnn.Platform/commit/e1d4c6eba9d4e102141badf0c95e194f8a2cc8a8)

Assign to Ash for code review and need pick up to 7.3.3 branch if approved, then also need update "fix in build" field.