July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1855) Update AuthenticationConfiguration#useAuthorizationPrincipal to avoid needing an extra call to AuthenticationConfiguration#useForwardedAuthorizationIdentity

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1855?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1855: ---------------------------- Fix Version/s: 1.6.4.CR1 > Update AuthenticationConfiguration#useAuthorizationPrincipal to avoid needing an extra call to AuthenticationConfiguration#useForwardedAuthorizationIdentity > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ELY-1855 > URL: https://issues.jboss.org/browse/ELY-1855 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.6.4.CR1 > > > Update {{AuthenticationConfiguration#useAuthorizationPrincipal}} to set {{SET_ACCESS_CTXT}} and {{SET_FWD_AUTHZ_NAME_DOMAIN}} to {{null}} to avoid needing an extra call to {{AuthenticationConfiguration#useForwardedAuthorizationIdentity(null)}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-1855) Update AuthenticationConfiguration#useAuthorizationPrincipal to avoid needing an extra call to AuthenticationConfiguration#useForwardedAuthorizationIdentity

by Farah Juma (Jira)

Farah Juma created ELY-1855: ------------------------------- Summary: Update AuthenticationConfiguration#useAuthorizationPrincipal to avoid needing an extra call to AuthenticationConfiguration#useForwardedAuthorizationIdentity Key: ELY-1855 URL: https://issues.jboss.org/browse/ELY-1855 Project: WildFly Elytron Issue Type: Task Components: Authentication Client Reporter: Farah Juma Assignee: Farah Juma Update {{AuthenticationConfiguration#useAuthorizationPrincipal}} to set {{SET_ACCESS_CTXT}} and {{SET_FWD_AUTHZ_NAME_DOMAIN}} to {{null}} to avoid needing an extra call to {{AuthenticationConfiguration#useForwardedAuthorizationIdentity(null)}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-1854) Add the ability to specify whether or not the AccessControlContext should be captured by using a system property called "wildfly.elytron.capture.access.control.context"

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1854?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1854: ---------------------------- Fix Version/s: 1.6.4.CR1 > Add the ability to specify whether or not the AccessControlContext should be captured by using a system property called "wildfly.elytron.capture.access.control.context" > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ELY-1854 > URL: https://issues.jboss.org/browse/ELY-1854 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.6.4.CR1 > > > Add the ability to specify whether or not the {{AccessControlContext}} should be captured by using a system property called {{wildfly.elytron.capture.access.control.context}}. It defaults to "true" so the {{AccessControlContext}} will be captured by default. It can be set to "false" if Kerberos is not being used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-1854) Add the ability to specify whether or not the AccessControlContext should be captured by using a system property called "wildfly.elytron.capture.access.control.context"

by Farah Juma (Jira)

Farah Juma created ELY-1854: ------------------------------- Summary: Add the ability to specify whether or not the AccessControlContext should be captured by using a system property called "wildfly.elytron.capture.access.control.context" Key: ELY-1854 URL: https://issues.jboss.org/browse/ELY-1854 Project: WildFly Elytron Issue Type: Task Components: Authentication Client Reporter: Farah Juma Assignee: Farah Juma Add the ability to specify whether or not the {{AccessControlContext}} should be captured by using a system property called {{wildfly.elytron.capture.access.control.context}}. It defaults to "true" so the {{AccessControlContext}} will be captured by default. It can be set to "false" if Kerberos is not being used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4364) [DMN Designer] Download buttons UX (Development task)

by Margot Menestrot (Jira)

[ https://issues.jboss.org/browse/DROOLS-4364?page=com.atlassian.jira.plugi... ] Margot Menestrot reassigned DROOLS-4364: ---------------------------------------- Description: h3. Need to update the DMN toolbar download buttons based on the context described in initial issue. Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC... Suggestions are as follows: 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out. 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation. 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there. --------------- h3. Context: Today users can: 1) Download the diagram picture by using this component: !component-1.png|thumbnail! 2) Download the DMN file by using this component: !component-2.png|thumbnail! 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab): !component-3.png|thumbnail! 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab): !component-3.png|thumbnail! ---- h3. Problem: The "Download" concept is getting confusing for users. As a user, I want to be able to: - Download the documentation as a .PDF file - Download the documentation as a .DOC file - Print the documentation ---- h3. Notice: This component can be removed (if UX considers that it's necessary): !component-1.png|thumbnail! was: h3. Context: Today users can: 1) Download the diagram picture by using this component: !component-1.png|thumbnail! 2) Download the DMN file by using this component: !component-2.png|thumbnail! 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab): !component-3.png|thumbnail! 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab): !component-3.png|thumbnail! ---- h3. Problem: The "Download" concept is getting confusing for users. As a user, I want to be able to: - Download the documentation as a .PDF file - Download the documentation as a .DOC file - Print the documentation ---- h3. Notice: This component can be removed (if UX considers that it's necessary): !component-1.png|thumbnail! Summary: [DMN Designer] Download buttons UX (Development task) (was: [DMN Designer] Documentation - Download buttons UX) Assignee: Guilherme Gomes (was: Margot Menestrot) > [DMN Designer] Download buttons UX (Development task) > ----------------------------------------------------- > > Key: DROOLS-4364 > URL: https://issues.jboss.org/browse/DROOLS-4364 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Margot Menestrot > Assignee: Guilherme Gomes > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: component-1.png, component-2.png, component-3.png > > > h3. Need to update the DMN toolbar download buttons based on the context described in initial issue. > Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC... > Suggestions are as follows: > 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out. > 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation. > 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there. > --------------- > h3. Context: > Today users can: > 1) Download the diagram picture by using this component: > !component-1.png|thumbnail! > 2) Download the DMN file by using this component: > !component-2.png|thumbnail! > 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab): > !component-3.png|thumbnail! > 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab): > !component-3.png|thumbnail! > ---- > h3. Problem: > The "Download" concept is getting confusing for users. > As a user, I want to be able to: > - Download the documentation as a .PDF file > - Download the documentation as a .DOC file > - Print the documentation > ---- > h3. Notice: > This component can be removed (if UX considers that it's necessary): > !component-1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4360) Salience assignment behaviour is different when SequentialMaxPriority is set

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4360?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4360. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/0feac379d8389acd4c11bdad0434e23... > Salience assignment behaviour is different when SequentialMaxPriority is set > ---------------------------------------------------------------------------- > > Key: DROOLS-4360 > URL: https://issues.jboss.org/browse/DROOLS-4360 > Project: Drools > Issue Type: Bug > Components: decision tables > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Labels: support > > In Spreadsheet decision tables, RuleSet property SequentialMaxPriority and SequentialMinPriority are for controlling the salience number range of Rules generated from Decision Tables. > https://access.redhat.com/documentation/en-us/red_hat_decision_manager/7.... > By setting Sequential=true without SequentialMaxPriority and SequentialMinPriority, the salience starts with 65535 and it's decremented one by one through all rules across multiple RuleTables. > On the other hand, by setting Sequential=true WITH SequentialMaxPriority, > every RuleTables starts with value specified by SequentialMaxPriority as salience. > i.e. first rule of each RuleTebles has same salience if there are multiple RuleTables. > In other words, when SequentialMaxPriority is set, start value of salience is reset per RuleTables, but this is unexpected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12318) SecurityManager push/pull is expensive

by Stefano Maestri (Jira)

[ https://issues.jboss.org/browse/WFLY-12318?page=com.atlassian.jira.plugin... ] Stefano Maestri updated WFLY-12318: ----------------------------------- Affects Version/s: 17.0.1.Final > SecurityManager push/pull is expensive > -------------------------------------- > > Key: WFLY-12318 > URL: https://issues.jboss.org/browse/WFLY-12318 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Affects Versions: 17.0.1.Final > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Major > > Pushing SecurityDefinition in securityManager in eery SubjectFactory is creating a lot of object with big impact on performance. > Double checking WFLY-6372 it seems not needed for that issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12318) SecurityManager push/pull is expensive

by Stefano Maestri (Jira)

Stefano Maestri created WFLY-12318: -------------------------------------- Summary: SecurityManager push/pull is expensive Key: WFLY-12318 URL: https://issues.jboss.org/browse/WFLY-12318 Project: WildFly Issue Type: Enhancement Reporter: Stefano Maestri Assignee: Brian Stansberry Pushing SecurityDefinition in securityManager in eery SubjectFactory is creating a lot of object with big impact on performance. Double checking WFLY-6372 it seems not needed for that issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12318) SecurityManager push/pull is expensive

by Stefano Maestri (Jira)

[ https://issues.jboss.org/browse/WFLY-12318?page=com.atlassian.jira.plugin... ] Stefano Maestri reassigned WFLY-12318: -------------------------------------- Assignee: Stefano Maestri (was: Brian Stansberry) > SecurityManager push/pull is expensive > -------------------------------------- > > Key: WFLY-12318 > URL: https://issues.jboss.org/browse/WFLY-12318 > Project: WildFly > Issue Type: Enhancement > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Major > > Pushing SecurityDefinition in securityManager in eery SubjectFactory is creating a lot of object with big impact on performance. > Double checking WFLY-6372 it seems not needed for that issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12318) SecurityManager push/pull is expensive

by Stefano Maestri (Jira)

[ https://issues.jboss.org/browse/WFLY-12318?page=com.atlassian.jira.plugin... ] Stefano Maestri updated WFLY-12318: ----------------------------------- Component/s: JCA > SecurityManager push/pull is expensive > -------------------------------------- > > Key: WFLY-12318 > URL: https://issues.jboss.org/browse/WFLY-12318 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Major > > Pushing SecurityDefinition in securityManager in eery SubjectFactory is creating a lot of object with big impact on performance. > Double checking WFLY-6372 it seems not needed for that issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

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 July 2019