Replies: 8 comments 19 replies
-
can you please enable DEBUG and supply the log from tandoor? |
Beta Was this translation helpful? Give feedback.
-
I already enabled that earlier, but it doesn't seem to be very verbose.
Or is this an indicator that the env file isn't really used? |
Beta Was this translation helpful? Give feedback.
-
I guess I can wait another week. Just installed everything, but didn't want to start using it with local accounts. |
Beta Was this translation helpful? Give feedback.
-
Yes, it's in docker. Good point, I had only tested that connectivity from the docker host. But in the end it turns out fine as far as I can tell:
As always, domain and subnets disguised. If that's of any relevance, this is the docker-compose file I used to create the setup:
But I wouldn't see any problem here. With the initially created admin account I am able to use Tandoor as expected. |
Beta Was this translation helpful? Give feedback.
-
Any update on this? Having the same issue |
Beta Was this translation helpful? Give feedback.
-
I just upgraded. I'm on x86, but I get this output for the main container:
Are you referring to this error? |
Beta Was this translation helpful? Give feedback.
-
Would be cool, if you could post a reply here once you've learned anything about it. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone, thanks for the fix. LDAP debugging is working now. Now it shows some more details. I have experimented with a couple of variations of the AUTH_LDAP_USER_SEARCH_FILTER_STR. It turns out they were all correct, but still I got something like this:
Even Active Directory style filters bring the same result:
I had trouble believing that, but the fact that the result was 0 and not an actual error made me check the group again. It turns out the user was really not directly in the group, but in a nested group. After adding the user directly to the group I could finally login!! |
Beta Was this translation helpful? Give feedback.
-
Hi everybody,
I'm trying to use LDAP as authentication backend. Unfortunately it's not working for me.
I have already configured many different applications to authenticate against my LDAP servers. So I should be able to supply the right values. But I'm unable to find the reason for it not working here.
This is an excerpt from my .env file:
SOMEUSER, SOMEPASSWORD and the domain names are of cause just placeholders here.
Judging by the documentation and this page: https://github.com/TandoorRecipes/recipes/blob/develop/.env.template
....my file looks ok.
Until I manage to get LDAP connections to work in cleartext, I always leave encryption disabled for the config phase. It would just be another source of problems.
I've had a look at these posts already:
#1225
But the log file stays empty for me unfortunately.
Doesn't help either: #1299
@lostlont By any chance might you be able to help here?
Beta Was this translation helpful? Give feedback.
All reactions