Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: Modesto Vega on November 26, 2021, 03:47:13 am

Title: What type of and how many AD groups can the PCS floating license server handle?
Post by: Modesto Vega on November 26, 2021, 03:47:13 am
We are getting regular 401 errors when connecting Sparx EA to a PCS floating license server for some AD accounts. We suspect that a possible cause is these AD accounts not belonging to the AD groups mapped to floating license groups through https://www.sparxsystems.com/enterprise_architect_user_guide/15.2/model_repository/webconfig_add_or_edit_group.html.

However, there are a number of other unusual behaviours that do not help diagnosing this:

Any help will be much appreciated.
Title: Re: What type of and how many AD groups can the PCS floating license server handle?
Post by: Modesto Vega on December 01, 2021, 12:49:16 am
What started as a 401 error when connecting Sparx EA to a PCS floating license server is quickly turning into a more complicated problem. We have an ongoing support case but I would also like to reach out to the wider community to find out if anybody has experienced a similar problem or we are trying to do something which is really not supported.

In a nutshell, it is unclear if the PCS floating license server can handle

Below is a description of what we are doing and what is happening.

We have at least 9 AD accounts at play - e.g, Account1, Account2, Account3, Account4, Account5, Account6, AdminAccount1, AdminAccount2, & AdminAccount3 (where the AdminAccount1 to 3 are likely to be privileged accounts.

We have at least 3 AD groups at play - e.g., Group1, Group2 & Group3  - with the following membership
We have mapped Group1 to the default floating license group, Group2 to the admin floating license group, and created a new floating license group identical to the  default admin group for Group3.

In our environment we are seeing [WARNING]: [SSKSGroupAM] Failed to load details for group for Group1 and Group3 and not for Group2. This explains the 401 error, any accounts belonging to those 2 groups not also in group 2 cannot access the PCS floating license server/store.

There are a number of odd things here: