August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4615) Eliminated deprecated WorkerService constructors

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4615?page=com.atlassian.jira.plugi... ] Richard Opalka reassigned WFCORE-4615: -------------------------------------- Assignee: Richard Opalka (was: Flavia Rainone) > Eliminated deprecated WorkerService constructors > ------------------------------------------------ > > Key: WFCORE-4615 > URL: https://issues.jboss.org/browse/WFCORE-4615 > Project: WildFly Core > Issue Type: Enhancement > Components: IO > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 10.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-171) Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-171?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-171: ------------------------------------ [~luck3y] When will you provide fixed image? We have deadline for testing fill tomorrow (Thursday). > Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME > ------------------------------------------------------------ > > Key: WFWIP-171 > URL: https://issues.jboss.org/browse/WFWIP-171 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Is it expected? Is this work tracked somewhere? > [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blo... > [2] https://github.com/luck3y/jboss-eap-7-openshift-image/blob/CLOUD-3331/tem... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2274) ASYM_ENCRYPT: deprecate sign_msgs

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2274?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2274: -------------------------------- {quote} HMAC needs its own shared key, so this may be one reason to keep the signing as part of the encryption protocol (so it can reuse the same shared secret) {quote} Hmm, I don't like this; as a matter of fact, I removed the signing because I wanted separation of concerns (encryption and signing). But there are ways of fetching the secret key from Encrypt: using GET_SECRET_KEY as event sent up or down the stack does this. This is currently used by SSL_KEY_EXCHANGE, as it also needs access to the secret key. Wrt the changes you mentioned: I prefer _additional (separate) protocols_ to implement something that's different than encryption. But, of course, if you wanted to add GCM mode, than Encrypt itself would have to be modified. If you have suggestions, I'm all ears. If you even want to _implement_ something, I'm all for it, but I can't do this myself! > ASYM_ENCRYPT: deprecate sign_msgs > --------------------------------- > > Key: JGRP-2274 > URL: https://issues.jboss.org/browse/JGRP-2274 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.12 > > > In {{ASYM_ENCRYPT}}, signing messages means that the checksum of an encrypted message is computed and used together with the secret key of the sender to sign the message. On the receiver side, the public key of the sender is used to validate the signature. > However, this is redundant, as decryption of a message will fail if the contents have been changed. > If needed, signing of messages can be done in a separate protocol. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12381) DH_KEY_EXCHANGE JGroups should be configured from Elytron capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12381?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12381: ---------------------------------- Affects Version/s: 17.0.1.Final 17.0.0.Final > DH_KEY_EXCHANGE JGroups should be configured from Elytron capabilities > ---------------------------------------------------------------------- > > Key: WFLY-12381 > URL: https://issues.jboss.org/browse/WFLY-12381 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.0.Final, 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > DH_KEY_EXCHANGE is relatively new and does not integrate with Elytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12164) SSL_KEY_EXCHANGE JGroups protocol should be configured from Elytron capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12164?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12164: ---------------------------------- Affects Version/s: 17.0.1.Final 17.0.0.Final > SSL_KEY_EXCHANGE JGroups protocol should be configured from Elytron capabilities > -------------------------------------------------------------------------------- > > Key: WFLY-12164 > URL: https://issues.jboss.org/browse/WFLY-12164 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.0.Beta1, 17.0.0.Final, 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > See JGRP-2157 – does not currently integrate with Elytron. The fix is to provide a protocol resource that requires an SSL context capability from Elytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12164) SSL_KEY_EXCHANGE JGroups protocol should be configured from Elytron capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12164?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12164: ---------------------------------- Summary: SSL_KEY_EXCHANGE JGroups protocol should be configured from Elytron capabilities (was: Support for SSL_KEY_EXCHANGE JGroups protocol with Elytron) > SSL_KEY_EXCHANGE JGroups protocol should be configured from Elytron capabilities > -------------------------------------------------------------------------------- > > Key: WFLY-12164 > URL: https://issues.jboss.org/browse/WFLY-12164 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > See JGRP-2157 – does not currently integrate with Elytron. The fix is to provide a protocol resource that requires an SSL context capability from Elytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12381) DH_KEY_EXCHANGE JGroups should be configured from Elytron capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12381?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12381: ---------------------------------- Summary: DH_KEY_EXCHANGE JGroups should be configured from Elytron capabilities (was: Support for DH_KEY_EXCHANGE JGroups protocol with Elytron) > DH_KEY_EXCHANGE JGroups should be configured from Elytron capabilities > ---------------------------------------------------------------------- > > Key: WFLY-12381 > URL: https://issues.jboss.org/browse/WFLY-12381 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > DH_KEY_EXCHANGE is relatively new and does not -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12381) DH_KEY_EXCHANGE JGroups should be configured from Elytron capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12381?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12381: ---------------------------------- Description: DH_KEY_EXCHANGE is relatively new and does not integrate with Elytron. (was: DH_KEY_EXCHANGE is relatively new and does not ) > DH_KEY_EXCHANGE JGroups should be configured from Elytron capabilities > ---------------------------------------------------------------------- > > Key: WFLY-12381 > URL: https://issues.jboss.org/browse/WFLY-12381 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > DH_KEY_EXCHANGE is relatively new and does not integrate with Elytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4452) [GDST] Wrong FQCN is selected if the end matches.

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4452?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4452: -------------------------------- Labels: drools-tools (was: ) > [GDST] Wrong FQCN is selected if the end matches. > ------------------------------------------------- > > Key: DROOLS-4452 > URL: https://issues.jboss.org/browse/DROOLS-4452 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.26.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > If the column uses class Person. The FQCN resolver that fills the DMO uses the first import that end with the class name. > For example if the list contains: > * org.test.AnotherPerson > * org.test.Person > Then first item is selected instead of the second. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4452) [GDST] Wrong FQCN is selected if the end matches.

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4452?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4452: -------------------------------- Affects Version/s: 7.26.0.Final > [GDST] Wrong FQCN is selected if the end matches. > ------------------------------------------------- > > Key: DROOLS-4452 > URL: https://issues.jboss.org/browse/DROOLS-4452 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.26.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > If the column uses class Person. The FQCN resolver that fills the DMO uses the first import that end with the class name. > For example if the list contains: > * org.test.AnotherPerson > * org.test.Person > Then first item is selected instead of the second. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2019