lol neither the code but more so the configuration into a nextcloud instance. fucking ldap and the groups are throwing more curveball to me than the cdc
LDAP is easy.
It's built like a inverted tree for the most part. You'll have a root, usually something like rootdse (ID and schema rules) and then it breaks down into OUs or Organizational Units. Something like dc=poal,dc=com woud be an OU. Under that you'd have groups, usually an application group like ou=exchange or ou=sql or ou=gaschamber. Elsewhere you'd have user groups like ou=kikes,dc=poal,dc=com OR ou=AccountsPayable,dc=poal,dc=com. You'd assign someone from a user group to an application group and that app would use LDAP for authentication for whatever access the user needed.
cn=Schlomo P. Kike,ou=kikes,dc=poal,dc=com can be assigned to the ou=gaschamber,dc=poal,dc=com group. Then Schlomo would gain access to the Gas Chamber. But Linda from accounting might need access to the ou=gaschamber group to pay for the Zyklon B the application requires. so cn=Linda Goy,ou=AccountsPayable,dc=poal,dc=com would also be assigned to the ou=gaschamber,dc=poal,dc=com group.
Here is a link that explains it pretty well.
wow, fantastic explanation and an excellent use of terminology.
there was a lone tear that may have rolled down my cheek amongst the laughter bellowing from my belly.
take that up vote you son a beach
Your welcome. After I wrote this I started to wonder if I should write an IT book called "IT Support for Bigots".
BTW, I found the issue in the TLS
if you every have to do ldap this one is slick, just a little new in my opinion.
the link below solved my issue, wasn't my configuration, but tha KS for the explanation. seriously laughed my ass off .
https://stackoverflow.com/questions/68903113/django-ldaps-tls-started-failing-with-error-server-down
(post is archived)