[JBoss JIRA] (WFCORE-4128) Support hex encoding in jdbc-realm for elytron
by Jan Kalina (JIRA)
Jan Kalina created WFCORE-4128:
----------------------------------
Summary: Support hex encoding in jdbc-realm for elytron
Key: WFCORE-4128
URL: https://issues.jboss.org/browse/WFCORE-4128
Project: WildFly Core
Issue Type: Feature Request
Components: Security
Affects Versions: 5.0.0.Alpha7
Reporter: Jan Kalina
Assignee: Jan Kalina
Old database login-module can be configured passing the attribute {{hashEncoding}}, for example:
{code:xml}
<login-module code="Database" flag="required">
<module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/>
<module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/>
<module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/>
<module-option name="hashAlgorithm" value="SHA-1"/>
<module-option name="hashEncoding" value="hex"/>
<module-option name="hashCharset" value="UTF-8"/>
</login-module>
{code}
Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron.
Think also about the charset attribute.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFCORE-3939) Add PersistentResourceXMLParser support for logical grouping of child resources
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3939?page=com.atlassian.jira.plugi... ]
Jeff Mesnil resolved WFCORE-3939.
---------------------------------
Resolution: Won't Do
Rejected as explained in https://github.com/wildfly/wildfly-core/pull/3372#issuecomment-422873735
> Add PersistentResourceXMLParser support for logical grouping of child resources
> -------------------------------------------------------------------------------
>
> Key: WFCORE-3939
> URL: https://issues.jboss.org/browse/WFCORE-3939
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Affects Versions: 6.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> One of the limitations of PersistentResourceXMLParser preventing its use within the clustering subsystems is the lack of the ability to group child resources. For example, the JGroups subsystem's root resource contains 2 attributes and 2 child resources, where child resources are logically grouped within an attribute groups. The JGroups subsystem in one such example:
> {code:xml}
> <channels default="...">
> <channel name="..." stack="..."/>
> <channel name="..."/>
> </channels>
> <stacks default="...">
> <stack name="..."/>
> <stack name="..."/>
> </stacks>
> {code}
> Here, we need the ability to group specific children within the element of an attribute group.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBMETA-404) Validation errors with "jboss-web_11_0.xsd
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/JBMETA-404?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet commented on JBMETA-404:
------------------------------------------
[~wolfgangknauf]this is updated in current master with some typos
> Validation errors with "jboss-web_11_0.xsd
> ------------------------------------------
>
> Key: JBMETA-404
> URL: https://issues.jboss.org/browse/JBMETA-404
> Project: JBoss Metadata
> Issue Type: Bug
> Affects Versions: 10.0.2.Final
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
> Fix For: 12.0.0.Final
>
>
> Eclipse reports some errors when validating a "jboss-web.xml" file which defines the 11.0 xsd.
> First problem: "web-app_3_1.xsd" is imported. The target namespace seems to be invalid, it should be "http://xmlns.jcp.org/xml/ns/javaee" instead of "http://java.sun.com/xml/ns/javaee"
> <xsd:import namespace="http://xmlns.jcp.org/xml/ns/javaee" schemaLocation="http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"/>
> The validation error: *"The namespace attribute 'http://java.sun.com/xml/ns/javaee' of an import element information must be identical to the targetNamespace attribute 'http://xmlns.jcp.org/xml/ns/javaee' of the imported document".*
> It would probably also make sense to include the full schemaLocation URL ;-).
> After fixing the namespace, there are four more errors left:
> *src-resolve: Cannot resolve the name 'jboss:jndiEnvironmentRefsGroup' to a( n ) group component
> src-resolve: Cannot resolve the name 'javaee:generic-booleanType' to a( n ) 'simpleType definition' component
> src-ct.2.1: Complex type definition Representation Error for type 'symbolic-link-allowedType' ...
> src-resolve: Cannot resolve the name 'jboss:security-roleType' to a( n ) 'type definition' component*
> The first two errors: previous versions of jboss-web.xsd imported "jboss-common_6_0.xsd" which defined a "jndiEnvironmentRefsGroup". This file also imported "javaee_6.xsd", which defines the "generic-booleanType".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBMETA-404) Validation errors with "jboss-web_11_0.xsd
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/JBMETA-404?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet edited comment on JBMETA-404 at 9/26/18 2:57 AM:
-------------------------------------------------------------------
[~wolfgangknauf]this is updated in current master (which should be the base for 12.0.0.Final) with some typos
was (Author: ehugonnet):
[~wolfgangknauf]this is updated in current master with some typos
> Validation errors with "jboss-web_11_0.xsd
> ------------------------------------------
>
> Key: JBMETA-404
> URL: https://issues.jboss.org/browse/JBMETA-404
> Project: JBoss Metadata
> Issue Type: Bug
> Affects Versions: 10.0.2.Final
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
> Fix For: 12.0.0.Final
>
>
> Eclipse reports some errors when validating a "jboss-web.xml" file which defines the 11.0 xsd.
> First problem: "web-app_3_1.xsd" is imported. The target namespace seems to be invalid, it should be "http://xmlns.jcp.org/xml/ns/javaee" instead of "http://java.sun.com/xml/ns/javaee"
> <xsd:import namespace="http://xmlns.jcp.org/xml/ns/javaee" schemaLocation="http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"/>
> The validation error: *"The namespace attribute 'http://java.sun.com/xml/ns/javaee' of an import element information must be identical to the targetNamespace attribute 'http://xmlns.jcp.org/xml/ns/javaee' of the imported document".*
> It would probably also make sense to include the full schemaLocation URL ;-).
> After fixing the namespace, there are four more errors left:
> *src-resolve: Cannot resolve the name 'jboss:jndiEnvironmentRefsGroup' to a( n ) group component
> src-resolve: Cannot resolve the name 'javaee:generic-booleanType' to a( n ) 'simpleType definition' component
> src-ct.2.1: Complex type definition Representation Error for type 'symbolic-link-allowedType' ...
> src-resolve: Cannot resolve the name 'jboss:security-roleType' to a( n ) 'type definition' component*
> The first two errors: previous versions of jboss-web.xsd imported "jboss-common_6_0.xsd" which defined a "jndiEnvironmentRefsGroup". This file also imported "javaee_6.xsd", which defines the "generic-booleanType".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3020) [DMN Designer] Data Types - Constraints - Expression option component
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3020?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3020:
-------------------------------------
[~karreiro] Thanks for clarification, please have a look on acceptance criteria and let me know what will be the behavior.
> [DMN Designer] Data Types - Constraints - Expression option component
> ---------------------------------------------------------------------
>
> Key: DROOLS-3020
> URL: https://issues.jboss.org/browse/DROOLS-3020
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: edit-decision.png
>
>
> - When "Expression" is selected in the _Base Component_, one field (value) must be loaded in the _Base Component_;
> - The field is a simple input without any validation;
> - The constraint type and the value (form the input field) must be set in the Data Type.
> h2. Acceptance test
> - No ui input fields for constraints visible
> - No ui input fields for constraints enabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3020) [DMN Designer] Data Types - Constraints - Expression option component
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3020?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3020:
--------------------------------
Description:
- When "Expression" is selected in the _Base Component_, one field (value) must be loaded in the _Base Component_;
- The field is a simple input without any validation;
- The constraint type and the value (form the input field) must be set in the Data Type.
h2. Acceptance test
- No ui input fields for constraints visible
- No ui input fields for constraints enabled
was:
- When "Expression" is selected in the _Base Component_, one field (value) must be loaded in the _Base Component_;
- The field is a simple input without any validation;
- The constraint type and the value (form the input field) must be set in the Data Type.
> [DMN Designer] Data Types - Constraints - Expression option component
> ---------------------------------------------------------------------
>
> Key: DROOLS-3020
> URL: https://issues.jboss.org/browse/DROOLS-3020
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: edit-decision.png
>
>
> - When "Expression" is selected in the _Base Component_, one field (value) must be loaded in the _Base Component_;
> - The field is a simple input without any validation;
> - The constraint type and the value (form the input field) must be set in the Data Type.
> h2. Acceptance test
> - No ui input fields for constraints visible
> - No ui input fields for constraints enabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Simple range option component
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3019:
--------------------------------
Description:
- When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
- The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
- The constraint type, the min. and the max values must be must be set in the Data Type.
h2. Acceptance Test
h3. Default data type
- Able to store just min
- Able to store just max
- Able to store both min and max
- Max can not be lover than min and vice versa
- Can not put string to where number expected
- Try to put conflicting value into table cell
h3. Custom data type
- Min max ui input fields not visible
was:
- When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
- The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
- The constraint type, the min. and the max values must be must be set in the Data Type.
> [DMN Designer] Data Types - Constraints - Simple range option component
> -----------------------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: edit-decision.png
>
>
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Simple range option component
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3019:
-------------------------------------
[~karreiro] Please go trough acceptance criteria and let me know what will be implemented
> [DMN Designer] Data Types - Constraints - Simple range option component
> -----------------------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: edit-decision.png
>
>
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3018) [DMN Designer] Data Types - Constraints - None option component
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3018?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3018:
--------------------------------
Description:
- When "None" is selected in the _Base Component_, no constraint must be set in the Data Type and no element should be loaded in the _Base Component_.
h2. Acceptance test
h3. Manage Custom Data Type dialog
- When *none* constraint selected, other input elements for constraints are hidden
- When *none* constraint selected, other input elements for constraints are disabled
h3. Output Data Type select box
- When *none* constraint selected, other input elements for constraints are hidden
- When *none* constraint selected, other input elements for constraints are disabled
was:
- When "None" is selected in the _Base Component_, no constraint must be set in the Data Type and no element should be loaded in the _Base Component_.
h2. Acceptance test
h3. Manage Custom Data Type dialog
- When *none* constraint selected, other input elements for constraints are hidden
- When *none* constraint selected, other input elements for constraints are disabled
h3. Output Data Type select box
- When *none* constraint selected, other input elements for constraints are hidden
- When *none* constraint selected, other input elements for constraints are disabled
> [DMN Designer] Data Types - Constraints - None option component
> ---------------------------------------------------------------
>
> Key: DROOLS-3018
> URL: https://issues.jboss.org/browse/DROOLS-3018
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: edit-decision.png
>
>
> - When "None" is selected in the _Base Component_, no constraint must be set in the Data Type and no element should be loaded in the _Base Component_.
> h2. Acceptance test
> h3. Manage Custom Data Type dialog
> - When *none* constraint selected, other input elements for constraints are hidden
> - When *none* constraint selected, other input elements for constraints are disabled
> h3. Output Data Type select box
> - When *none* constraint selected, other input elements for constraints are hidden
> - When *none* constraint selected, other input elements for constraints are disabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3018) [DMN Designer] Data Types - Constraints - None option component
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3018?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3018:
-------------------------------------
[~karreiro] Thanks for clarification, I put two options to acceptance criteria (visible, hidden) could you please choose which one will be used?
> [DMN Designer] Data Types - Constraints - None option component
> ---------------------------------------------------------------
>
> Key: DROOLS-3018
> URL: https://issues.jboss.org/browse/DROOLS-3018
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: edit-decision.png
>
>
> - When "None" is selected in the _Base Component_, no constraint must be set in the Data Type and no element should be loaded in the _Base Component_.
> h2. Acceptance test
> h3. Manage Custom Data Type dialog
> - When *none* constraint selected, other input elements for constraints are hidden
> - When *none* constraint selected, other input elements for constraints are disabled
> h3. Output Data Type select box
> - When *none* constraint selected, other input elements for constraints are hidden
> - When *none* constraint selected, other input elements for constraints are disabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months