I am standing up OOD to talk to our on prem HPC. i would like to get everything running on one host.
OS: RockyLinux 9.6
I am looking to use keycloak 26.3.2 for auth.
I have installed the ood RPM and its responding on http. i have installed “Keycloak” and setup a new “Realm” and also setup the “User federation”.
These directions talk about adding an OIDC Client Template but i don’t see where to do that
I did add OnDemand as a client so that part is done. don’t know how to move forward. please help.
I just completed an install using those same versions. Try the latest version of the docs and it should work. Feel free to reach out with more questions.
Thank you @maflister! I may not have noticed the link to the documentation is very old. Not sure why/how you got release docs for 1.4, but yea latest is your best bet.
You should use the “OpenID Connect with KeyCloak on RHEL7” guide for this purpose. Not sure why the OpenID Connect page still exists as its probably redundant now.
We deploy KeyCloak on its own VM since we have several OOD instances and other applications authenticating to the same instance. But our first deployment many years ago had KC and OOD on the same host. If this is the only app that uses KC it is a good solution. Only difference is the hostname and port in the different config files.
You can skip the CILogon page unless that is your type of authentication. We use LDAP. You can skip the theme step until everything is working.
I’m not sure what “default page” means. Send a screenshot if possible. If you’re not being prompted for authentication, there is probably a missed step like firewall ports not open, ood-portal-generator not run after change, etc. I am happy to look at config files if you’d like to share those but probably best to confirm if you’re even prompted for authentication.
At a glance it looks OK. Are there errors in the systemd/journalctl output when you bounce httpd? Also I just want to check the ood-portal.conf and see what it looks like.
Actually now I’m thinking that page may be cached on your browser. Can you try in a different browser and/or private mode?
That said - I would still like to confirm the content of ood-portal.conf to be sure that it has the correct vhost in it and not the conf file that points to this public page.