Multiple Users and the Application Catalog

[iainjo]

We're running AS 11.5 SP1. We have two domain users who have their own client tools machines. Each user account is a member of a domain group which provides the access to the Application Catalog database.

Both have access and can create groups and import applications into the Application Catalog, however:

The first user account, the one that was used originally install AS and setup the catalog can see everything in the catalog, including apps/groups created by the second account.

The next account that was commissioned can't access any groups or applications that the first account has added. It can see the other groups in the right hand pane but not do anything with them. It can create a group and import an application but only seems to be able to manage it's own set. Whereas the first account can manage everything.

They have the same access in SQL, is there an AS configuration setting that sets a master account?

Thanks

[jaybee96]

are you using AdminStudio Enterprise and/or WorkFlow Manager?
You are then able to create roles with detailed permissions /access to do certain tasks. After that you can add users / groups to those roles.

From that moment on , you can use single sign-on.

[iainjo]

jaybee96 wrote:
are you using AdminStudio Enterprise and/or WorkFlow Manager?
You are then able to create roles with detailed permissions /access to do certain tasks. After that you can add users / groups to those roles.

From that moment on , you can use single sign-on.

Unfortunately we just have AdminStudio Professional (Complete) and no WorkFlow Manager.

The SQL permissions are identical for each user so I can only assume there's some additional AdminStudio security hidden away somewhere.

We have per node licensing. We've setup two machines and two user accounts in order we have some awareness of who is working on what. Should we be using a single user account across both machines?

[jaybee96]

Yes, using 1 generic (sql) account should do the trick.
there is no hidden security... 😉

[iainjo]

jaybee96 wrote:
Yes, using 1 generic (sql) account should do the trick.
there is no hidden security... 😉

We don't use any individual SQL accounts. All that was setup in the beginning was an AD Group that has all our "Client Tools" accounts in. That group is the one that has the rights in SQL.

We've logged an incident with Flexera so will see what they recommend.