Forum Discussion
APM AD Group Size Limit Issue
We have two main groups within our AD Structure. These have a huge amount of users (tens of thousands). The issue is, when assigning these groups to an Access Policy on the APM, they won't work. We are assuming it is a size limit somewhere and we would ideally like to use these two groups as a fallback if other smaller groups don't have a specific policy defined (we are running a rolling implementation of the webtop).
Does anyone have any ideas whether there is a way to change the acceptance of this group in APM, or if there is another way around it.
If there isn't please also let us know and we will have to define each group explicitly.
The issue was not to do with the Size of an AD Group. Instead, it was due to the fact that in the APM, the AD Query had not been configured for returning Parent and Nested Groups. After enabling these two, the policy is running perfectly.
- UncountedBrute_Altocumulus
The issue was not to do with the Size of an AD Group. Instead, it was due to the fact that in the APM, the AD Query had not been configured for returning Parent and Nested Groups. After enabling these two, the policy is running perfectly.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com