Ok, thanks for information.

I filed an upstream ticket to capture the decision:

Please comment in the ticket if I forget anything.


On 06/07/2013 05:52 PM, Peter Skopek wrote:
> Hi Martin,
> the main reason why I suggested to not include the script in EAP is that we
> removed all similar scripts (for example data-source definition files) from 
> its
> directories to keep is as simple and clean as possible.
> JBoss EAP 6 configuration changes needed to integrate with FreeIPA are quite
> stable and as EAP has it as API/CLI it is not going to change in the near
> future (all JBoss EAP 6 [6.0.0, 6.0.1, 6.1.0] releases will work with
> configuration proposed in config. document).
> I can understand, that similar reasons exist in FreeIPA side. So, the best way
> would be your proposal to create the "freeipa-client-jboss" subpackage.
> Regards,
> Peter
> On 06/07/2013 02:58 PM, Martin Kosek wrote:
>> Hello Jan a Peter, freeipa-devel users,
>> There was recently a project of integrating FreeIPA server with Jboss EAP. 
>> One
>> of the results of this project should be a script able to conveniently
>> configure JBoss EAP on a machine to use FreeIPA as an identity&authentication
>> backend.
>> What I would like to find out is what would be the best place to 
>> store&maintain
>> such script. AFAIK, JBoss EAP did not want to keep the configuration script
>> with their project - can you Peter please share the reasons for it? I was
>> thinking it would be then easier to maintain the script according to JBoss 
>> EAP
>> releases.
>> Second option would be to deploy the script with FreeIPA project. Then, they
>> would also conform to FreeIPA release schedule and not JBoss ones. So I was
>> pondering where should we put scripts like this one, it is quite a specific
>> script, so I do not want to keeping it with freeipa-client package.
>> In this case I would propose creating a new optional subpackage
>> "freeipa-client-jboss" which would include all scripts/docs for the JBoss EAP
>> integration (may extend in future). In future, there may also come more
>> thematic FreeIPA integration scripts when they cannot be stored in relevant
>> upstream projects.
>> Any ideas? Is the correct approach to keep configuration scripts for other
>> upstream projects?
>> Thanks,
>> Martin

Freeipa-devel mailing list

Reply via email to