[JBoss JIRA] (ARTIF-634) Automate Keycloak setup during integration tests
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-634?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-634:
------------------------------
Description:
Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete:
- Automate the realm import
- Automate the EAP/Wildfly admin user password
- Re-enable the server install/configure ant tasks
- Re-enable Jenkins integration test jobs
- Add job for Wildfly
was:
Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete:
- Automate the realm import
- Automate the EAP/Wildfly admin user password
- Re-enable the server install/configure ant tasks
- Re-enable Jenkins integration test job
> Automate Keycloak setup during integration tests
> ------------------------------------------------
>
> Key: ARTIF-634
> URL: https://issues.jboss.org/browse/ARTIF-634
> Project: Artificer
> Issue Type: Task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete:
> - Automate the realm import
> - Automate the EAP/Wildfly admin user password
> - Re-enable the server install/configure ant tasks
> - Re-enable Jenkins integration test jobs
> - Add job for Wildfly
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-634) Automate Keycloak setup during integration tests
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-634?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on ARTIF-634:
-----------------------------------
It looks like the container config in arquillian.xml can take a "javaVmArguments" param. Pass it -Dkeycloak.import=[path]/governance-realm.json?
> Automate Keycloak setup during integration tests
> ------------------------------------------------
>
> Key: ARTIF-634
> URL: https://issues.jboss.org/browse/ARTIF-634
> Project: Artificer
> Issue Type: Task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete:
> - Automate the realm import
> - Automate the EAP/Wildfly admin user password
> - Re-enable the server install/configure ant tasks
> - Re-enable Jenkins integration test job
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-634) Automate Keycloak setup during integration tests
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-634:
---------------------------------
Summary: Automate Keycloak setup during integration tests
Key: ARTIF-634
URL: https://issues.jboss.org/browse/ARTIF-634
Project: Artificer
Issue Type: Task
Reporter: Brett Meyer
Assignee: Brett Meyer
Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete:
- Automate the realm import
- Automate the EAP/Wildfly admin user password
- Re-enable the server install/configure ant tasks
- Re-enable Jenkins integration test job
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-633) Work around RESTEasy issues affecting batch upload support in Wildfly
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-633?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-633:
------------------------------
Summary: Work around RESTEasy issues affecting batch upload support in Wildfly (was: Work around RESTEasy issues affecting batch support in Wildfly)
> Work around RESTEasy issues affecting batch upload support in Wildfly
> ---------------------------------------------------------------------
>
> Key: ARTIF-633
> URL: https://issues.jboss.org/browse/ARTIF-633
> Project: Artificer
> Issue Type: Bug
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> RESTEASY-1119 affects batch upload support in Wildfly. Part of the reason is that we're using deprecated code (ClientExecutor, etc.). As suggested, something like the following is a workaround:
> {code}
> ResteasyProviderFactory factory = ResteasyProviderFactory.getInstance();
> ResteasyProviderFactory.pushContext(javax.ws.rs.ext.Providers.class, factory);
> ResteasyClientBuilder resteasyClientBuilder = new
> ResteasyClientBuilder().providerFactory(factory);
> ResteasyClient client = resteasyClientBuilder.build();
> {code}
> But, that's only available in RE 3. We might have to pull the client-creation code into s-ramp-server/eap and s-ramp-server/wildfly (or upgrade wildfly in eap)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-633) Work around RESTEasy issues affecting batch support in Wildfly
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-633:
---------------------------------
Summary: Work around RESTEasy issues affecting batch support in Wildfly
Key: ARTIF-633
URL: https://issues.jboss.org/browse/ARTIF-633
Project: Artificer
Issue Type: Bug
Reporter: Brett Meyer
Assignee: Brett Meyer
RESTEASY-1119 affects batch upload support in Wildfly. Part of the reason is that we're using deprecated code (ClientExecutor, etc.). As suggested, something like the following is a workaround:
{code}
ResteasyProviderFactory factory = ResteasyProviderFactory.getInstance();
ResteasyProviderFactory.pushContext(javax.ws.rs.ext.Providers.class, factory);
ResteasyClientBuilder resteasyClientBuilder = new
ResteasyClientBuilder().providerFactory(factory);
ResteasyClient client = resteasyClientBuilder.build();
{code}
But, that's only available in RE 3. We might have to pull the client-creation code into s-ramp-server/eap and s-ramp-server/wildfly (or upgrade wildfly in eap)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-632) Deprecate Tomcat support
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-632?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-632:
------------------------------
Description: Until KEYCLOAK-932, deprecate Tomcat support. We could require the use of the standalone Keycloak appliance, external to the Tomcat instance, but it'll be work to configure/support and is probably not worth it.
> Deprecate Tomcat support
> ------------------------
>
> Key: ARTIF-632
> URL: https://issues.jboss.org/browse/ARTIF-632
> Project: Artificer
> Issue Type: Task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Until KEYCLOAK-932, deprecate Tomcat support. We could require the use of the standalone Keycloak appliance, external to the Tomcat instance, but it'll be work to configure/support and is probably not worth it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months