[JBoss JIRA] (JGRP-2275) ASYM_ENCRYPT: encrypt join response
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2275?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2275:
--------------------------------
Ditto for {{INSTALL_MERGE_VIEW}}; same logic as for {{JOIN_RSP}}..
> ASYM_ENCRYPT: encrypt join response
> -----------------------------------
>
> Key: JGRP-2275
> URL: https://issues.jboss.org/browse/JGRP-2275
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.12
>
>
> In {{ASYM_ENCRYPT}}, when a new member joins, it sends a JOIN-REQ to the coordinator (unencrypted, as it does not yet have the secret key).
> The coordinator skips decryption, creates a JOIN-RSP, and sends it to the joiner *unencrypted*. The reason is that the joiner doesn't yet have the secret key, so it couldn't possibly decrypt the JOIN-RSP and install the view.
> (This is btw not a security issue as subsequent messages *are* encrypted and a rogue member would not be able to decrypt them. However, a rogue member would be able to join the cluster.
> To prevent this, the JOIN-RSP sent by the coordinator to the joiner will be encrypted. The joiner will not be able to decrypt it and simply drops it, but it also asks the keyserver (coord) for the secret key. Once the secret key has been received, the (retransmitted) JOIN-RSP will be received, decrypted with the received secret key and the view can be installed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3914) HTTPSchemeServiceAuthModule contructor is not defined
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created WFCORE-3914:
--------------------------------------
Summary: HTTPSchemeServiceAuthModule contructor is not defined
Key: WFCORE-3914
URL: https://issues.jboss.org/browse/WFCORE-3914
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 3.0.10.Final
Environment: - EAP7.1.0
Reporter: Hisanobu Okuda
Assignee: Darran Lofthouse
JASPI does not work, since HTTPSchemeServiceAuthModule contructor is not defined.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3913) HTTPSchemeServiceAuthModule contructor is not defined
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created WFCORE-3913:
--------------------------------------
Summary: HTTPSchemeServiceAuthModule contructor is not defined
Key: WFCORE-3913
URL: https://issues.jboss.org/browse/WFCORE-3913
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 3.0.10.Final
Environment: - EAP7.1.0
Reporter: Hisanobu Okuda
Assignee: Darran Lofthouse
JASPI does not work, since HTTPSchemeServiceAuthModule contructor is not defined.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10522) Support Eclipse MicroProfile Config
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-10522:
----------------------------------
Summary: Support Eclipse MicroProfile Config
Key: WFLY-10522
URL: https://issues.jboss.org/browse/WFLY-10522
Project: WildFly
Issue Type: Feature Request
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Support Eclipse MicroProfile Config for applications deployed in WildFly.
The integration uses the smallrye-config component to provide the MicroProfile Config implementation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2586) CSS/HTML for scenario simulation UX
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2586?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2586:
-------------------------------------
[~manstis] Sorry I feel like concerning still about something, but let me bring my point I stated also in google doc with the wireframes. From selenium regression testing point of view is more appropriate to use docker panel on right side, as it is not implemented as html5 canvas.
> CSS/HTML for scenario simulation UX
> -----------------------------------
>
> Key: DROOLS-2586
> URL: https://issues.jboss.org/browse/DROOLS-2586
> Project: Drools
> Issue Type: Task
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-06-05 at 3.44.15 PM.png
>
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide CSS/HTML to support wireframe designs which includes the following:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer
by Gail Badner (JIRA)
Gail Badner created WFLY-10520:
----------------------------------
Summary: Add Hibernate ORM 5.3 compatibility transformer
Key: WFLY-10520
URL: https://issues.jboss.org/browse/WFLY-10520
Project: WildFly
Issue Type: Task
Components: JPA / Hibernate
Reporter: Gail Badner
Assignee: Scott Marlow
Fix For: 14.0.0.CR1
A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month