Security Disabled - How to reset security

[llsempro]

We only have one user ID / password set-up in our repository environment as we are just getting it set-up.  The user ID belongs to the admin role.  I was in the process of creating other user groups to restrict access for general users.  Somehow, I must have disabled security in the admin role, because when I log-in as admin, the "Enable Security" option under the Configure Menu - Manage Security Drop-down is greyed out.  I don't even have the option to select "enable" security to do anything.  Has anyone else encountered this and know how to reset it?

[Uffe]

If security is enabled and you're logged in as a user without the Security - Enable/Disable permission, the Enable Security menu item will be disabled but the key icon will be enclosed in a box.

There is no special handling for the "admin" user, so it is quite possible to remove the necessary administration permissions from your admin user or group and thus lock yourself out. If that is the case, the simple solution is to create a new project. There is no "reset security" function. (That would be poor security.)

/Uffe

[Geert Bellekens]

Or you can change the setting directly in the database

Geert

[llsempro]

Thanks Uffe - Sadly, this is in our cloud connection repository - I can't create another project there.  Any other advice? 

[llsempro]

@ Geert -
Any familiarity with Sparx db schema to point my DB admin in right direction?

[qwerty]

Just tell him to clear t_secpolicies. That will disable security.

q.

[Uffe]

Hacking the database manually is in no way supported by the vendor. What you should do is restore a backup from before the project was broken.

That said, t_secpolicies is a simple property/value table. Clearing it, or selected rows in it, should remove security altogether and allow you to re-enable it which should recreate the default "admin" user.

But I don't know what's gone wrong with your project, it's impossible to tell just from what you describe. There are many other components that come together to make an EA deployment. Cloud connections are one complication, for instance, and there are several others. Only you know what decisions you made in your deployment.

So I make no promises and take no responsibility. You are completely on your own here.


/Uffe

[Graham_Moir]

FYI, this appears to have been fixed/reset by updating the t_secpolicies table and disabling the UserSecurity Property.