<div dir="ltr">Forgot to add two things:<div><br></div><div>* DNS setup - we want proper DNS setup on the machines, which would be required for the Kerberos stuff to work properly</div><div>* HTTPS - optional, but would be great if it also had HTTPS configured<br><div class="gmail_extra"><br><div class="gmail_quote">On 13 September 2016 at 09:24, Marek Posolda <span dir="ltr"><<a href="mailto:mposolda@redhat.com" target="_blank">mposolda@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">+1<br>
<br>
Few more things and tips (you may be already aware of them, but still.. Hope some of them are useful :) :<br>
<br>
- My docker image [1] already contains FreeIPA server and Keycloak server pre-configured with LDAP+Kerberos federation provider to use it. Thing is that both Keycloak+FreeIPA are on same machine, which is likely not the best for show production setup. The workstation setup needs to be done on your local machine (so you need KErberos client + Firefox setup on your laptop. That's sufficient for testing, but probably also not ideal for showcase).<br>
<br>
- In addition to FreeIPA docker images for server, FreeIPA has also docker image for client setup. See for example [2] . I am not 100% sure, but I believe that if you run this docker image and point to the already running "server" image, you will gain also all the things like PAM setup, login to the workstation with Kerberos credentials, and automatically retrieved kerberos ticket during login. Hence you just login to workstation, open firefox and you are authenticated to Keycloak. No need to manually run "kinit".<br></blockquote><div><br></div><div>The workstation will need to be a virtual machine rather than container to add X support. So IMO we should just use Vagrant and have FreeIPA and use Vagrantfile to install Fedora + FreeIPA.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
- If Keycloak and FreeIPA server are on different workstations, then:<br>
-- The Keycloak server may also need FreeIPA client installed. Or at least kerberos client installed with proper setup in /etc/krb5.conf pointing to FreeIPA kerberos realm and proper DNS setup working with FreeIPA. </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
-- Also for different servers, you will likely need to add HTTP kerberos principal for the server where keycloak is running. For example if FreeIPA is on "<a href="http://freeipa.example.org" rel="noreferrer" target="_blank">freeipa.example.org</a>" and keycloak is on "<a href="http://keycloak.example.org" rel="noreferrer" target="_blank">keycloak.example.org</a>", you will need the principal like HTTP/<a href="mailto:keycloak.example.org@KEYCLOAK.ORG" target="_blank">keycloak.example.org@KEYC<wbr>LOAK.ORG</a> . This corresponds to LDAP principal under "cn=services,cn=accounts,dc=fr<wbr>eeipa,dc=example,dc=org" . Maybe FreeIPA has it documented somewhere and/or it's easily possible to add new HTTP server principal through FreeIPA admin console. You will also need keytab exported with the credentials of this principal.<br>
Note this step is not needed if Keycloak and FreeIPA are on same machine as FreeIPA server automatically has HTTP principal for it's own machine (something like HTTP/<a href="mailto:freeipa.example.org@KEYCLOAK.ORG" target="_blank">freeipa.example.org@KEYCL<wbr>OAK.ORG</a> for the example above), to allow login to FreeIPA admin console with kerberos OOTB.<br></blockquote><div><br></div><div>We should really figure out how to do this on separate machines, so I think going that way would be best even though it's harder to do.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
[1] <a href="https://github.com/mposolda/keycloak-freeipa-docker/" rel="noreferrer" target="_blank">https://github.com/mposolda/ke<wbr>ycloak-freeipa-docker/</a><br>
[2] <a href="https://github.com/adelton/docker-freeipa/tree/fedora-22-client" rel="noreferrer" target="_blank">https://github.com/adelton/doc<wbr>ker-freeipa/tree/fedora-22-cli<wbr>ent</a><span class="gmail-HOEnZb"><font color="#888888"><br>
<br>
Marek</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
On 13/09/16 08:07, Stian Thorgersen wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I'd like to have a simple way to demo LDAP and Kerberos support. To that end we should add a Vagrant setup with the following:<br>
<br>
* Keycloak server<br>
* MySQL or Postgres<br>
* FreeIPA<br>
* Workstation with Kerberos authentication (needs X and Firefox installed)<br>
<br>
The Keycloak server should already be configured to use the FreeIPA server as a user federation provider (using LDAP and Kerberos). The workstation can be co-located with FreeIPA server if it makes things much simpler, but it should be possible to login to the workstation with Kerberos. Firefox should be pre-configured for Kerberos to work both on Keycloak login and FreeIPA admin console.<br>
<br>
I want a proper database and a web based client for the database so it's simple to inspect the database.<br>
<br>
Bruno has already volunteered to look into this, but first we should make sure this is the setup we'd like to be able to showcase.<br>
</blockquote>
<br>
<br>
</div></div></blockquote></div><br></div></div></div>