April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

by Brian Loss (Jira)

[ https://issues.jboss.org/browse/WFLY-11892?page=com.atlassian.jira.plugin... ] Brian Loss commented on WFLY-11892: ----------------------------------- The legacy code I have _requires_ the use of the RunAsLoginModule since I need to call a secured EJB from the custom login module. Therefore, my legacy code is not supported even though your documentation indicates it should be. > With Elytron the legacy RunAsLoginModule no longer works > -------------------------------------------------------- > > Key: WFLY-11892 > URL: https://issues.jboss.org/browse/WFLY-11892 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Loss > Assignee: Ivo Studensky > Priority: Major > > When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack. > It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/ma...] was responsible for setting up the security context. However, that action is no longer executed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3296) Ephemeral port number (port="0") should not be affected by port offset

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFCORE-3296?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFCORE-3296: ----------------------------------- Component/s: Server > Ephemeral port number (port="0") should not be affected by port offset > ---------------------------------------------------------------------- > > Key: WFCORE-3296 > URL: https://issues.jboss.org/browse/WFCORE-3296 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 3.0.2.Final, 4.0.0.Final, 5.0.0.Final, 6.0.2.Final, 7.0.0.Final, 8.0.0.Final, 9.0.0.Beta2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Port 0 is almost universally considered a wildcard port/indeterminate port/ephemeral/port chosen by the OS and obviously applying an offset to such port (e.g. offset of -100) will fail on multiple fronts, e.g.: > {noformat} > Caused by: java.lang.IllegalArgumentException: port out of range:-100 > {noformat} > This is a regression introduced in https://issues.jboss.org/browse/WFLY-2345 based on discussion on https://developer.jboss.org/message/842406#842407 in PR https://github.com/wildfly/wildfly/pull/5307/files#diff-1a9ef995f085779b0... > The original condition was also not really correct, since we allow negative and positive port offsets, the correct condition really is {code}if (!isFixedPort && port != 0) {{code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFLY-11892?page=com.atlassian.jira.plugin... ] Ivo Studensky resolved WFLY-11892. ---------------------------------- Resolution: Rejected Combination of legacy RunAsLoginModule and Elytron is considered unsupported. >From the Darran's email: Once a deployment is making use of WildFly Elytron the login modules such as RunAsLoginModule which rely on the PicketBox security context would not be supported as that security context no longer exists. The wrapping of the legacy security domains that we do provide with Elytron SecurityRealms is just so users can continue to use code they have implemented in the past to interact with their repository of identities. > With Elytron the legacy RunAsLoginModule no longer works > -------------------------------------------------------- > > Key: WFLY-11892 > URL: https://issues.jboss.org/browse/WFLY-11892 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Loss > Assignee: Ivo Studensky > Priority: Major > > When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack. > It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/ma...] was responsible for setting up the security context. However, that action is no longer executed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4403) Upgrade Undertow to 2.0.20.Final

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFCORE-4403?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFCORE-4403: ---------------------------------- Component/s: Build System > Upgrade Undertow to 2.0.20.Final > -------------------------------- > > Key: WFCORE-4403 > URL: https://issues.jboss.org/browse/WFCORE-4403 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Flavia Rainone > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4403) Upgrade Undertow to 2.0.20.Final

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFCORE-4403?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFCORE-4403: ---------------------------------- Fix Version/s: (was: 8.0.0.CR1) (was: 8.0.0.Final) > Upgrade Undertow to 2.0.20.Final > -------------------------------- > > Key: WFCORE-4403 > URL: https://issues.jboss.org/browse/WFCORE-4403 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Ilia Vassilev > Assignee: Flavia Rainone > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4403) Upgrade Undertow to 2.0.20.Final

by Ilia Vassilev (Jira)

Ilia Vassilev created WFCORE-4403: ------------------------------------- Summary: Upgrade Undertow to 2.0.20.Final Key: WFCORE-4403 URL: https://issues.jboss.org/browse/WFCORE-4403 Project: WildFly Core Issue Type: Component Upgrade Reporter: Ilia Vassilev Assignee: Flavia Rainone Fix For: 8.0.0.CR1, 8.0.0.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3784: -------------------------------------- Issue Type: Story (was: Epic) > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3784: -------------------------------------- Labels: Field UX UXTeam drools-tools (was: drools-tools) > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3784: -------------------------------------- Issue Type: Epic (was: Story) > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3784: -------------------------------------- Issue Type: Story (was: Epic) > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019