January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3382) Further Enhance Elytron Permission Configuration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3382?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3382: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Further Enhance Elytron Permission Configuration > ------------------------------------------------ > > Key: WFCORE-3382 > URL: https://issues.jboss.org/browse/WFCORE-3382 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Fix For: 4.0.0.Alpha8 > > > This has currently been simplified to a single resource for the out of the box configuration, however this brings issues as now permissions are duplicated so modifications need to be replicated instead of to a single location. > Finding a way for the default required permissions to be defined in one location could help eliminate the duplication. > We could also consider going one step further and subsystems register the default permissions that should be granted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3360) Eliminate org.wildfly.extension.elytron.ProviderUtil

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3360?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3360: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Eliminate org.wildfly.extension.elytron.ProviderUtil > ---------------------------------------------------- > > Key: WFCORE-3360 > URL: https://issues.jboss.org/browse/WFCORE-3360 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 4.0.0.Alpha8 > > > WildFly Elytron contains a public utility class org.wildfly.security.util.ProviderUtil for the same purpose, we should use the code within WildFly Elytron and not custom code within the subsystem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3255) Complex type AttributeDefinition variants don't handle ParameterCorrector properly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3255?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3255: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Complex type AttributeDefinition variants don't handle ParameterCorrector properly > ---------------------------------------------------------------------------------- > > Key: WFCORE-3255 > URL: https://issues.jboss.org/browse/WFCORE-3255 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.1.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha8 > > > If a field in a complex attribute (i.e. one that uses Object...AttributeDefinition) has a ParameterCorrector configured, that corrector never gets called. That's because only a corrector on the top level attribute gets called. > These classes should automatically use an internal corrector that first calls any corrector configured for fields, and then, if one is present, calls any top level corrector. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3181) Review CustomCredentialSecurityFactoryTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3181?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3181: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Review CustomCredentialSecurityFactoryTestCase > ---------------------------------------------- > > Key: WFCORE-3181 > URL: https://issues.jboss.org/browse/WFCORE-3181 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Reporter: Darran Lofthouse > Fix For: 4.0.0.Alpha8 > > > The test case CustomCredentialSecurityFactoryTestCase appears to be testing that the 'code does what it does' rather than testing the 'code is doing what it should'. > The test is testing a custom credential security factory can be called but the test is using HTTP Basic authentication and relying on SPNEGO authentication being triggered as this is the only mechanism that currently uses this factory. > Should a minor change be required to the SPNEGO authentication mechanism which affects when this credential factory is called this test case could subsequently fail. > If possible it would be better to convert this test to be a SPNEGO test and then test the behaviour of the credential security factory affects the mechanism as expected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3519) Add JASPI Module

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3519?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3519: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Add JASPI Module > ---------------- > > Key: WFCORE-3519 > URL: https://issues.jboss.org/browse/WFCORE-3519 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 4.0.0.Alpha8 > > > (Copy from WildFly) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3457) Reduce class loading of Elytron subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3457?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3457: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Reduce class loading of 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.Alpha8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3424) Replace MSC listeners with stability monitors

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3424?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3424: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Replace MSC listeners with stability monitors > --------------------------------------------- > > Key: WFCORE-3424 > URL: https://issues.jboss.org/browse/WFCORE-3424 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Affects Versions: 4.0.0.Alpha2 > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 4.0.0.Alpha8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3542) Elytron JDBC realm password mapping is not consistent with underlying implementation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3542?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3542: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Elytron JDBC realm password mapping is not consistent with underlying implementation > ------------------------------------------------------------------------------------ > > Key: WFCORE-3542 > URL: https://issues.jboss.org/browse/WFCORE-3542 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 4.0.0.Alpha8 > > > There is no way to configure the JDBC realm to use modular crypt in WildFly, even though the underlying realm does support it. > The problem is that the {{salt-index}} and {{itereration-count-index}} attributes should be optional, and if they not given, a value of {{-1}} should be passed to the mapper. By omitting both of these values, the database column values will then be recognized as modular-crypt strings. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3527) Remove OSGi obsolete code

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3527?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3527: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Remove OSGi obsolete code > ------------------------- > > Key: WFCORE-3527 > URL: https://issues.jboss.org/browse/WFCORE-3527 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Affects Versions: 4.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 4.0.0.Alpha8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3558) Upgrade JBoss Threads to 2.3.0.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3558?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3558: ------------------------------------- Fix Version/s: 4.0.0.Alpha8 (was: 4.0.0.Alpha7) > Upgrade JBoss Threads to 2.3.0.Final > ------------------------------------ > > Key: WFCORE-3558 > URL: https://issues.jboss.org/browse/WFCORE-3558 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Richard Opalka > Assignee: David Lloyd > Fix For: 4.0.0.Alpha8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018