[JBoss JIRA] (ELY-1975) Update AcmeClientSpi#obtainCertificate so that it obtains the order URL from the response to newOrder
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/ELY-1975?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated ELY-1975:
----------------------------------
Fix Version/s: 1.13.0.CR1
> Update AcmeClientSpi#obtainCertificate so that it obtains the order URL from the response to newOrder
> -----------------------------------------------------------------------------------------------------
>
> Key: ELY-1975
> URL: https://issues.redhat.com/browse/ELY-1975
> Project: WildFly Elytron
> Issue Type: Task
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Major
> Fix For: 1.13.0.CR1
>
>
> {{AcmeClientSpi#obtainCertificate}} currently determines the order URL that should be used by taking the {{Location}} header from the response to finalizing the order (the ACME protocol specification has an example response that includes this header). This works when obtaining certificates from Let's Encrypt and Boulder. However, it seems that EJBCA does not include the {{Location}} header in the response to finalizing the order. {{AcmeClientSpi#obtainCertificate}} should instead use the Location header from the response to {{newOrder}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ELY-1975) Update AcmeClientSpi#obtainCertificate so that it obtains the order URL from the response to newOrder
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/ELY-1975?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse resolved ELY-1975.
-----------------------------------
Resolution: Done
> Update AcmeClientSpi#obtainCertificate so that it obtains the order URL from the response to newOrder
> -----------------------------------------------------------------------------------------------------
>
> Key: ELY-1975
> URL: https://issues.redhat.com/browse/ELY-1975
> Project: WildFly Elytron
> Issue Type: Task
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Major
> Fix For: 1.13.0.CR1
>
>
> {{AcmeClientSpi#obtainCertificate}} currently determines the order URL that should be used by taking the {{Location}} header from the response to finalizing the order (the ACME protocol specification has an example response that includes this header). This works when obtaining certificates from Let's Encrypt and Boulder. However, it seems that EJBCA does not include the {{Location}} header in the response to finalizing the order. {{AcmeClientSpi#obtainCertificate}} should instead use the Location header from the response to {{newOrder}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5026) Remove blinkinking in Test Tools pannel
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5026?page=com.atlassian.jira.plug... ]
Yeser Amer commented on DROOLS-5026:
------------------------------------
This requires a change on appformer docks API.
> Remove blinkinking in Test Tools pannel
> ---------------------------------------
>
> Key: DROOLS-5026
> URL: https://issues.redhat.com/browse/DROOLS-5026
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.30.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screencast from 02-07-2020.webm
>
>
> Change Test Tools behavior to stop blinking every time when
> focus in *Grid* are moving through *Header*.
> Now if you move focus in *Grid* particularly for *Header*
> rows (by using keyboard arrows keys) then Test Tools icon blinks.
> That is not happening with values in the Grid.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ]
Eduardo Martins commented on WFLY-13051:
----------------------------------------
[~nimo22] That shouldn't happen, the recurrent task should be cancelled, can you please re-check that and if that happens submit a new bug JIRA and attach an app project or WFLY integration test that I may use to recreate the issue?
> provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService
> ------------------------------------------------------------------
>
> Key: WFLY-13051
> URL: https://issues.redhat.com/browse/WFLY-13051
> Project: WildFly
> Issue Type: Enhancement
> Components: Concurrency Utilities
> Affects Versions: 19.0.0.Beta1
> Reporter: nimo stephan
> Assignee: Eduardo Martins
> Priority: Major
>
> Using
> {code:java}
> @Resource
> private ManagedScheduledExecutorService executor;
> {code}
> provides no possiblity to setRemoveOnCancelPolicy to true.
> A casting within a method:
> {code:java}
> ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true);
> {code}
> throws the error:
> {code:java}
> Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap')
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246)
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388)
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68)
> {code}
> Please provide option to cast or if not possible to add the property
> {code:java}
> setRemoveOnCancelPolicy()
> {code}
> within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (SWSQE-966) UI Automations - Check Traces tab functionality
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-966?page=com.atlassian.jira.plugin... ]
Hayk Hovsepyan updated SWSQE-966:
---------------------------------
Sprint: Kiali Sprint #28, Kiali Sprint #30, Kiali Sprint #41 (was: Kiali Sprint #28, Kiali Sprint #30)
> UI Automations - Check Traces tab functionality
> -----------------------------------------------
>
> Key: SWSQE-966
> URL: https://issues.redhat.com/browse/SWSQE-966
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Major
> Labels: automation
>
> Traces tab of Kiali is not automated in UI Automations framework.
> We need to automate:
> 1. Traces menu clicking and verifying the opened page.
> 2. Traces tab. Click, no errors, no login asked.
> 3. Search Traces in Traces tab. Verify that it shows traces or a message that traces does not exist.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month