Here follows the scenario: SharePoint 2013 on premises, forms authentication enabled and working against three providers: two ADs and one SQL
Our users are able to authenticate against the site, people-picker find both users (from ADs and SQL) and AD groups. However, if we give permissions through AD Security Groups, the users report the site were not shared with them.
Bellow is the web.config role manager configuration
<add name="FB_Role" type="Microsoft.Office.Server.Security.LdapRoleProvider, Microsoft.Office.Server, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" server="desenv.fb.org.br" port="389" useSSL="false" groupContainer="DC=desenv,DC=fb,DC=org,DC=br" groupNameAttribute="cn" groupNameAlternateSearchAttribute="samAccountName" groupMemberAttribute="member" userNameAttribute="sAMAccountName" dnAttribute="distinguishedName" groupFilter="(ObjectClass=group)" userFilter="(ObjectClass=person)" scope="Subtree" />
<add name="EDU_Role" type="Microsoft.Office.Server.Security.LdapRoleProvider, Microsoft.Office.Server, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" server="desenvedu.fb.org.br" port="389" useSSL="false" groupContainer="DC=desenvedu,DC=fb,DC=org,DC=br" groupNameAttribute="cn" groupNameAlternateSearchAttribute="samAccountName" groupMemberAttribute="member" userNameAttribute="sAMAccountName" dnAttribute="distinguishedName" groupFilter="(ObjectClass=group)" userFilter="(ObjectClass=person)" scope="Subtree" />
We tried changing the FormsTokenLifeTime and profile sync but still no success and we are still unable to give permissions through AD groups. Any ideas ?
server=
andgroupContainer
attributes differ for the first part of the FQDN. Is this intentional? As an aside, it's generally better and easier to maintain a pre-auth FBA service in front of SharePoint, such as WAP + ADFS, rather than configure FBA directly on SharePoint.