Known Issues

Key Product Summary Affected Version(s) Fix Available In
LIC-6479 Licensing

For a license rule, when you define an application scope that equals to or contains a specific string and select the Dynamic option, the Controller UI displays all the application names matching the condition, ignoring the uppercase and lowercase differences.

However, the license rule itself is applied in a case-sensitive manner. The rule only affects applications whose names match the specified condition exactly as typed, considering the uppercase and lowercase letters.

Example:

Suppose you have the following applications: Xyz1, Abc1, Abc2, Cba1, and Cba2.

  • You set the condition to CONTAINS a.
  • The Controller UI displays Abc1, Abc2, Cba1, and Cba2. All these names contain "a" or "A", regardless of case.
  • The license rule will only be applied to Cba1 and Cba2. These names contain a lowercase "a" exactly as specified in the condition.

  • The rule will not apply to Abc1 and Abc2, because they contain an uppercase "A", which does not match the lowercase "a".

Recommendation:

Avoid the Dynamic option when configuring Application Scope. Instead, manually select each application name individually from the list.

 25.7.0, 25.10.0

-
CON-7279 Controller

The registered JMX entities block the agent registration leading to thread pool saturation.

 25.7.5, 25.10.0

-

IAM-7355

 Accounts
When you navigate to Settings > Administration > Authentication Provider > SAML Group Mappings and perform the following actions in the Mapping of Group to Roles
  • Add a new group and assign a role. Save both the popup and the main page.
  • Edit an existing group and update the group name by changing only the letter case. For example, changing "TEST_NAME_3" to "TEST_NAMe_3", then save the changes.

AppDynamics does not retain the edited SAML group if the update involves only letter case changes. After saving, the group is removed from the mapping list, and all associated role mappings are lost.

Workaround:

To update a group name with only a case change:
  1. Delete the existing group-to-role mapping for the group you wish to modify.
  2. Add a new group-to-role mapping using the desired case for the group name.
  3. Reassign the roles that were previously mapped to this group.
Note: This issue is specific to group name changes involving letter case only. Renaming a group entirely does not trigger the issue.
25.10.0 -