Skip to main content
Solved

IAM tasks to apply roles & rights: how to workaround 2 applications on same db


Freddy
Forum|alt.badge.img+16
  • Thinkwise Local Partner Brasil
  • 529 replies

In the IAM you have 2 taks to apply roles & user rights on the DB, and that one gives a notice when I have 1 model 2 applications that point to the same DB.

De rechten van deze applicatie kunnen niet toegepast worden omdat er andere applicaties actief zijn op dezelfde database en server.

 

Although I understand the reason this check is there, however it is only viable when the applications have different models I guess.  Situation is as follows, there is 1 model, 2 applications (each with a distinct context variable and some other contextual difference like color) that point to the same database (it's not an option to separate the DB).

  • Due to this check I cannot sync the roles, and as the applications have the same model/version it should be allowed to do this.
  • As for the user-rights, it appears this can also run perfectly fine when the model/version is equal between the applications, as the user-list looks at the users of the Tenant, not specifically users that are present in the authorization-groups for this application. 

How can make these tasks work again? 

 

Best answer by Ester

Hey ​@Freddy,

Maybe, you could use Indicium to access the database and give only the Indicium pool user rights. That would be the preferred option in the future. 

For now, I understand if there are reasons that this is not possible yet. A workaround would be to generate a script before you activate the second application and run it afterwards. 

I don’t know if it is necessary to keep the check this strict. It could be that it was something we needed in the project/project_version structure, but is no longer needed in the model/branch structure. But this will probably not get much priority since we want to move towards the situation where Indicium decides on the rights and is the only actor on the database. 

View original
Did this topic help you find an answer to your question?

2 replies

Ester
Moderator
Forum|alt.badge.img+5
  • Moderator
  • 59 replies
  • Answer
  • April 23, 2025

Hey ​@Freddy,

Maybe, you could use Indicium to access the database and give only the Indicium pool user rights. That would be the preferred option in the future. 

For now, I understand if there are reasons that this is not possible yet. A workaround would be to generate a script before you activate the second application and run it afterwards. 

I don’t know if it is necessary to keep the check this strict. It could be that it was something we needed in the project/project_version structure, but is no longer needed in the model/branch structure. But this will probably not get much priority since we want to move towards the situation where Indicium decides on the rights and is the only actor on the database. 


Jeroen van den Belt
Administrator
Forum|alt.badge.img+9

Hi ​@Freddy,

Can you let us know if this helped you?


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings