Skip to main content

We have a model version with 2 applications. For each applicatie a user group (ad) can have different roles. When I apply the rights for a specific application to the database, it seems that the script is not based on the authorizations for the selected application. The scripts for both applications are the same only the use database differs.   

The script is also only adding members and not removing members. When rights are revoked I want to be able to remove the member from that database role. 

Am I using the wrong option or is it creating the wrong script?

Hi Andre,

There are two scripts which can be created. The first one to apply the database roles and one to link users to the roles. For two applications which use the same model, it makes sense that the script to create the database roles are identical. After all, they use the same model and contain the same roles.

The second script applies user rights to the previously created roles on the database. This should be different per application. It should also start off with a section which drops the current role members and obsolete users.

Note that both scripts assume exclusive control of an application over the database. Two applications with the same database but different models will not work for the first script. Two applications using the same database will not work for the second script.

Hi Anne, 

The first script generating the role rights is ok! The second script generates the same output for two different applications of one user group, although the assigned roles for each application is different. Only the database name on top of the script is different. 

So it looks like assigning role members (for each database) is not in the context of an application.  

 

Hi Andre,

That doesn’t seem right, can you submit a ticket for this?

Reply


Terms & ConditionsCookie settings