tdockendorf
September 1, 2020, 11:26am
2
Do not remove socket files manually, that could leave the PUN in a weird state. Instead try to use this:
/opt/ood/nginx_stage/sbin/nginx_stage nginx_clean -f -u laud
Have you tried OnDemand 1.8 with Dex and LDAP? That might yield better results. As for why you see that in the first place, it’s hard to say. I found a few older threads with similar errors maybe useful. It looks like could be issue with LDAP configuration or user not mapping correctly to local OOD system. Does the user laud exist when you do getent passwd laud from the OnDemand host?
use this config
AuthLDAPSearchAsUser on
instead of
AuthLDAPBindDN someTestUser
AuthLDAPBindPassword someTestPassword
Maybe it could be your AuthLDAPBindDN that is the issue? I mean if you’re binding to a different base DN than the rest of your users?
You’re sure they have this attribute, name?
Can you show us the entire config? Feel free to obfuscate things with ‘host’ and ‘a’ ‘b’ ‘c’ and so on. With LDAP, there is always some very simple reason things fail.
I would suggest these thi…
Hey guys,
We had or have the same issue. FYI, Our IDAM path for OOD is convoluted, ie. AD creds with IPA, sssd, pwath and a module in Apache (cannot remember it’s name) and some users were created in AD by central IT with spaces in their name.