September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1765) Review authentication client dependencies on credential sources

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1765?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1765: ---------------------------- Fix Version/s: 1.10.2.CR1 (was: 1.10.1.Final) > Review authentication client dependencies on credential sources > --------------------------------------------------------------- > > Key: ELY-1765 > URL: https://issues.jboss.org/browse/ELY-1765 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.10.2.CR1 > > > Could these credential sources be discoverable from java.security.Provider with a more generic configuration API? This could help break any dependency from authentication client to the implementation. > _In the opposite direction I think it is Ok for the impl to depend on the client._ -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1749) Code review of WildFlyElytronProvider

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1749?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1749: ---------------------------- Fix Version/s: 1.10.2.CR1 (was: 1.10.1.Final) > Code review of WildFlyElytronProvider > ------------------------------------- > > Key: ELY-1749 > URL: https://issues.jboss.org/browse/ELY-1749 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.10.2.CR1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1867) Update the syslog audit endpoint to use the current reconnect attempts in the infinite case

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1867?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1867: ---------------------------- Fix Version/s: 1.10.1.Final > Update the syslog audit endpoint to use the current reconnect attempts in the infinite case > ------------------------------------------------------------------------------------------- > > Key: ELY-1867 > URL: https://issues.jboss.org/browse/ELY-1867 > Project: WildFly Elytron > Issue Type: Task > Components: Audit > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > Fix For: 1.10.1.Final > > > Currently, the syslog audit endpoint does not keep track of the current amount of reconnect attempts if the infinite attempts ("-1") is specified. This task is to add this ability to the endpoint, along the ability to check what the current value is and for users to be able to see the current amount of attempts in the trace message if there is an error sending. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1875) Release WildFly Elytron 1.10.1.Final

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1875?page=com.atlassian.jira.plugin.s... ] Farah Juma resolved ELY-1875. ----------------------------- Resolution: Done > Release WildFly Elytron 1.10.1.Final > ------------------------------------ > > Key: ELY-1875 > URL: https://issues.jboss.org/browse/ELY-1875 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.10.1.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12503) Turn off the default surefire execution when the 'elytron' and 'security.manager' profiles are used

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12503?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12503: ------------------------------------ Description: We have CI runs for PRs that differ from the basic ones by using -Delytron instead of -DallTests to turn on profiles that select a subset of the testsuite and to specially configure things for that subset. Same for -Dsecurity.manager. Expand on this by having -Delytron and -Dsecurity.manager also turn on profiles that turn off the default surefire execution, so surefire only runs for those maven modules where a profile turns it back on. There's no point, for example, running the 'undertow' maven module tests in these CI runs. was: We have CI runs for PRs that differ from the basic ones by using -Delytron instead of -DallTests to turn on profiles that select a subset of the testsuite and to specially configure things for that subset. Expand on this by having -Delytron also turn on a profile that turns off the default surefire execution, so surefire only runs for those maven modules where an elytron profile turns it back on. There's no point, for example, running the 'undertow' maven module tests in these CI runs. > Turn off the default surefire execution when the 'elytron' and 'security.manager' profiles are used > --------------------------------------------------------------------------------------------------- > > Key: WFLY-12503 > URL: https://issues.jboss.org/browse/WFLY-12503 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > We have CI runs for PRs that differ from the basic ones by using -Delytron instead of -DallTests to turn on profiles that select a subset of the testsuite and to specially configure things for that subset. Same for -Dsecurity.manager. > Expand on this by having -Delytron and -Dsecurity.manager also turn on profiles that turn off the default surefire execution, so surefire only runs for those maven modules where a profile turns it back on. There's no point, for example, running the 'undertow' maven module tests in these CI runs. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12503) Turn off the default surefire execution when the 'elytron' and 'security.manager' profiles are used

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12503?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12503: ------------------------------------ Summary: Turn off the default surefire execution when the 'elytron' and 'security.manager' profiles are used (was: Turn off the default surefire execution when the 'elytron' profile is used) > Turn off the default surefire execution when the 'elytron' and 'security.manager' profiles are used > --------------------------------------------------------------------------------------------------- > > Key: WFLY-12503 > URL: https://issues.jboss.org/browse/WFLY-12503 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > We have CI runs for PRs that differ from the basic ones by using -Delytron instead of -DallTests to turn on profiles that select a subset of the testsuite and to specially configure things for that subset. > Expand on this by having -Delytron also turn on a profile that turns off the default surefire execution, so surefire only runs for those maven modules where an elytron profile turns it back on. There's no point, for example, running the 'undertow' maven module tests in these CI runs. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12503) Turn off the default surefire execution when the 'elytron' profile is used

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12503: --------------------------------------- Summary: Turn off the default surefire execution when the 'elytron' profile is used Key: WFLY-12503 URL: https://issues.jboss.org/browse/WFLY-12503 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry We have CI runs for PRs that differ from the basic ones by using -Delytron instead of -DallTests to turn on profiles that select a subset of the testsuite and to specially configure things for that subset. Expand on this by having -Delytron also turn on a profile that turns off the default surefire execution, so surefire only runs for those maven modules where an elytron profile turns it back on. There's no point, for example, running the 'undertow' maven module tests in these CI runs. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12502) Move to jakarta.inject:jakarta.inject-api

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12502?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12502: --------------------------------- Description: This will be a two commit, three step process since the {{javax.injecti}} module is in WildFly Core. # Create the {{jjavax.inject}} module in full. This is the first commit # Change the {{javax.inject:javax.inject:1}} dependencies in other modules to {{jakarta.inject:jakarta.inject-api:1.0}}. This is the second commit. # Once core, WFCORE-4630, is merged into WildFly revert the first commit. was: Migrate from javax.inject:javax.inject:1 to jakarta.inject:jakarta.inject-api:1.0 once it has been formally released and available at maven central. Jakarta specification release: https://github.com/jakartaee/specifications/pull/63 WildFly boms would need to be revised. WildFly feature-packs are also using the javax.inject:javax.inject dependency. Exclusions for other dependencies could be required > Move to jakarta.inject:jakarta.inject-api > ----------------------------------------- > > Key: WFLY-12502 > URL: https://issues.jboss.org/browse/WFLY-12502 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > This will be a two commit, three step process since the {{javax.injecti}} module is in WildFly Core. > # Create the {{jjavax.inject}} module in full. This is the first commit > # Change the {{javax.inject:javax.inject:1}} dependencies in other modules to {{jakarta.inject:jakarta.inject-api:1.0}}. This is the second commit. > # Once core, WFCORE-4630, is merged into WildFly revert the first commit. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12502) Move to jakarta.inject:jakarta.inject-api

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12502?page=com.atlassian.jira.plugin... ] James Perkins reassigned WFLY-12502: ------------------------------------ Assignee: James Perkins (was: Yeray Borges) > Move to jakarta.inject:jakarta.inject-api > ----------------------------------------- > > Key: WFLY-12502 > URL: https://issues.jboss.org/browse/WFLY-12502 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Yeray Borges > Assignee: James Perkins > Priority: Major > > This will be a two commit, three step process since the {{javax.injecti}} module is in WildFly Core. > # Create the {{jjavax.inject}} module in full. This is the first commit > # Change the {{javax.inject:javax.inject:1}} dependencies in other modules to {{jakarta.inject:jakarta.inject-api:1.0}}. This is the second commit. > # Once core, WFCORE-4630, is merged into WildFly revert the first commit. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12502) Move to jakarta.inject:jakarta.inject-api

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12502?page=com.atlassian.jira.plugin... ] James Perkins moved WFCORE-4650 to WFLY-12502: ---------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-12502 (was: WFCORE-4650) Component/s: EE (was: Build System) > Move to jakarta.inject:jakarta.inject-api > ----------------------------------------- > > Key: WFLY-12502 > URL: https://issues.jboss.org/browse/WFLY-12502 > Project: WildFly > Issue Type: Task > Components: EE > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > Migrate from javax.inject:javax.inject:1 to jakarta.inject:jakarta.inject-api:1.0 once it has been formally released and available at maven central. > Jakarta specification release: https://github.com/jakartaee/specifications/pull/63 > WildFly boms would need to be revised. > WildFly feature-packs are also using the javax.inject:javax.inject dependency. > Exclusions for other dependencies could be required -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 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 September 2019