#LDAP with custom domain
1 messages · Page 1 of 1 (latest)
on the ldap provider under protocol settings you can define your desired base
Ok, i already did this, but how can i "attach" the users under that base? i would like to separate the users so every customer has his base
if i understand that correct you need to create an ldap provider for each customer with their unique ldap base and connect each provider to the outpost
not sure how to limit the users inside that provider to a specific set of users tho
i'll do an example
in jumpcloud, when i configure ldap provider, it generates a base DN: O=something,DC=jumpcloud,DC=com
i think that the O is the customer organization on which an application can do a lookup
i would like to separate the various customers on my authentik
but the problem is that if i use the default config ldap.goauthentik.io i could create groups on which i could insert the customer's users
but the domain still remains unique "ldap.goauthentik.io"
i don't know if i'm explaining in a clear way, i'd like to configure authentik as a "multi-forest" in Microsoft AD
i understand the goal. i just have no clue if thats possible the way you currently want it.
i would create a provider for each domain in that forest and then try to figure out how to separate it and play around with ldapsearch to verify.
the base can be provided per provider, but i have no clue on how to set it up the way that only the users of a specific directory is getting populated in the ldap structure
and for example, have you got any idea for modify the default domain goauthentik.io? can i modify it via docker-compose?
ok, i tried to configure 2 providers with a different domain each one
i created 2 ldap search bind user and i gave them the respective permissions on the providers
but if i do the ldap search, either find the same authentik's directory
do you know a method to separate the 2 "searches"
let me check
now i want to play around with that aswell. but need some time before im on any pc
no problem, i did the binding in the application using group
with only the ldap search user inside, but i see all the directory 😦
i think that i might doing something wrong with the filter, i'm using "'(objectClass=user)'"
i guess that user has the right to search the whole tree?
might need to define that more specific
maybe, i only gave him the full search permission on the provider
should i use some attributes?
well, the provider is currently offering all users from your authentik
goal would be limiting the provider to only return the desired users and groups. so it needs to be somewhere on either application or provider
with the full tree right you see all users in the authentik instance
you're right
maybe i should create a new path on the directory menu?
i would highly suggest that to begin with!
if you want to separate them, thats a good idea in general
and what would be the base DN then?
from the other provider
theres also a preview
on what it currently is
either on application or provider. cant remember
ok, i'll try. I'm not understanding if i can use a custom directory path insted of the default "users" in the LDAP base DN
i dont think you can. thats just purely cosmetical as you want them separate in ldap, they should be separated to begin with, no?
what i'm seeing is that if i have 2 users, let's say Peter and Tom. Peter is part of Corporate A, Tom is part of Corporate B
Corporate A has a domain of example.com
Corporate B has a domain of example.eu
in authentik i have to configure 4 users in theory:
- Peter
- Tom
- LDAP-User-Corporate-A
- LDAP-User-Corporate-B
yes, we are on the same page
oh ok
but both service accounts are currently seeing peter and tom within their domain
not really
if i do a LDAP search with LDAP-User-Corporate-A, the result is Peter.ldap.example.com and Tom.ldap.example.com
yes
if i do a LDAP search with LDAP-User-Corporate-B, the result is Peter.ldap.example.eu and Tom.ldap.example.eu
the other returns both with eu
ye i know
so you think that i can't separate "logically" the users?
thats what i want to find out aswell ^^
look into the application binding and provider permissions
theres got to be something to limit it somehow
text if you find something noteworthy. ill be on in about 2-3 hrs
didnt find anything aswell. you might need to use different brands
i did some other tests
if i leave the default base DN, eg. DC=ldap,DC=example,DC=com, with the command ldapsearch i'm able to "restrict" the -b option with the desired user group
so it finds only the group i want restrict for the search
but when i put the complete base DN that i found in Authentik as base DN of the provider, i get "ldap_bind: Insufficient access (50)"