[JBoss JIRA] (WFCORE-3963) Fix of WFCORE-3826 breaks plain authentication for ejbs using legacy configuration
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3963?page=com.atlassian.jira.plugi... ]
Jiri Ondrusek updated WFCORE-3963:
----------------------------------
Summary: Fix of WFCORE-3826 breaks plain authentication for ejbs using legacy configuration (was: [GSS] (7.1.z) anonymous authentication for ejbs using legacy configuration - test)
> Fix of WFCORE-3826 breaks plain authentication for ejbs using legacy configuration
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-3963
> URL: https://issues.jboss.org/browse/WFCORE-3963
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 6.0.0.Alpha3
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Labels: Regression, test
>
> Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration:
> <subsystem xmlns="urn:jboss:domain:remoting:4.0">
> <endpoint/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
> <properties>
> <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> </properties>
> </http-connector>
> </subsystem>
> Unfortunately, this same configuration does not work on 7.1.1. It looks
> like the server still wants to use DIGEST-MD5 based authentication.
> Has the legacy based configuration (non-elytron) for anonymous ejb
> access changed on eap 7.1.1?
> I am attaching the standalone.xml, server.log and client log.
> Customer does not want to use elytron at the moment.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3963) Fix of WFCORE-3826 breaks plain authentication for ejbs using legacy configuration
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3963?page=com.atlassian.jira.plugi... ]
Jiri Ondrusek updated WFCORE-3963:
----------------------------------
Git Pull Request: (was: https://github.com/jbossas/jboss-eap7/pull/2653)
> Fix of WFCORE-3826 breaks plain authentication for ejbs using legacy configuration
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-3963
> URL: https://issues.jboss.org/browse/WFCORE-3963
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 6.0.0.Alpha3
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Labels: Regression, test
>
> Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration:
> <subsystem xmlns="urn:jboss:domain:remoting:4.0">
> <endpoint/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
> <properties>
> <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> </properties>
> </http-connector>
> </subsystem>
> Unfortunately, this same configuration does not work on 7.1.1. It looks
> like the server still wants to use DIGEST-MD5 based authentication.
> Has the legacy based configuration (non-elytron) for anonymous ejb
> access changed on eap 7.1.1?
> I am attaching the standalone.xml, server.log and client log.
> Customer does not want to use elytron at the moment.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3963) [GSS] (7.1.z) anonymous authentication for ejbs using legacy configuration - test
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3963?page=com.atlassian.jira.plugi... ]
Jiri Ondrusek moved JBEAP-15039 to WFCORE-3963:
-----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3963 (was: JBEAP-15039)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
Affects Version/s: 6.0.0.Alpha3
(was: 7.1.1.GA)
Fix Version/s: (was: 7.1.5.GA)
> [GSS] (7.1.z) anonymous authentication for ejbs using legacy configuration - test
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-3963
> URL: https://issues.jboss.org/browse/WFCORE-3963
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 6.0.0.Alpha3
> Reporter: Jiri Ondrusek
> Assignee: Bartosz Spyrko-Śmietanko
> Labels: Regression, test
>
> Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration:
> <subsystem xmlns="urn:jboss:domain:remoting:4.0">
> <endpoint/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
> <properties>
> <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> </properties>
> </http-connector>
> </subsystem>
> Unfortunately, this same configuration does not work on 7.1.1. It looks
> like the server still wants to use DIGEST-MD5 based authentication.
> Has the legacy based configuration (non-elytron) for anonymous ejb
> access changed on eap 7.1.1?
> I am attaching the standalone.xml, server.log and client log.
> Customer does not want to use elytron at the moment.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3963) [GSS] (7.1.z) anonymous authentication for ejbs using legacy configuration - test
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3963?page=com.atlassian.jira.plugi... ]
Jiri Ondrusek reassigned WFCORE-3963:
-------------------------------------
Assignee: Jiri Ondrusek (was: Bartosz Spyrko-Śmietanko)
> [GSS] (7.1.z) anonymous authentication for ejbs using legacy configuration - test
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-3963
> URL: https://issues.jboss.org/browse/WFCORE-3963
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 6.0.0.Alpha3
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Labels: Regression, test
>
> Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration:
> <subsystem xmlns="urn:jboss:domain:remoting:4.0">
> <endpoint/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
> <properties>
> <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> </properties>
> </http-connector>
> </subsystem>
> Unfortunately, this same configuration does not work on 7.1.1. It looks
> like the server still wants to use DIGEST-MD5 based authentication.
> Has the legacy based configuration (non-elytron) for anonymous ejb
> access changed on eap 7.1.1?
> I am attaching the standalone.xml, server.log and client log.
> Customer does not want to use elytron at the moment.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2728:
----------------------------------------
[~karreiro] Great comments.
[~uxdlc] Whatever design is envisaged needs to support an unlimited level of nesting (e.g. {{Planet.Country.Region.City.Person.Address.Street}} etc).
I'm not convinced this level of nesting can be represented by your initial mock-ups.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ELY-1607) Revise cipher suites exposed by Elytron
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/ELY-1607?page=com.atlassian.jira.plugin.s... ]
Justin Cook commented on ELY-1607:
----------------------------------
The Java names for the ones that I could not find an OpenSSL name for are:
TLS_DH_DSS_WITH_ARIA_128_CBC_SHA256, TLS_DH_DSS_WITH_ARIA_256_CBC_SHA384, TLS_DH_RSA_WITH_ARIA_128_CBC_SHA256, TLS_DH_RSA_WITH_ARIA_256_CBC_SHA384, TLS_ECDH_ECDSA_WITH_ARIA_128_CBC_SHA256 ,TLS_ECDH_ECDSA_WITH_ARIA_256_CBC_SHA384, TLS_ECDH_RSA_WITH_ARIA_128_CBC_SHA256, TLS_ECDH_RSA_WITH_ARIA_256_CBC_SHA384, TLS_DH_RSA_WITH_ARIA_128_GCM_SHA256, TLS_DH_RSA_WITH_ARIA_256_GCM_SHA384, TLS_DH_DSS_WITH_ARIA_128_GCM_SHA256, TLS_DH_DSS_WITH_ARIA_256_GCM_SHA384, TLS_DH_anon_WITH_ARIA_128_GCM_SHA256, TLS_DH_anon_WITH_ARIA_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_ARIA_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_ARIA_256_GCM_SHA384, TLS_ECDH_RSA_WITH_ARIA_128_GCM_SHA256, TLS_ECDH_RSA_WITH_ARIA_256_GCM_SHA384, TLS_PSK_WITH_ARIA_128_CBC_SHA256, TLS_PSK_WITH_ARIA_256_CBC_SHA384, TLS_DHE_PSK_WITH_ARIA_128_CBC_SHA256, TLS_DHE_PSK_WITH_ARIA_256_CBC_SHA384, TLS_RSA_PSK_WITH_ARIA_128_CBC_SHA256, TLS_RSA_PSK_WITH_ARIA_256_CBC_SHA384, TLS_ECDHE_PSK_WITH_ARIA_128_CBC_SHA256, TLS_ECDHE_PSK_WITH_ARIA_256_CBC_SHA384
To summarize: all the PSK with CBC ones and most of the Diffie Hellman Non-Ephemeral ones
> Revise cipher suites exposed by Elytron
> ---------------------------------------
>
> Key: ELY-1607
> URL: https://issues.jboss.org/browse/ELY-1607
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.4.0.Final
> Reporter: Martin Choma
> Assignee: Justin Cook
> Priority: Blocker
> Fix For: 1.4.1.CR1
>
>
> I know there have been discussed earlier we should revise/update database and defaults regularly.
> Checking few ciphersuites from java cipher suite list [1]. I have noticed:
> * Elytron is missing CHACHA20 variants introduced in rfc 7905
> * missing ciphersuites from RFC 6209
> * ...
> Please revise content of MechanismDatabase.properties
> [1] https://docs.oracle.com/javase/10/docs/specs/security/standard-names.html...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-2728 at 7/12/18 9:15 AM:
---------------------------------------------------------------------
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
- Person
-- name (String)
-- age (Number)
-- email (String)
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
- Person
-- name (String)
-- age (Number)
-- email (String)
-- address
--- street (String)
--- house_number (Number)
--- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
was (Author: karreiro):
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
- Person
-- name (String)
-- age (Number)
-- email (String)
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-2728 at 7/12/18 9:15 AM:
---------------------------------------------------------------------
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
- Person
-- name (String)
-- age (Number)
-- email (String)
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
was (Author: karreiro):
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
* Person
* name (String)
* age (Number)
* email (String)
}}
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-2728 at 7/12/18 9:14 AM:
---------------------------------------------------------------------
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
* Person
* name (String)
* age (Number)
* email (String)
}}
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
was (Author: karreiro):
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
{{
- Person
- name (String)
- age (Number)
- email (String)
}}
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years