Re: [keycloak-dev] Packaging of ApacheDS for examples?

----- Original Message ----- > From: "Marek Posolda" <mposolda(a)redhat.com&gt; > To: "Stian Thorgersen" <stian(a)redhat.com&gt; > Cc: keycloak-dev(a)lists.jboss.org > Sent: Thursday, 2 July, 2015 9:48:52 AM > Subject: Re: [keycloak-dev] Packaging of ApacheDS for examples? > > Thanks, I will investigate (c) then . > > It's more work than (a), which is no work > > Well, it won't be that hard to do, just afraid of all the dependencies > required for ApacheDS . Which might cause that size of keycloak-examples > will grow to be very big (in that case we may need separate example > package with embedded ApacheDS LDAP/Kerberos to download). I will > investigate sizes etc and will send update. We don't package dependencies with the examples, only the source. So that shouldn't be a problem? > Marek > > On 2.7.2015 09:13, Stian Thorgersen wrote: >> I don't like option a. Why is option c much more work? Doesn't seem like it >> should be that hard. >> >> ----- Original Message ----- >>> From: "Marek Posolda" <mposolda(a)redhat.com&gt; >>> To: keycloak-dev(a)lists.jboss.org >>> Sent: Tuesday, 30 June, 2015 3:12:41 PM >>> Subject: [keycloak-dev] Packaging of ApacheDS for examples? >>> >>> I am thinking about adding LDAP example, which can be used as a base for >>> LDAP >>> mappers based blog and screencast. >>> >>> It will contain the application to show some claims (also both >>> singlevalued >>> and multivalued attributes). It will also contain JSON realm with >>> UserFederation configuration pointing to our ApacheDS and LDIF with some >>> simple users for testing. I already added end-to-end test to the testsuite >>> (LDAPMultipleAttributesTest.ldapPortalEndToEndTest ) >>> >>> >>> The only possible problem is how to easily bootstrap ApacheDS based LDAP >>> servers in user's environment. I am thinking about 3 approaches: >>> >>> a) Point to the embedded ApacheDS server from our testsuite. This will be >>> easy to do and it's what Kerberos example is already doing . Problem is >>> that >>> it requires people to checkout the keycloak sources through github and >>> build >>> them through maven, so not very user friendly >>> >>> b) Create docker image for ApacheDS servers (one for ldap example and >>> another >>> for kerberos). Not sure if it's fine to require users to install docker >>> (even more pain might be on windows, when they need boot2docker or >>> something...) >>> >>> c) Packaging with ApacheDS based servers directly into our example >>> package, >>> so people can just run something like: >>> >>> java -jar keycloak-examples/ldap/apacheds-embedded.jar >>> -Dldif.location=keycloak-examples/ldap/example.ldif >>> >>> and similarly for kerberos. >>> >>> For me it's easiest to go with (a) but not sure about usability... >>> Regarding >>> usability (c) looks best but it's much more work. >>> >>> WDYT? >>> Marek >>> >>> >>> >>> _______________________________________________ >>> keycloak-dev mailing list >>> keycloak-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/keycloak-dev >