December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1386) <certificate-revocation-list /> should also support a URI and resource in addition to path.

by Martin Mazanek (JIRA)

[ https://issues.jboss.org/browse/ELY-1386?page=com.atlassian.jira.plugin.s... ] Martin Mazanek reassigned ELY-1386: ----------------------------------- Assignee: Martin Mazanek > <certificate-revocation-list /> should also support a URI and resource in addition to path. > ------------------------------------------------------------------------------------------- > > Key: ELY-1386 > URL: https://issues.jboss.org/browse/ELY-1386 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Martin Mazanek > Fix For: 1.2.0.Beta11 > > > KeyStores can be loaded from a path, a URI, or as a resource - the certificate revocation list should be the same. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1464) Programatic authentication should be caching the SecurityIdentity not the name of the identity

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1464: ------------------------------------- Summary: Programatic authentication should be caching the SecurityIdentity not the name of the identity Key: ELY-1464 URL: https://issues.jboss.org/browse/ELY-1464 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta11 By only caching the name of the identity the server authentication context -> security domain -> security realm chain is called for each subsequent request when we should have been able to re-use an existing identity. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1463) Programatic authentication is not creating a HTTP session if one does not already exist.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1463: ------------------------------------- Summary: Programatic authentication is not creating a HTTP session if one does not already exist. Key: ELY-1463 URL: https://issues.jboss.org/browse/ELY-1463 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta11 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1462) Move programatic authentication from Elytron Web to Elytron

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1462: ------------------------------------- Summary: Move programatic authentication from Elytron Web to Elytron Key: ELY-1462 URL: https://issues.jboss.org/browse/ELY-1462 Project: WildFly Elytron Issue Type: Task Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta11 The core implementation should be following the same pattern as is followed for mechanisms such as FORM authentication, this should not need to live within the HTTP server integration project. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3457) Minimise Classes in the Elytron Subsystem

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3457: ---------------------------------------- Summary: Minimise Classes in the Elytron Subsystem Key: WFCORE-3457 URL: https://issues.jboss.org/browse/WFCORE-3457 Project: WildFly Core Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 4.0.0.Alpha5 We currently compile to 308 classes, as this subsystem is almost exclusively about management representation (Model and XML) rather than implementation all 308 of these classes will need to be loaded when the subsystem is installed. By switching to builders where we can instead of anonymous inner classes and possibly using more common classes I believe a reasonable early target could be drop this to 200 to 250 classes so possibly up to a 33% saving. Even without restructuring our resource registrations a lot of our classes exist just to logically group related resources rather than any other purpose. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Cheng Fang edited comment on WFLY-9610 at 12/13/17 7:19 AM: ------------------------------------------------------------ you can try set the batch subsystem thread pool max size to be a small number (but not too small), e.g., 3, start a long-running batch job execution, check if it's started, and start the job a second time, check if it's started, and so on. When not enough batch threads are available, the job execution will be put on hold. You can check batch status to see its progress: STARTED means it's already started; STARTING means it has been received but has not been started yet. This can be done via WildFly CLI, or Web Console, or from your application code. You can also use a debugger to see the progress of the job execution. was (Author: cfang): you can try set the batch subsystem thread pool max size to be a small number (but not too small), e.g., 3, start a long-running batch job execution, check if it's started, and start the job a second time, check if it's started, and so on. When not enough batch threads are available, the job execution will be put on hold. You can check batch status to see its progress: STARTED means it's already started; STARTING means it has been received but has not been started yet. You can also use a debugger to see the progress of the job execution. > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Cheng Fang commented on WFLY-9610: ---------------------------------- you can try set the batch subsystem thread pool max size to be a small number (but not too small), e.g., 3, start a long-running batch job execution, check if it's started, and start the job a second time, check if it's started, and so on. When not enough batch threads are available, the job execution will be put on hold. You can check batch status to see its progress: STARTED means it's already started; STARTING means it has been received but has not been started yet. You can also use a debugger to see the progress of the job execution. > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9614) Make keystore optional in SSO configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9614?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-9614: -------------------------------------- Assignee: (was: Darran Lofthouse) > Make keystore optional in SSO configuration > ------------------------------------------- > > Key: WFLY-9614 > URL: https://issues.jboss.org/browse/WFLY-9614 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Martin Choma > > Keystore is required [1], thus signing logout message by default. > Questionable is if security brought by this is worth default command complexity as: > * Integrity of messages could be achieved on node to node communication level > * If message was not signed, attacker needs to know http session id to do a harm. Once attacker knows http session id, he can do a lot more useful attacks then logout user. > Some long communication on topic occured on Wildfly Elytron hipchat room 2017-12-7 - 2017-12-11. > [1] https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-929) AuthenticationConfiguration uniqueness enhancements

by Martin Mazanek (JIRA)

[ https://issues.jboss.org/browse/ELY-929?page=com.atlassian.jira.plugin.sy... ] Martin Mazanek reassigned ELY-929: ---------------------------------- Assignee: Martin Mazanek > AuthenticationConfiguration uniqueness enhancements > --------------------------------------------------- > > Key: ELY-929 > URL: https://issues.jboss.org/browse/ELY-929 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: Martin Mazanek > Fix For: 1.2.0.Beta12 > > > Apply some enhancements to AuthenticationConfiguration uniqueness. > * Add admonishing JavaDoc to {{useCallbackHandler}} to point out the importance of per-identity uniqueness of the callback handler > The following also may be possible and useful: > * Modify the {{AuthenticationConfiguration}} process to capture instances for {{Supplier}}-driven components at the time the configuration is used via the {{AuthenticationContextConfigurationClient}} > * Add a variation of {{useCallbackHandler}} which accepts a {{Supplier<CallbackHandler>}}, or a {{Function<T, CallbackHandler}} and a {{T}}, allowing constructor refs to be given -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2163) [DMN Editor] Context table doesn't show entry type label if table is scrolled

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2163?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2163: ------------------------------------- Coverage extended slightly https://github.com/manstis/kie-wb-common/pull/20 > [DMN Editor] Context table doesn't show entry type label if table is scrolled > ----------------------------------------------------------------------------- > > Key: DROOLS-2163 > URL: https://issues.jboss.org/browse/DROOLS-2163 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > > Context table offers 5 types of entries while each entry has label of its own type (Literal Expression, Function Relation etc.) However this label is not shown if the user scroll the table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 December 2017