[JBoss JIRA] (SWSQE-796) Kiali Doc OKR Metrics
by Matthew Mahoney (Jira)
Matthew Mahoney created SWSQE-796:
-------------------------------------
Summary: Kiali Doc OKR Metrics
Key: SWSQE-796
URL: https://issues.jboss.org/browse/SWSQE-796
Project: Kiali QE
Issue Type: QE Task
Reporter: Matthew Mahoney
Currently Kiali Doc metrics are not represented in Tablue. Work with Kiali Docs folks to identify tests which will generate PQI/OKR metrics.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4142:
--------------------------------------
Summary: [GSS-RFE] UX design: Find feature in GDST/DMN 7.5 (was: [GSS-RFE] UX design: Search feature in GDST 7.5)
> [GSS-RFE] UX design: Find feature in GDST/DMN 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. Requirements
> See referenced document.
> 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, 11 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:
--------------------------------------
Description:
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. Requirements
See referenced document.
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
was:
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. Requirements
*Find function*
* Find text strings within "Data cells"
* Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
* “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
* Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
*UI Find/Search components*
* A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
* UI element that supports a long string query in the input field of the search box
*Find/Search Results*
* The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
* If there are No results: Presentation and state of the search component when users searches for something and gets no results.
* Search results shows strings that might: Appear once, Appear multiple times
* [FIND] Previous/Next arrows with focus, to navigate.
* Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
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
> [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. Requirements
> See referenced document.
> 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, 11 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:
--------------------------------------
Description:
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. Requirements
*Find function*
* Find text strings within "Data cells"
* Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
* “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
* Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
*UI Find/Search components*
* A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
* UI element that supports a long string query in the input field of the search box
*Find/Search Results*
* The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
* If there are No results: Presentation and state of the search component when users searches for something and gets no results.
* Search results shows strings that might: Appear once, Appear multiple times
* [FIND] Previous/Next arrows with focus, to navigate.
* Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
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
was:
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. Requirements
*Find function*
* Find text strings within "Data cells"
* Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
* “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
* Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
*UI Find/Search components*
* A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
* UI element that supports a long string query in the input field of the search box
*Find/Search Results*
* The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
* If there are No results: Presentation and state of the search component when users searches for something and gets no results.
* Search results shows strings that might: Appear once, Appear multiple times
* [FIND] Previous/Next arrows with focus, to navigate.
* Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
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
> [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. Requirements
> *Find function*
> * Find text strings within "Data cells"
> * Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
> * “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
> * Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
> *UI Find/Search components*
> * A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
> * UI element that supports a long string query in the input field of the search box
> *Find/Search Results*
> * The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
> * If there are No results: Presentation and state of the search component when users searches for something and gets no results.
> * Search results shows strings that might: Appear once, Appear multiple times
> * [FIND] Previous/Next arrows with focus, to navigate.
> * Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
> 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, 11 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:
--------------------------------------
Description:
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. Requirements
*Find function*
* Find text strings within "Data cells"
* Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
* “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
* Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
*UI Find/Search components*
* A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
* UI element that supports a long string query in the input field of the search box
*Find/Search Results*
* The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
* If there are No results: Presentation and state of the search component when users searches for something and gets no results.
* Search results shows strings that might: Appear once, Appear multiple times
* [FIND] Previous/Next arrows with focus, to navigate.
* Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
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
was:
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
> [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. Requirements
> *Find function*
> * Find text strings within "Data cells"
> * Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
> * “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
> * Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
> *UI Find/Search components*
> * A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
> * UI element that supports a long string query in the input field of the search box
> *Find/Search Results*
> * The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
> * If there are No results: Presentation and state of the search component when users searches for something and gets no results.
> * Search results shows strings that might: Appear once, Appear multiple times
> * [FIND] Previous/Next arrows with focus, to navigate.
> * Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
> 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, 11 months
[JBoss JIRA] (WFCORE-4551) Cannot add Elytron jdbc-realm using embedded server in admin mode
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4551?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-4551:
----------------------------------------
Component/s: Security
(was: CLI)
(was: Embedded)
Assignee: Darran Lofthouse (was: Jean Francois Denise)
> Cannot add Elytron jdbc-realm using embedded server in admin mode
> -----------------------------------------------------------------
>
> Key: WFCORE-4551
> URL: https://issues.jboss.org/browse/WFCORE-4551
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.0.0.Final, 9.0.1.Final
> Reporter: David Gill
> Assignee: Darran Lofthouse
> Priority: Major
>
> On a fresh a Wildfly install (tested on 16.final and 17.final) the following jboss-cli commands will fail to add an Elytron jdbc-realm to an embedded server using the ExampleDS data source that is predefined out-of-the-box:
> {noformat}
> embed-server --server-config=standalone.xml
> /subsystem=elytron/jdbc-realm=MyRealm:add(principal-query=[{sql="SELECT * FROM Users WHERE username = ?", data-source=ExampleDS}])
> {noformat}
> Resulting in this error:
> {noformat}
> ERROR [org.jboss.as.controller.management-operation] (pool-3-thread-1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("jdbc-realm" => "MyRealm")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.ExampleDS"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.MyRealm is missing [org.wildfly.data-source.ExampleDS]"]
> }
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.ExampleDS"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.MyRealm is missing [org.wildfly.data-source.ExampleDS]"]
> },
> "rolled-back" => true
> }
> {noformat}
> If you instead embed the server using {{--admin-only=false}} then the jdbc-realm will be added successfully.
> A workaround seems to be to first add and remove some other type of realm with the same name as the jdbc-realm you want to add, here for example using an identity-realm:
> {noformat}
> embed-server --server-config=standalone.xml
> # First add & remove a dummy realm with the same name as the jdbc-realm you want to add
> /subsystem=elytron/identity-realm=MyRealm:add(identity='dummy identity realm')
> /subsystem=elytron/identity-realm=MyRealm:remove
> # Now the jdbc-realm will add successfully
> /subsystem=elytron/jdbc-realm=MyRealm:add(principal-query=[{sql="SELECT * FROM Users WHERE username = ?", data-source=ExampleDS}])
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4551) Cannot add Elytron jdbc-realm using embedded server in admin mode
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4551?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-4551:
-------------------------------------
Component/s: Embedded
> Cannot add Elytron jdbc-realm using embedded server in admin mode
> -----------------------------------------------------------------
>
> Key: WFCORE-4551
> URL: https://issues.jboss.org/browse/WFCORE-4551
> Project: WildFly Core
> Issue Type: Bug
> Components: Embedded, Security
> Affects Versions: 8.0.0.Final, 9.0.1.Final
> Reporter: David Gill
> Assignee: Darran Lofthouse
> Priority: Major
>
> On a fresh a Wildfly install (tested on 16.final and 17.final) the following jboss-cli commands will fail to add an Elytron jdbc-realm to an embedded server using the ExampleDS data source that is predefined out-of-the-box:
> {noformat}
> embed-server --server-config=standalone.xml
> /subsystem=elytron/jdbc-realm=MyRealm:add(principal-query=[{sql="SELECT * FROM Users WHERE username = ?", data-source=ExampleDS}])
> {noformat}
> Resulting in this error:
> {noformat}
> ERROR [org.jboss.as.controller.management-operation] (pool-3-thread-1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("jdbc-realm" => "MyRealm")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.ExampleDS"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.MyRealm is missing [org.wildfly.data-source.ExampleDS]"]
> }
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.ExampleDS"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.MyRealm is missing [org.wildfly.data-source.ExampleDS]"]
> },
> "rolled-back" => true
> }
> {noformat}
> If you instead embed the server using {{--admin-only=false}} then the jdbc-realm will be added successfully.
> A workaround seems to be to first add and remove some other type of realm with the same name as the jdbc-realm you want to add, here for example using an identity-realm:
> {noformat}
> embed-server --server-config=standalone.xml
> # First add & remove a dummy realm with the same name as the jdbc-realm you want to add
> /subsystem=elytron/identity-realm=MyRealm:add(identity='dummy identity realm')
> /subsystem=elytron/identity-realm=MyRealm:remove
> # Now the jdbc-realm will add successfully
> /subsystem=elytron/jdbc-realm=MyRealm:add(principal-query=[{sql="SELECT * FROM Users WHERE username = ?", data-source=ExampleDS}])
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months