This is a re-do of a March issue where that solution is not working this time. I have re-installed OOD, and have the dex section of /etc/ood/config/ood_portal.yml like this:
# # Default based on if ssl key for ood-portal-generator is defined
# # Only used if SSL is disabled
# http_port: "5556"
# # Only used if SSL is enabled
# # tls_cert and tls_key take OnDemand configured values for ssl and copy keys to /etc/ood/dex maintaining file names
# # Client ID, defaults to servername or FQDN
# client_id: null
# # Client secret, value auto generated
# # A value that is a filesystem path can be used to store secret in a file
# # The OnDemand redirectURI is auto-generated, this option allows adding additional URIs
# client_redirect_uris: 
# # Additional Dex OIDC clients to configure
# static_clients: 
# # The following example is to configure OpenLDAP
# # Docs: https://github.com/dexidp/dex/blob/master/Documentation/connectors/ldap.md
- type: ldap
bindDN: "CN=ldap authentication,OU=Service Accounts,OU=ITStaff,OU=Departments,OU=CSHLusers,DC=cshl,DC=edu"
- userAttr: DN
I am getting an internal server error with the following in the log:
[Mon May 09 16:38:23.577353 2022] [auth_openidc:error] [pid 2066773:tid 140388216600320] [client 220.127.116.11:52349] oidc_check_userid_openidc: configuration error: the authentication type is set to "openid-connect" but OIDCRedirectURI has not been set
Thanks for posting. I do not see the exact issue. I’m going to paste my personal, functional LDAP config for OOD. It works properly with the exception that I have not setup ssl since i’m on my private network. Maybe you can compare the mine against yours, or maybe someone else will be able to chime in to help.
That get ondemand-dex running, but reloading the page gives an internal server error, with this in the apache log:
[Tue May 10 14:05:45.449202 2022] [auth_openidc:error] [pid 2106852:tid 140057406928640] [client 18.104.22.168:63181] oidc_util_http_call: curl_easy_perform() failed on: https://lightshare.cshl.edu:5554/.well-known/openid-configuration (Failed to connect to lightshare.cshl.edu port 5554: Connection refused)
[Tue May 10 14:05:45.449275 2022] [auth_openidc:error] [pid 2106852:tid 140057406928640] [client 22.214.171.124:63181] oidc_provider_static_config: could not retrieve metadata from url: https://lightshare.cshl.edu:5554/.well-known/openid-configuration
I left the old dex stuff in /etc/ood/config/ood_portal.yml alone; not sure what that file is being used for now.
Thanks. The firewall rule for 5554 was there (from before), but doing “firewall-cmd --reload” fixed the issue.
Now it appears LDAP authentication is working (as per /var/log/messages), but the OOD page says: " Home directory not found… Your home directory appears to be missing. The home directory mount may be unavailable, or your home directory may need to still be created. Please contact support for help and attempt to restart your web server by clicking below when the problem has been fixed."
But the home directory does exist and I can log in and into the home directory via ssh.
The only logging I see is in /var/log/ondemand-nginx…
[root@lightshare ~]# cat /var/log/ondemand-nginx/error.log
2022/05/11 10:00:03 [notice] 2147931#0: signal process started
2022/05/11 10:36:46 [notice] 2149486#0: signal process started
2022/05/11 10:36:46 [error] 2149486#0: open() "/var/run/ondemand-nginx/patoddh/passenger.pid" failed (2: No such file or directory)
The error message could be a red herring. Looks like the log file is stating that passenger.pid is not found. You might want to ensure that passenger is actually running and that the pid file is located in the location that OOD is expecting.
Thanks for all your help here. I don’t know anything about passenger, but I restarted services. I’m still getting “home directory not found” on the web page, but the log file no longer has that message, and I now see the file /var/run/ondemand-nginx/patoddh/passenger.pid
The only new logging is in /var/log/ondemand-nginx/patoddh/error.log…
[ N 2022-05-11 14:21:25.2229 2157540/T1 age/Wat/WatchdogMain.cpp:1373 ]: Starting Passenger watchdog...
[ N 2022-05-11 14:21:25.2472 2157543/T1 age/Cor/CoreMain.cpp:1340 ]: Starting Passenger core...
[ N 2022-05-11 14:21:25.2474 2157543/T1 age/Cor/CoreMain.cpp:256 ]: Passenger core running in multi-application mode.
[ N 2022-05-11 14:21:25.2599 2157543/T1 age/Cor/CoreMain.cpp:1015 ]: Passenger core online, PID 2157543
[ E 2022-05-11 14:21:27.6456 2157543/T5 age/Cor/SecurityUpdateChecker.h:521 ]: A security update is available for your version (6.0.7) of Phusion Passenger. We strongly recommend upgrading to version 6.0.14.
[ E 2022-05-11 14:21:27.6456 2157543/T5 age/Cor/SecurityUpdateChecker.h:526 ]: Additional security update check information:
- [Fixed in 6.0.14] [CVE-2018-25032] zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.
- [Fixed in 6.0.14] A use after free memory safety issue was introduced in 6.0.12, and fixed in 6.0.14.
I see an “E” on the lefts side of a couple of lines that sound like a suggestion. Error?
Users cannot update passenger directly. I’ll submit a ticket to update it upstream.
That said - back to the original issue about HOME directory. Could be an SELinux issue. If you’ve enabled SELinux, have you also enabled the booleans? There’s another active discourse topic for SELinux if that’s the case.
Are you using local HOME directories? I don’t think we wrote policies for that, so I’d bet you’re getting denials there.
I’m guessing you’re looking for ondemand_use_nfs-ish type policy for local HOME, though I’m not an SELinux issue, if the directory exists but we complain about not seeing I’d bet money it’s an SELinux issue.
No, they are not local home directories, they are on NFS and mapped via SSSD. And they worked on the installation I did in March, prior to this re-installation.
I experimented with the “semodule -DB”, “semodule -B”, and “cat /var/log/audit/audit.log | audit2allow” things referred to in the other thread/ticket you pointed me to. I also turned the ondemand_manage_user_home_dir boolean on and off (restarting services). Nothing made any difference in the logging. I’m stumped at the moment.