[JBoss JIRA] (HAWKULARQE-81) Baseline #3
by viet nguyen (JIRA)
[ https://issues.jboss.org/browse/HAWKULARQE-81?page=com.atlassian.jira.plu... ]
viet nguyen commented on HAWKULARQE-81:
---------------------------------------
After set query window to a fix range (March 28 02:00, -30 minutes) the metrics tallies are consistent between 4 runs.
[^March28_0200_raw.zip]
> Baseline #3
> -----------
>
> Key: HAWKULARQE-81
> URL: https://issues.jboss.org/browse/HAWKULARQE-81
> Project: Hawkular QE
> Issue Type: Sub-task
> Reporter: viet nguyen
> Assignee: viet nguyen
> Attachments: March28_0200_raw.zip
>
>
> * Run pyme on master to eliminate vpn slowness
> * Fix query start-end window
> * Update pyme endpoint to increase metrics to 30 (currently 2)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (SECURITY-966) Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/SECURITY-966?page=com.atlassian.jira.plug... ]
Stefan Guilhen resolved SECURITY-966.
-------------------------------------
Resolution: Done
SecurityKeyManager has been changed to extend X509ExtendedKeyManager, thus becoming compatible with the Elytron SSL contexts.
> Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
> ----------------------------------------------------------------------------------------------
>
> Key: SECURITY-966
> URL: https://issues.jboss.org/browse/SECURITY-966
> Project: PicketBox
> Issue Type: Bug
> Components: JBossSX, Security-SPI
> Affects Versions: PicketBox_5_0_0.Beta1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
> Fix For: PicketBox_5_0_0.Final
>
>
> It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
> {noformat}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
> },
> "rolled-back" => true
> }
> {noformat}
> The exported KeyManager doesn't extend the X509ExtendedKeyManager class. A simple change to SecurityKeyManager should make it compatible with the Elytron ssl contexts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (SECURITY-966) Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/SECURITY-966?page=com.atlassian.jira.plug... ]
Stefan Guilhen closed SECURITY-966.
-----------------------------------
> Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
> ----------------------------------------------------------------------------------------------
>
> Key: SECURITY-966
> URL: https://issues.jboss.org/browse/SECURITY-966
> Project: PicketBox
> Issue Type: Bug
> Components: JBossSX, Security-SPI
> Affects Versions: PicketBox_5_0_0.Beta1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
> Fix For: PicketBox_5_0_0.Final
>
>
> It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
> {noformat}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
> },
> "rolled-back" => true
> }
> {noformat}
> The exported KeyManager doesn't extend the X509ExtendedKeyManager class. A simple change to SecurityKeyManager should make it compatible with the Elytron ssl contexts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (SECURITY-966) Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/SECURITY-966?page=com.atlassian.jira.plug... ]
Stefan Guilhen updated SECURITY-966:
------------------------------------
Fix Version/s: PicketBox_5_0_0.Final
> Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
> ----------------------------------------------------------------------------------------------
>
> Key: SECURITY-966
> URL: https://issues.jboss.org/browse/SECURITY-966
> Project: PicketBox
> Issue Type: Bug
> Components: JBossSX, Security-SPI
> Affects Versions: PicketBox_5_0_0.Beta1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
> Fix For: PicketBox_5_0_0.Final
>
>
> It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
> {noformat}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
> },
> "rolled-back" => true
> }
> {noformat}
> The exported KeyManager doesn't extend the X509ExtendedKeyManager class. A simple change to SecurityKeyManager should make it compatible with the Elytron ssl contexts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (SECURITY-966) Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/SECURITY-966?page=com.atlassian.jira.plug... ]
Stefan Guilhen updated SECURITY-966:
------------------------------------
Description:
It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
{noformat}
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
},
"rolled-back" => true
}
{noformat}
The exported KeyManager doesn't extend the X509ExtendedKeyManager class. A simple change to SecurityKeyManager should make it compatible with the Elytron ssl contexts.
was:
It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
{noformat}
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
},
"rolled-back" => true
}
{noformat}
The exported key manager is announced as org.wildfly.security.key-managers capability. Hence it is expected to work wherever the capability is requested.
> Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
> ----------------------------------------------------------------------------------------------
>
> Key: SECURITY-966
> URL: https://issues.jboss.org/browse/SECURITY-966
> Project: PicketBox
> Issue Type: Bug
> Components: JBossSX, Security-SPI
> Affects Versions: PicketBox_5_0_0.Beta1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
>
> It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
> {noformat}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
> },
> "rolled-back" => true
> }
> {noformat}
> The exported KeyManager doesn't extend the X509ExtendedKeyManager class. A simple change to SecurityKeyManager should make it compatible with the Elytron ssl contexts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (SECURITY-966) Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/SECURITY-966?page=com.atlassian.jira.plug... ]
Stefan Guilhen updated SECURITY-966:
------------------------------------
Description:
It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
{noformat}
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
},
"rolled-back" => true
}
{noformat}
The exported key manager is announced as org.wildfly.security.key-managers capability. Hence it is expected to work wherever the capability is requested.
was:
It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
},
"rolled-back" => true
}
The exported key manager is announced as org.wildfly.security.key-managers capability. Hence it is expected to work wherever the capability is requested.
> Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
> ----------------------------------------------------------------------------------------------
>
> Key: SECURITY-966
> URL: https://issues.jboss.org/browse/SECURITY-966
> Project: PicketBox
> Issue Type: Bug
> Components: JBossSX, Security-SPI
> Affects Versions: PicketBox_5_0_0.Beta1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
>
> It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
> {noformat}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
> },
> "rolled-back" => true
> }
> {noformat}
> The exported key manager is announced as org.wildfly.security.key-managers capability. Hence it is expected to work wherever the capability is requested.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (SECURITY-966) Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
by Stefan Guilhen (JIRA)
Stefan Guilhen created SECURITY-966:
---------------------------------------
Summary: Key manager exported from legacy JSSE security domain does not work Elytron server-ssl-context
Key: SECURITY-966
URL: https://issues.jboss.org/browse/SECURITY-966
Project: PicketBox
Issue Type: Bug
Components: JBossSX, Security-SPI
Affects Versions: PicketBox_5_0_0.Beta1
Reporter: Stefan Guilhen
Assignee: Stefan Guilhen
It is not possible to use a key manager exported from legacy security domain (i.e. elytron-key-manager) in Elytron server-ssl-context. It results in:
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
},
"rolled-back" => true
}
The exported key manager is announced as org.wildfly.security.key-managers capability. Hence it is expected to work wherever the capability is requested.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years