Hi Johan,
We're using the following configuration:
<roleManager enabled="true" defaultProvider="ActiveDirectoryRoleProvider" cacheRolesInCookie="true">
<providers>
<clear/>
<add name="ActiveDirectoryRoleProvider" type="CustomComponent.Security.ActiveDirectory.ActiveDirectoryRoleProvider, CustomComponent" connectionStringName="ActiveDirectoryProviderConnection" connectionUsername="[username]" connectionPassword="[password]" attributeMapUsername="sAMAccountName"/>
</providers>
</roleManager>
<membership defaultProvider="ActiveDirectoryMembershipProvider" userIsOnlineTimeWindow="10">
<providers>
<clear/>
<add name="ActiveDirectoryMembershipProvider" type="CustomComponent.Security.ActiveDirectory.WinActiveDirectoryMembershipProvider, CustomComponent" connectionStringName="ActiveDirectoryProviderConnection" connectionUsername="[username]" connectionPassword="[password]" enableSearchMethods="true" attributeMapUsername="sAMAccountName"/>
</providers>
</membership>
Hi,
A client has implemented AD role and membership providers and is seeing a difference in the number of groups in the CMS set access rights screen and the access rights screen in Community Moderation Mode. There are groups needed for setting access rights to content that are not available but they are available in Community.
Interestingly in one of our environments we are seeing the opposite - there are more groups in CMS set access rights.
Anyone encountered this before?
Thanks,
Mark