Bug: Corrupt private credential visible for everyone / private folder visible

[thogud]

Hi

We just had a issue with a new credential for a colleague.
He created a new private credential.

This ended up corrupt/with encryption issues. Making it visible for everyone and I got the typical error message when starting ASG-RD stating there is one or more invalid/corrupt/uncrypted credentials.

He fixed the credential now and it is not visible anymore for all the other users. However his private folder still is (even after I tried to restarter ASG-RD).

Seems like some security/visibility bug will occur if a private credential gets corrupt?

kegj is a private folder for his user. And I can verify it still states Private from my admin account, however every user can see it, so seems it got bugged and acts like a public folder.

Before he fixed his private credential from a normal user:


Before he fixed his private credential as a new login from my admin account:


After he fixed it for both me as admin + other users:

[DevOma]

I don't know how it is possible but I try to show you some SQL commands to correct

First try to get the row for the private folder

SELECT * FROM Items WHERE Text = 'kegj'

Check the 2 columns "Private" and "UserId" - perhaps it's marked private but there is no UserId? I guess that might be the problem... if yes, please continue...

Copy the ItemId. Now you can get the UserId from table "Users" - so just execute SELECT * FROM Users

Pick up the ID for the right user and replace the ID's in the following command

UPDATE Items SET UserId = %UserId% WHERE ItemId = %ItemId%

[DevOma]

Or the user create a second private folder and move the cred to the new folder :-)

[thogud]

Or the user create a second private folder and move the cred to the new folder :-)

This is what he did, since he did not have anything else in the folder. Wondered why I got no hits on the query, but a refresh in ASG-RD and the folder was gone. He confirmed he deleted it as other colleagues had told him we could see the folder

Well, at least you know about the bug now, so let's just hope no more corrupt credentials will happen on private ones in the future, hehe.

[DevOma]

Ok - just let me know if this really happens again!