On Dec 6, 2017 1:47 AM, "jelmer van amen" <[email protected]> wrote:

The keycloak adapter subsystem needs more than just some XML configuration
(as described on http://www.keycloak.org/docs/latest/securing_apps/
index.html#_jboss_adapter).  It needs to have some layers extracted to the
wildfly root dir, besides from the XML change. How would one go around
solving this using the standard S2I pipeline?


If the default assemble script doesn't allow you to override the
configuration you need to override, you'll have to provide a custom
assemble script that does.


On 5 December 2017 at 14:38, Ben Parees <[email protected]> wrote:

> The wildfly image allows you to supply your own standalone.xml config as
> part of your source.
>
>
> Ben Parees | OpenShift
>
> On Dec 5, 2017 05:10, "jelmer van amen" <[email protected]> wrote:
>
>> When using the standard s2i pipeline, no configuration seems to be
>> present to add a keycloak security subsystem. How would one go about adding
>> a keycloak adapter (as subsystem in wildfly) using the standard S2I image
>> stream for wildfly?
>>
>> Kind regards,
>> Jelmer
>>
>> On 5 December 2017 at 07:15, Steven Pousty <[email protected]> wrote:
>>
>>> Why do you think it doesn't support it. There should be no problem
>>> adding it. WHich part are you stuck on?
>>> Thanks
>>> Steve
>>>
>>> On Mon, Dec 4, 2017 at 10:11 PM, jelmer van amen <
>>> [email protected]> wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> We’re migrating our software to OpenShift. We have a maven (well,
>>>> actually gradle, but we’re ok with moving to maven) J2EE war application
>>>> secured using keycloak adapter in a wildfly instance.
>>>>
>>>>
>>>>
>>>> We’d like to use s2i for this application. Our first guess would be
>>>> https://github.com/openshift-s2i/s2i-wildfly , but that does not (seem
>>>> to) support adding the keycloak adapter (http://www.keycloak.org/docs/
>>>> 3.0/securing_apps/topics/oidc/java/jboss-adapter.html#_jboss_adapter).
>>>>
>>>>
>>>>
>>>> What would be the best way to go?
>>>>
>>>>
>>>>
>>>> Thanks!
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> [email protected]
>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> users mailing list
>> [email protected]
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to