Bug: da_sso_<ID> user does not belong to you when deleting a database

[k1l0b1t]

When deleting a database, I get the following error:

Error deleting database(s)​

The user da_sso_3uiuKotcj does not belong to you

Database is deleted (at least, as far as I can see).
SSO user does not get deleted.

To reproduce: create database, log in to sso (just that db's sso user), close phpmyadmin and delete the database.

DA version 1.62.4, Cent7, MariaDB 10.5

@smtalk

 

[k1l0b1t]

nobody with this issue/bug?

 

[ben29]

Try reset da_admin

Version 1.61.4 | Directadmin Docs

DirectAdmin Knowledge Base

www.directadmin.com

if it's still happen
it mean something to user Privileges

let us know here

 

[k1l0b1t]

still happening...

I did notice the entries get deleted eventualy though. the mysql.user table is not filling up with random sso users, they seem to clear up at night though.

 

[Mr. Jinx]

Same here:

1. Created a DB
2. Login to phpmyadmin with SSO
3. Return to DA and delete the DB

 

[DirectAdmin Support]

Popup Error Message when Deleting database on Server

Hi, On a test DA server I created a new DB named admin_1234 then deleted it a few minutes later. The strange thing is that the DA Gui popped up an error message after the deletion stating (or see attachment): ERROR DELETING DATABASES The user da_sso_lsuEN7Izt does not belong to you Seems like...

forum.directadmin.com

FYI, should be fixed in the "alpha" binaries now.
It will be in the next release (after 1.63.5), as 1.63.5 is already locked in the release candidate phase.

Also, after testing, it does look like the DB and all normal Users are correctly being deleted.
The da_sso_* users are all listed in a file, so should in theory be cleaned up by the dataskq after they expired.

John

 

[k1l0b1t]

Awesome. Yeah I did notice they're getting deleted by datasq at midnight.