[JBoss JIRA] (WFCORE-4459) outbound-socket-binding element should allow grouping which subsystems can reference
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFCORE-4459?page=com.atlassian.jira.plugi... ]
Radoslav Husar closed WFCORE-4459.
----------------------------------
Resolution: Rejected
Rejecting in favor of WFLY-12222.
> outbound-socket-binding element should allow grouping which subsystems can reference
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-4459
> URL: https://issues.jboss.org/browse/WFCORE-4459
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.0.0.Beta4
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> Useful especially for clustering subsystems like jgroups discovery protocols, infinispan hotrod servers, and mod_cluster balancers.
> ----
> JGroups configuration can use two different ways to configure cluster detection
> ------ older configuration is via protocol properties --
> <protocol type="TCPPING">
> <property name="initial_hosts">host[7600]</property>
> ------ new configuration via socket reference
> <socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/>
> ...
> <outbound-socket-binding name="ref-a">
> <remote-destination host="127.0.0.1" port="7600"/>
> </outbound-socket-binding>
> -----------
> with the old option it is possible to use an expression to set all hosts in a cluster.
> The new one need to have all outbound connections listed which is harder to maintain.
> As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration.
> So a configuration like this would enhance that
> {code:xml}
> <outbound-socket-binding-group>
> <outbound-socket-binding name="ref-a">
> <remote-destination host="host1" port="7600"/>
> </outbound-socket-binding>
> <outbound-socket-binding name="ref-b">
> <remote-destination host="host2" port="7600"/>
> </outbound-socket-binding>
> </outbound-socket-binding-group>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-3767) Ability to configure each aggregated realm separately
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/WFCORE-3767?page=com.atlassian.jira.plugi... ]
Farah Juma resolved WFCORE-3767.
--------------------------------
Resolution: Duplicate Issue
> Ability to configure each aggregated realm separately
> -----------------------------------------------------
>
> Key: WFCORE-3767
> URL: https://issues.jboss.org/browse/WFCORE-3767
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Security
> Reporter: Jean Francois Denise
> Priority: Major
> Attachments: conf-extract
>
>
> The use-case is EXTERNAL + role derived from mgmt-groups.properties. To achieve this use-case a realm aggregate is needed. Each aggregated realm can't be configured with its own principal-transformer. So each realm is impacted by the transformer set on the aggregation.
> Allowing to configure each realm separately would offer the flexibility to isolate principal transformation for authorisation and not impact authentication.
> Authentication impact is quite important, an alias in the trust-store and the decoded principal must match exactly. Something that shouldn't be made mandatory in this case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-3767) Ability to configure each aggregated realm separately
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/WFCORE-3767?page=com.atlassian.jira.plugi... ]
Farah Juma commented on WFCORE-3767:
------------------------------------
I'm going to close this one since it's a duplicate of WFCORE-4496.
> Ability to configure each aggregated realm separately
> -----------------------------------------------------
>
> Key: WFCORE-3767
> URL: https://issues.jboss.org/browse/WFCORE-3767
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Security
> Reporter: Jean Francois Denise
> Priority: Major
> Attachments: conf-extract
>
>
> The use-case is EXTERNAL + role derived from mgmt-groups.properties. To achieve this use-case a realm aggregate is needed. Each aggregated realm can't be configured with its own principal-transformer. So each realm is impacted by the transformer set on the aggregation.
> Allowing to configure each realm separately would offer the flexibility to isolate principal transformation for authorisation and not impact authentication.
> Authentication impact is quite important, an alias in the trust-store and the decoded principal must match exactly. Something that shouldn't be made mandatory in this case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Search feature in GDST 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4142:
--------------------------------------
Sprint: 2019 Week 23-25
> [GSS-RFE] UX design: Search feature in GDST 7.5
> -----------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-12224) CLI output is doubled after embed-server reload
by Jean Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFLY-12224?page=com.atlassian.jira.plugin... ]
Jean Francois Denise edited comment on WFLY-12224 at 6/21/19 10:03 AM:
-----------------------------------------------------------------------
It occurs even calling :reload operation.
The duplicated output comes from logging. [~jamezp], I isolated the commit that introduced this:
https://github.com/wildfly/wildfly-core/commit/766c3991e2b11eedda4be83040...
was (Author: jdenise):
It occurs even calling :reload operation.
The duplicated output comes from logging. [~jamezp], I solated the commit that introduced this:
https://github.com/wildfly/wildfly-core/commit/766c3991e2b11eedda4be83040...
> CLI output is doubled after embed-server reload
> -----------------------------------------------
>
> Key: WFLY-12224
> URL: https://issues.jboss.org/browse/WFLY-12224
> Project: WildFly
> Issue Type: Bug
> Components: CLI, Logging
> Affects Versions: 18.0.0.Beta1
> Reporter: Ondrej Kotek
> Assignee: Jean Francois Denise
> Priority: Major
>
> CLI output is doubled after embed-server reload:
> {noformat}
> [okotek@localhost wildfly-18.0.0.Beta1-SNAPSHOT]$ ./bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-server
> [standalone@embedded /] :whoami
> {
> "outcome" => "success",
> "result" => {"identity" => {"username" => "anonymous"}}
> }
> [standalone@embedded /] reload
> [standalone@embedded /] :whoami
> 12:34:27,735 INFO [org.jboss.as.cli.CommandContext] (CLI command) {
> "outcome" => "success",
> "result" => {"identity" => {"username" => "anonymous"}}
> }
> {
> "outcome" => "success",
> "result" => {"identity" => {"username" => "anonymous"}}
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months