August 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.9.2.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, 1.10.0.CR5 > > > 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, 11 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.10.0.CR5 > 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, 1.10.0.CR5 > > > 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 authentication is not being used for EJB invocations -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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)

[ https://issues.jboss.org/browse/ELY-1855?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1855: ---------------------------- Fix Version/s: 1.10.0.CR5 (was: 1.9.2.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, 1.10.0.CR5 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1860) Release WildFly Elytron 1.6.4.Final

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1860?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1860: ---------------------------- Fix Version/s: 1.9.2.CR1 > Release WildFly Elytron 1.6.4.Final > ----------------------------------- > > Key: ELY-1860 > URL: https://issues.jboss.org/browse/ELY-1860 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.6.4.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1860) Release WildFly Elytron 1.6.4.Final

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1860?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1860: ---------------------------- Fix Version/s: (was: 1.9.2.CR1) > Release WildFly Elytron 1.6.4.Final > ----------------------------------- > > Key: ELY-1860 > URL: https://issues.jboss.org/browse/ELY-1860 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.6.4.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1860) Release WildFly Elytron 1.6.4.Final

by Farah Juma (Jira)

Farah Juma created ELY-1860: ------------------------------- Summary: Release WildFly Elytron 1.6.4.Final Key: ELY-1860 URL: https://issues.jboss.org/browse/ELY-1860 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.6.4.CR1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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: ---------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1319 (was: https://github.com/wildfly-security/wildfly-elytron/pull/1310) > 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 authentication is not being used for EJB invocations -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4270) Visual design: Highlighting treatment for GDST/DMN 7.5 Find results

by Brian Dellascio (Jira)

[ https://issues.jboss.org/browse/DROOLS-4270?page=com.atlassian.jira.plugi... ] Brian Dellascio closed DROOLS-4270. ----------------------------------- Resolution: Done > Visual design: Highlighting treatment for GDST/DMN 7.5 Find results > ------------------------------------------------------------------- > > Key: DROOLS-4270 > URL: https://issues.jboss.org/browse/DROOLS-4270 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Elizabeth Clayton > Assignee: Brian Dellascio > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png, guided-decision-table-find.gif > > > As a user of the proposed 7.5 GDT/DMN "Find" feature, when I submit text using the find tool, I need to see the results visually highlighting in the respective canvas area. > Find is a local search that could be performed in these areas of the application: > * Guided Decision Table editor (tables) - text strings within "Data cells" > * DMN graph- text strings within canvas nodes. > * DMN boxed expressions (logic) - text strings within "Data cells" > Requirements > * Colors, etc for partial and whole text strings will need to be highlighted is required. > * General recommendations regarding the usability and appearance for highlighting entire table cells and nodes. > * Visual styles for the above if recommended. > Considerations > * Will not be able to leverage browser controls for Find. > * Visual design should take into consideration the visual treatments that will be applied within these jiras: https://issues.jboss.org/browse/DROOLS-3953 and https://issues.jboss.org/browse/DROOLS-4258. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4413) fireUntilHalt continues to block after session disposed

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4413?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4413. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/6cd920e7f53b7ea3129aae72b641a97... > fireUntilHalt continues to block after session disposed > ------------------------------------------------------- > > Key: DROOLS-4413 > URL: https://issues.jboss.org/browse/DROOLS-4413 > Project: Drools > Issue Type: Bug > Affects Versions: 7.25.0.Final > Environment: Local build of 7.24.0.Final with Oracle JDK 8 > Reporter: Jesse White > Assignee: Mario Fusco > Priority: Major > Attachments: WhatsWrongWithMeTest.java, halt_log.txt, intellij-test-failure.png > > > See attached test case that reproduces the problem. > I'm expecting that a thread calling fireUntilHalt will exit after the session is halted and disposed, but it continues to block. If the code block that performs the marshalling is ignored, then the thread exists as expected. > Stack is: > {code:java} > "Thread-1" #14 daemon prio=5 os_prio=0 tid=0x00007f5a7c683000 nid=0x1c028 in Object.wait() [0x00007f5acc170000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000ecfc67b0> (a org.drools.core.phreak.SynchronizedPropagationList) > at java.lang.Object.wait(Object.java:502) > at org.drools.core.phreak.SynchronizedPropagationList.waitOnRest(SynchronizedPropagationList.java:128) > - locked <0x00000000ecfc67b0> (a org.drools.core.phreak.SynchronizedPropagationList) > at org.drools.core.common.DefaultAgenda$RestHandler$FireUntilHaltRestHandler.handleRest(DefaultAgenda.java:1133) > - locked <0x00000000ecfc67b0> (a org.drools.core.phreak.SynchronizedPropagationList) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1074) > at org.drools.core.common.DefaultAgenda.internalFireUntilHalt(DefaultAgenda.java:991) > at org.drools.core.common.DefaultAgenda.fireUntilHalt(DefaultAgenda.java:983) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1369) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1348) > at org.drools.compiler.integrationtests.WhatsWrongWithMeTest.lambda$canReturnWhenHalted$0(WhatsWrongWithMeTest.java:78) > at org.drools.compiler.integrationtests.WhatsWrongWithMeTest$$Lambda$60/994541328.run(Unknown Source) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4413) fireUntilHalt continues to block after session disposed

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4413?page=com.atlassian.jira.plugi... ] Mario Fusco reopened DROOLS-4413: --------------------------------- > fireUntilHalt continues to block after session disposed > ------------------------------------------------------- > > Key: DROOLS-4413 > URL: https://issues.jboss.org/browse/DROOLS-4413 > Project: Drools > Issue Type: Bug > Affects Versions: 7.25.0.Final > Environment: Local build of 7.24.0.Final with Oracle JDK 8 > Reporter: Jesse White > Assignee: Mario Fusco > Priority: Major > Attachments: WhatsWrongWithMeTest.java, halt_log.txt, intellij-test-failure.png > > > See attached test case that reproduces the problem. > I'm expecting that a thread calling fireUntilHalt will exit after the session is halted and disposed, but it continues to block. If the code block that performs the marshalling is ignored, then the thread exists as expected. > Stack is: > {code:java} > "Thread-1" #14 daemon prio=5 os_prio=0 tid=0x00007f5a7c683000 nid=0x1c028 in Object.wait() [0x00007f5acc170000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000ecfc67b0> (a org.drools.core.phreak.SynchronizedPropagationList) > at java.lang.Object.wait(Object.java:502) > at org.drools.core.phreak.SynchronizedPropagationList.waitOnRest(SynchronizedPropagationList.java:128) > - locked <0x00000000ecfc67b0> (a org.drools.core.phreak.SynchronizedPropagationList) > at org.drools.core.common.DefaultAgenda$RestHandler$FireUntilHaltRestHandler.handleRest(DefaultAgenda.java:1133) > - locked <0x00000000ecfc67b0> (a org.drools.core.phreak.SynchronizedPropagationList) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1074) > at org.drools.core.common.DefaultAgenda.internalFireUntilHalt(DefaultAgenda.java:991) > at org.drools.core.common.DefaultAgenda.fireUntilHalt(DefaultAgenda.java:983) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1369) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1348) > at org.drools.compiler.integrationtests.WhatsWrongWithMeTest.lambda$canReturnWhenHalted$0(WhatsWrongWithMeTest.java:78) > at org.drools.compiler.integrationtests.WhatsWrongWithMeTest$$Lambda$60/994541328.run(Unknown Source) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019