September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1778) Enhanced Audit Logging - Feature parity with legacy audit logging

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1778?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1778: ---------------------------- Fix Version/s: 1.14.0.CR1 (was: 1.13.0.Final) > Enhanced Audit Logging - Feature parity with legacy audit logging > ----------------------------------------------------------------- > > Key: ELY-1778 > URL: https://issues.redhat.com/browse/ELY-1778 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Audit > Reporter: Justin Cook > Priority: Major > Fix For: 1.14.0.CR1 > > > This RFE for Enhanced Audit Logging in WildFly Elytron is for feature parity with legacy audit logging via: > * Additional audit events > * An "Audit" annotation -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

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

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1765?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1765: ---------------------------- Fix Version/s: 1.14.0.CR1 (was: 1.13.0.Final) > Review authentication client dependencies on credential sources > --------------------------------------------------------------- > > Key: ELY-1765 > URL: https://issues.redhat.com/browse/ELY-1765 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.14.0.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.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-2021) Release WildFly Elytron 1.13.0.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2021?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2021: ---------------------------- Fix Version/s: 1.14.0.CR1 (was: 1.13.0.Final) > Release WildFly Elytron 1.13.0.Final > ------------------------------------ > > Key: ELY-2021 > URL: https://issues.redhat.com/browse/ELY-2021 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.14.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1950) FORM authentication not working for URL encoded session IDs

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1950?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1950: ---------------------------- Fix Version/s: 1.14.0.CR1 (was: 1.13.0.Final) > FORM authentication not working for URL encoded session IDs > ----------------------------------------------------------- > > Key: ELY-1950 > URL: https://issues.redhat.com/browse/ELY-1950 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.14.0.CR1 > > > The session IDs are encoded as: - > {code} > /secure/j_security_check;jsessionid=kVzsBG9c3XxcOlzpa65ohiMeMNqXdSNQuOdvdpR3.flame > {code} > However the code that checks if this is a submission to j_security_check is: - > {code:java} > request.getRequestURI().getPath().endsWith(postLocation) > {code} > This code needs to trim the path at ';' -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1842) Update the tool to support generating and exporting / importing a secret key to the credential store

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1842?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1842: ---------------------------- Fix Version/s: 1.14.0.CR1 (was: 1.13.0.Final) > Update the tool to support generating and exporting / importing a secret key to the credential store > ---------------------------------------------------------------------------------------------------- > > Key: ELY-1842 > URL: https://issues.redhat.com/browse/ELY-1842 > Project: WildFly Elytron > Issue Type: Requirement > Components: Command-Line Tool, Credential Store > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.14.0.CR1 > > > In general the following options should be supported: - > * `--generate-secret-key` > * `--export-secret-key` > * `--import-secret-key` -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1808) Undertake further review of all duplicate packages to ensure we can make unique

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1808?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1808: ---------------------------- Fix Version/s: 1.14.0.CR1 (was: 1.13.0.Final) > Undertake further review of all duplicate packages to ensure we can make unique > ------------------------------------------------------------------------------- > > Key: ELY-1808 > URL: https://issues.redhat.com/browse/ELY-1808 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.14.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1809) Update JAPICMP on a module by module basis

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1809?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1809: ---------------------------- Fix Version/s: 1.14.0.CR1 (was: 1.13.0.Final) > Update JAPICMP on a module by module basis > ------------------------------------------ > > Key: ELY-1809 > URL: https://issues.redhat.com/browse/ELY-1809 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.14.0.CR1 > > > Each module should test it's own compatibility - however the compatible version should likely be defined in the root pom. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1994) Ensure the Elytron build works on Java 14

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1994?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1994: ---------------------------- Fix Version/s: 1.14.0.CR1 (was: 1.13.0.Final) > Ensure the Elytron build works on Java 14 > ----------------------------------------- > > Key: ELY-1994 > URL: https://issues.redhat.com/browse/ELY-1994 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.14.0.CR1 > > > Overall the build is not doing too badly and doesn't fail until we get to the main testsuite. > > {code:java} > [INFO] WildFly Elytron - Tests ............................ FAILURE [ 1.447 s] > [INFO] WildFly Elytron .................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 01:46 min > [INFO] Finished at: 2020-06-11T11:25:23+01:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0-jboss-1:testCompile (default-testCompile) on project wildfly-elytron-tests: Compilation failure: Compilation failure: > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[31,25] package java.security.acl does not exist > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[107,40] cannot find symbol > [ERROR] symbol: class Group > [ERROR] location: class org.wildfly.security.auth.TestLoginModule > [ERROR] -> [Help 1] {code} > If this is all that is failing for us maybe we can revisit the test and see how appropriate it is and if it can be adapted to use available APIs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13849) Decouple version.org.infinispan.server from version.org.infinispan

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13849?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13849: ---------------------------------- Component/s: Clustering > Decouple version.org.infinispan.server from version.org.infinispan > ------------------------------------------------------------------ > > Key: WFLY-13849 > URL: https://issues.redhat.com/browse/WFLY-13849 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: No Release > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 21.0.0.Beta1 > > > This had been fixed version until recently. While this is nifty as it keeps the versions synchronized, this is a problem in: > * prod builds which override the version > * clustering CI builds which test against snapshots > * QE jobs > More details in the cloned from issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13837) Investigate JSP (Jakarta EE 9 Platform) TCK failures

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13837?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13837: ----------------------------------------- A guess is this DTD is in a jboss-metadata jar in one of our modules, and perhaps if we look at the file in the transformed archive something might jump out. > Investigate JSP (Jakarta EE 9 Platform) TCK failures > ---------------------------------------------------- > > Key: WFLY-13837 > URL: https://issues.redhat.com/browse/WFLY-13837 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Labels: EE9 > > I'm not exactly sure yet where the reference to "DTD Web Application 2.2" is coming from in the follow deployment error that occurring during JSP TCK testing: > {quote} > 2020-09-09 16:48:42,512 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "jsp_arrayelresolver_web.war" (runtime-name: "jsp_arrayelresolver_web.war") > 2020-09-09 16:48:42,625 ERROR [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-1) Cannot get schema for location: -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN: org.xml.sax.SAXParseException; systemId: file:///mnt/hudson_workspace/customWorkspaceName/wildfly/bin/-//Sun%20Microsystems,%20Inc.//DTD%20Web%20Application%202.2//EN; lineNumber: 81; columnNumber: 3; The markup in the document preceding the root element must be well-formed. > at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:201) > at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:175) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:398) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:282) > at org.apache.xerces.impl.XMLScanner.reportFatalError(XMLScanner.java:1496) > at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:784) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324) > at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:623) > at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:679) > at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(SchemaDOMParser.java:527) > at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(XSDHandler.java:2168) > at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:558) > at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:580) > at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:547) > at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:513) > at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:234) > at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638) [rt.jar:1.8.0_191] > at __redirected.__SchemaFactory.newSchema(__SchemaFactory.java:115) [jboss-modules.jar:1.10.2.Final] > at org.jboss.metadata.parser.util.XMLSchemaValidator.getSchemaForLocation(XMLSchemaValidator.java:117) [jboss-metadata-common-14.0.0.Alpha1.jar:14.0.0.Alpha1] > at org.jboss.metadata.parser.util.XMLSchemaValidator.validate(XMLSchemaValidator.java:85) [jboss-metadata-common-14.0.0.Alpha1.jar:14.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:117) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_191] > 2020-09-09 16:48:42,631 WARN [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-1) Cannot get schema for location: -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN > 2020-09-09 16:48:42,896 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/jsp_arrayelresolver_web.war"] > 2020-09-09 16:48:42,896 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/jsp_arrayelresolver_web.war"] > 2020-09-09 16:48:43,243 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jsp_arrayelresolver_web.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.jsp_arrayelresolver_web.jsp_arrayelresolver_web.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"] > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020