search for: groupmembershipattribut

Displaying 6 results from an estimated 6 matches for "groupmembershipattribut".

2020 Aug 21
3
Using Samba AD/DC as an Active Directory OAuth provider for OpenShift
...the AD Cert) with Active Directory. (Working config attached) 2) declare a group synchronization sync config. (non working config attached) Part #1 worked fine and I can now login to the OCP platform using my AD credentials. ...But I'm struggling to make part #2 work fully. In short, with: groupMembershipAttributes: [ "memberof" ] .. some groups (non-nested) get synced but others do not. OCP doesn't support nested groups and it is documented ([1]) that when using AD and nested groups, one should use this instead: groupMembershipAttributes: [ "memberof:1.2.840.113556.1.4.1941:" ] O...
2020 Aug 21
1
Using Samba AD/DC as an Active Directory OAuth provider for OpenShift
...e a group synchronization sync config. >> (non working config attached) >> >> Part #1 worked fine and I can now login to the OCP platform using my AD >> credentials. >> >> ...But I'm struggling to make part #2 work fully. In short, with: >> >> groupMembershipAttributes: [ "memberof" ] >> .. some groups (non-nested) get synced but others do not. >> >> OCP doesn't support nested groups and it is documented ([1]) that when >> using AD and nested groups, one should use this instead: >> groupMembershipAttributes: [ &quot...
2020 Aug 21
2
Using Samba AD/DC as an Active Directory OAuth provider for OpenShift
...lare a group synchronization sync config. >> (non working config attached) >> >> Part #1 worked fine and I can now login to the OCP platform using my >> AD credentials. >> >> ...But I'm struggling to make part #2 work fully. In short, with: >> >> groupMembershipAttributes: [ "memberof" ] >> .. some groups (non-nested) get synced but others do not. >> >> OCP doesn't support nested groups and it is documented ([1]) that >> when using AD and nested groups, one should use this instead: >> groupMembershipAttributes: [ "...
2020 Aug 21
4
Using Samba AD/DC as an Active Directory OAuth provider for OpenShift
...??? groupsQuery: > ??????? baseDN: "DC=ad,DC=lasthome,DC=solace,DC=krynn" > ??????? scope: sub > ??????? derefAliases: never > ??????? pageSize: 0 > ??????? filter: (objectclass=group) > ??? groupUIDAttribute: primaryGroupID > ??? groupNameAttributes: [ cn ] > ??? groupMembershipAttributes: [ "memberof:1.2.840.113556.1.4.1941:" ] > ??? usersQuery: > ??????? baseDN: "DC=ad,DC=lasthome,DC=solace,DC=krynn" > ??????? scope: sub > ??????? derefAliases: never > ??????? filter: (objectclass=person) > ??????? pageSize: 0 > ??? userNameAttributes: [...
2020 Aug 21
0
Using Samba AD/DC as an Active Directory OAuth provider for OpenShift
...onfig attached) > > 2) declare a group synchronization sync config. > (non working config attached) > > Part #1 worked fine and I can now login to the OCP platform using my > AD credentials. > > ...But I'm struggling to make part #2 work fully. In short, with: > > groupMembershipAttributes: [ "memberof" ] > .. some groups (non-nested) get synced but others do not. > > OCP doesn't support nested groups and it is documented ([1]) that when > using AD and nested groups, one should use this instead: > groupMembershipAttributes: [ "memberof:1.2.840.113...
2020 Aug 21
0
Using Samba AD/DC as an Active Directory OAuth provider for OpenShift
...?? baseDN: "DC=ad,DC=lasthome,DC=solace,DC=krynn" >> ??????? scope: sub >> ??????? derefAliases: never >> ??????? pageSize: 0 >> ??????? filter: (objectclass=group) >> ??? groupUIDAttribute: primaryGroupID >> ??? groupNameAttributes: [ cn ] >> ??? groupMembershipAttributes: [ "memberof:1.2.840.113556.1.4.1941:" ] >> ??? usersQuery: >> ??????? baseDN: "DC=ad,DC=lasthome,DC=solace,DC=krynn" >> ??????? scope: sub >> ??????? derefAliases: never >> ??????? filter: (objectclass=person) >> ??????? pageSize: 0 >&gt...