September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-2007) Bring SecurityIdentity PolicyContextHandler inline with WildFly Core implementation.

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2007?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2007: ---------------------------- Fix Version/s: 1.10.9.CR1 > Bring SecurityIdentity PolicyContextHandler inline with WildFly Core implementation. > ------------------------------------------------------------------------------------ > > Key: ELY-2007 > URL: https://issues.redhat.com/browse/ELY-2007 > Project: WildFly Elytron > Issue Type: Enhancement > Components: EE > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2, 1.10.9.CR1 > > > There is an implementation in WildFly Core which uses SecurityDomain.getCurrent() - move this to the Elytron implementation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-2008) Move JACC tests into JACC module

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2008?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2008: ---------------------------- Fix Version/s: 1.10.9.CR1 > Move JACC tests into JACC module > -------------------------------- > > Key: ELY-2008 > URL: https://issues.redhat.com/browse/ELY-2008 > Project: WildFly Elytron > Issue Type: Enhancement > Components: EE, Testsuite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2, 1.10.9.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-2006) Add a "Delegating" PolicyContextHandler

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2006?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2006: ---------------------------- Fix Version/s: 1.10.9.CR1 > Add a "Delegating" PolicyContextHandler > --------------------------------------- > > Key: ELY-2006 > URL: https://issues.redhat.com/browse/ELY-2006 > Project: WildFly Elytron > Issue Type: Enhancement > Components: EE > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2, 1.10.9.CR1 > > > We have some cases in WildFly Core where we need to install a WildFly Elytron PolicyContextHandler but delegate to a legacy implementation if an Elytron identity is not available. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-2005) Support for "Container Subject Policy Context Handler" should be in Elytron

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2005?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2005: ---------------------------- Fix Version/s: 1.10.9.CR1 > Support for "Container Subject Policy Context Handler" should be in Elytron > --------------------------------------------------------------------------- > > Key: ELY-2005 > URL: https://issues.redhat.com/browse/ELY-2005 > Project: WildFly Elytron > Issue Type: Task > Components: EE > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2, 1.10.9.CR1 > > > Support should be in WildFly Elytron, the majority of the code presently lives within WildFly Core. > However to complicate it further the current implementation presently depends upon "java.security.acl.Group" - we probably should skip this step if the Group interface is not available. > We may be able to do a better multi release jar switch later but I think that will depend upon the project moving to be built with Java 17. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-348) Bootable JAR - No context is registered on server if packaging is left on default

by Jan Kasik (Jira)

Jan Kasik created WFWIP-348: ------------------------------- Summary: Bootable JAR - No context is registered on server if packaging is left on default Key: WFWIP-348 URL: https://issues.redhat.com/browse/WFWIP-348 Project: WildFly WIP Issue Type: Bug Reporter: Jan Kasik Assignee: Jean Francois Denise When default packaging for app is selected (meaning no {{<packaging>}}), the app deploys but no web context is registered. {{war}} must be set as value of {{<packaging>}} in order to register web context. Since setting of packaging is not a part of plugin configuration I find it confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AG-147) Add SpringBoot starter

by Luis Barreiro (Jira)

Luis Barreiro created AG-147: -------------------------------- Summary: Add SpringBoot starter Key: AG-147 URL: https://issues.redhat.com/browse/AG-147 Project: Agroal Issue Type: Bug Components: spring Affects Versions: 1.8 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 1.9 A SpringBoot starter project will allow SpringBoot applications to use Agroal as the connection provider. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-347) Bootable JAR - No context is registered on server if packaging is left on default

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-347?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-347: ---------------------------------------- The current behaviour sounds reasonable, I think it is a minimal requirement that the pom is correctly configured for the type of the deployment before the addition of our plug-in. > Bootable JAR - No context is registered on server if packaging is left on default > --------------------------------------------------------------------------------- > > Key: WFWIP-347 > URL: https://issues.redhat.com/browse/WFWIP-347 > Project: WildFly WIP > Issue Type: Bug > Reporter: Jan Kasik > Assignee: Jean Francois Denise > Priority: Major > > When default packaging for app is selected (meaning no {{<packaging>}}), the app deploys but no web context is registered. {{war}} must be set as value of {{<packaging>}} in order to register web context. > Since setting of packaging is not a part of plugin configuration I find it confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-347) Bootable JAR - No context is registered on server if packaging is left on default

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFWIP-347?page=com.atlassian.jira.plugin... ] Jean Francois Denise commented on WFWIP-347: -------------------------------------------- That is expected. If you don't set a packaging, jar is the default. It means that the deployment is not a war, so is not set registered. That is a WildFly behavior, not a Bootable JAR one. > Bootable JAR - No context is registered on server if packaging is left on default > --------------------------------------------------------------------------------- > > Key: WFWIP-347 > URL: https://issues.redhat.com/browse/WFWIP-347 > Project: WildFly WIP > Issue Type: Bug > Reporter: Jan Kasik > Assignee: Jean Francois Denise > Priority: Major > > When default packaging for app is selected (meaning no {{<packaging>}}), the app deploys but no web context is registered. {{war}} must be set as value of {{<packaging>}} in order to register web context. > Since setting of packaging is not a part of plugin configuration I find it confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-347) Bootable JAR - No context is registered on server if packaging is left on default

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFWIP-347?page=com.atlassian.jira.plugin... ] Jean Francois Denise edited comment on WFWIP-347 at 9/8/20 9:47 AM: -------------------------------------------------------------------- That is expected. If you don't set a packaging, jar is the default. It means that the deployment is not a war, so is not registered. That is a WildFly behavior, not a Bootable JAR one. was (Author: jdenise): That is expected. If you don't set a packaging, jar is the default. It means that the deployment is not a war, so is not set registered. That is a WildFly behavior, not a Bootable JAR one. > Bootable JAR - No context is registered on server if packaging is left on default > --------------------------------------------------------------------------------- > > Key: WFWIP-347 > URL: https://issues.redhat.com/browse/WFWIP-347 > Project: WildFly WIP > Issue Type: Bug > Reporter: Jan Kasik > Assignee: Jean Francois Denise > Priority: Major > > When default packaging for app is selected (meaning no {{<packaging>}}), the app deploys but no web context is registered. {{war}} must be set as value of {{<packaging>}} in order to register web context. > Since setting of packaging is not a part of plugin configuration I find it confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-347) Bootable JAR - No context is registered on server if packaging is left on default

by Jan Kasik (Jira)

Jan Kasik created WFWIP-347: ------------------------------- Summary: Bootable JAR - No context is registered on server if packaging is left on default Key: WFWIP-347 URL: https://issues.redhat.com/browse/WFWIP-347 Project: WildFly WIP Issue Type: Bug Reporter: Jan Kasik Assignee: Jean Francois Denise When default packaging for app is selected (meaning no {{<packaging>}}), the app deploys but no web context is registered. {{war}} must be set as value of {{<packaging>}} in order to register web context. Since setting of packaging is not a part of plugin configuration I find it confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 2020