[JBoss JIRA] (DROOLS-3761) [DMN Designer] Data Types - Constraints - Enumeration constraint entry on edit mode - Fix buttons behavior
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3761?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3761:
-------------------------------------
[~tirelli] just friendly reminder, see my comment above, seems we should close this because mine and your requirement is in conflict with patterfly spec. Please correct me if I am wrong.
> [DMN Designer] Data Types - Constraints - Enumeration constraint entry on edit mode - Fix buttons behavior
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3761
> URL: https://issues.jboss.org/browse/DROOLS-3761
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.19.0.Final
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Minor
> Labels: drools-tools
> Attachments: constraint_unsaved.png, focus_lost.webm, lost_focus_data_types.webm
>
>
> The attached video shows the user interaction with enumeration constraint component. We can see if user fill valid values and clicks somewhere outside of the entry in edit mode, the values are lost. The only way how to save values is to click the *check* button. User should not lost filled in values if he clicks outside of input fields.
> Please compare the same behavior with data types list view component. It means [^focus_lost.webm] vs [^lost_focus_data_types.webm] .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12847) Auth constraint with role name of "*" defaults to deny
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFLY-12847?page=com.atlassian.jira.plugin... ]
Darran Lofthouse resolved WFLY-12847.
-------------------------------------
Resolution: Rejected
Actually going to reject this one "*" is not quite what I need.
> Auth constraint with role name of "*" defaults to deny
> ------------------------------------------------------
>
> Key: WFLY-12847
> URL: https://issues.jboss.org/browse/WFLY-12847
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.1.Final
> Reporter: Darran Lofthouse
> Assignee: Flavia Rainone
> Priority: Major
>
> This will probably need some further investigation but just raising the Jira for now so recorded.
> I have been working with a deployment where I wish to trigger authentication for all paths except for one specific path where I wish to allow unauthenticated access so went for the following constraints.
> {noformat}
> <security-constraint>
> <display-name>All Paths</display-name>
> <web-resource-collection>
> <web-resource-name>All</web-resource-name>
> <url-pattern>/*</url-pattern>
> </web-resource-collection>
> <auth-constraint>
> <role-name>**</role-name>
> </auth-constraint>
> </security-constraint>
> <security-constraint>
> <display-name>Unrestricted Path</display-name>
> <web-resource-collection>
> <web-resource-name>Unrestricted</web-resource-name>
> <url-pattern>/some/special/path</url-pattern>
> </web-resource-collection>
> <auth-constraint>
> <role-name>*</role-name>
> </auth-constraint>
> </security-constraint>
> {noformat}
> This had the desired effect in relation to authentication, it became mandatory for all paths except the special path. The all paths constrains also did not trigger any authorisation failures i.e. 403 but the special path does.
> Debugging this we have a default behaviour of deny all if no roles are specified. This definitely makes sense for annotated servlets where a developer could inadvertently omit an annotation so we deliberately fail safe. But in this example my configuration specifically states I want to allow anyone through so if this constraint is matched I think we should consider if the specific constraint should default to PERMIT.
> I did look at jboss-web.xml overrides to see if I could override the mode, although I can override on a servlet basis I can't override it for the general path based constraint. If the current behaviour is deemed correct maybe a path based override in the jboss-web.xml could be considered.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12847) Auth constraint with role name of "*" defaults to deny
by Darran Lofthouse (Jira)
Darran Lofthouse created WFLY-12847:
---------------------------------------
Summary: Auth constraint with role name of "*" defaults to deny
Key: WFLY-12847
URL: https://issues.jboss.org/browse/WFLY-12847
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 18.0.1.Final
Reporter: Darran Lofthouse
Assignee: Flavia Rainone
This will probably need some further investigation but just raising the Jira for now so recorded.
I have been working with a deployment where I wish to trigger authentication for all paths except for one specific path where I wish to allow unauthenticated access so went for the following constraints.
{noformat}
<security-constraint>
<display-name>All Paths</display-name>
<web-resource-collection>
<web-resource-name>All</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>**</role-name>
</auth-constraint>
</security-constraint>
<security-constraint>
<display-name>Unrestricted Path</display-name>
<web-resource-collection>
<web-resource-name>Unrestricted</web-resource-name>
<url-pattern>/some/special/path</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>*</role-name>
</auth-constraint>
</security-constraint>
{noformat}
This had the desired effect in relation to authentication, it became mandatory for all paths except the special path. The all paths constrains also did not trigger any authorisation failures i.e. 403 but the special path does.
Debugging this we have a default behaviour of deny all if no roles are specified. This definitely makes sense for annotated servlets where a developer could inadvertently omit an annotation so we deliberately fail safe. But in this example my configuration specifically states I want to allow anyone through so if this constraint is matched I think we should consider if the specific constraint should default to PERMIT.
I did look at jboss-web.xml overrides to see if I could override the mode, although I can override on a servlet basis I can't override it for the general path based constraint. If the current behaviour is deemed correct maybe a path based override in the jboss-web.xml could be considered.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12846) JAX-RS Servlet Overrides jboss-web.xml configuration
by Darran Lofthouse (Jira)
Darran Lofthouse created WFLY-12846:
---------------------------------------
Summary: JAX-RS Servlet Overrides jboss-web.xml configuration
Key: WFLY-12846
URL: https://issues.jboss.org/browse/WFLY-12846
Project: WildFly
Issue Type: Bug
Components: REST
Affects Versions: 18.0.1.Final
Reporter: Darran Lofthouse
Assignee: Alessio Soldano
I thought I was going to require this for the JWT TCK but looks like I don't but am raising the issue anyway in case it wants to be considered.
I have found the way the servlet is registered for JAX-RS any overrides in jboss-web.xml are ignored, it seems to be a relatively small change to merge the two together.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months