December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10777) Add WildFly Elytron / JASPI Integration Tests

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10777?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10777: --------------------------------- Fix Version/s: 15.0.0.Final > Add WildFly Elytron / JASPI Integration Tests > --------------------------------------------- > > Key: WFLY-10777 > URL: https://issues.jboss.org/browse/WFLY-10777 > Project: WildFly > Issue Type: Task > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > The following key scenarios should be covered within the Elytron testsuite module: - > * Pre-configured JASPIC > In this case the SAMs are configured within the Elytron subsystem and applied at runtime to the web application. > Two predominant modes to consider: - > # Fully integrated, i.e. the Callbacks make use of the SecurityDomain for authentication. > # Ad-Hoc Identity i.e. We still have a security domain but trust the SAM to establish an ad-hoc identity. > * Programatically configured JASPIC > During servlet initilisation the new JaspicConfigurationBuilder API can be used to dynamically register a configuration. > Likely to need the same two modes. > * Retrospective JASPIC > In both the above cases the deployment can be deployed and either use Elytron HTTP authentication mechanisms or be unsecured, JASPIC for the deployment can be activated either via configuration or programatically and should take precedence over the existing authentication. > * Programatic Authentication > A servlet can use the authentication API on the HttpServletRequest and trigger authentication. > * No SecurityDomain > This one may not be as applicable at this stage but we should at some point support JASPIC being applied to a deployment not associated with any security domain, i.e. a new deployment on a clean install could programatically register a JASPIC configuration. > Without any security domain the identity would only have relevance within the servlet container so establishing an ad-hoc identity is actually a better approach. Additionally this relies on no default being present in the default config. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10966) Add version 8 of the Undertow subsystem schema and model

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10966?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10966: --------------------------------- Fix Version/s: 15.0.0.Final > Add version 8 of the Undertow subsystem schema and model > -------------------------------------------------------- > > Key: WFLY-10966 > URL: https://issues.jboss.org/browse/WFLY-10966 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11232) Upgrade jboss-ejb-client from 4.0.11 to 4.0.12

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11232?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11232: --------------------------------- Fix Version/s: 15.0.0.Final > Upgrade jboss-ejb-client from 4.0.11 to 4.0.12 > ---------------------------------------------- > > Key: WFLY-11232 > URL: https://issues.jboss.org/browse/WFLY-11232 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > There is a single fix in the upgrade https://github.com/wildfly/jboss-ejb-client/compare/4.0.11.Final...4.0.12... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11229) Quickstarts JBDS WSDLAnalyzer warning

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11229?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11229: --------------------------------- Fix Version/s: 15.0.0.Final > Quickstarts JBDS WSDLAnalyzer warning > ------------------------------------- > > Key: WFLY-11229 > URL: https://issues.jboss.org/browse/WFLY-11229 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Environment: Fedora 27, Red Hat Developer Studio 12.0, jdk 1.8.0_162, 7.2.0.Beta.CR1 EAP/Maven/QS > Reporter: Sande Gilda > Assignee: Eduardo Martins > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > The following quickstarts: > * jaxws-addressing > * jaxws-retail > * wsat-simple > have the following warning after an import to Red Hat Developer Studio: > {noformat} > WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File. > AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem > RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem > ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem > {noformat} > This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10810) WildFly Elytron JASPI Integration

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10810?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10810: --------------------------------- Fix Version/s: 15.0.0.Final > WildFly Elytron JASPI Integration > --------------------------------- > > Key: WFLY-10810 > URL: https://issues.jboss.org/browse/WFLY-10810 > Project: WildFly > Issue Type: Feature Request > Components: Security, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11212) Do not register jdbc-driver's datasource-class-info as metric

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11212?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11212: --------------------------------- Fix Version/s: 15.0.0.Final > Do not register jdbc-driver's datasource-class-info as metric > ------------------------------------------------------------- > > Key: WFLY-11212 > URL: https://issues.jboss.org/browse/WFLY-11212 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 14.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > jdbc-driver resource registers 1 attribute as metric: > * datasource-class-info > {code} > /subsystem=datasources/jdbc-driver=h2:read-attribute(name=datasource-class-info) > { > "outcome" => "success", > "result" => [{"org.h2.jdbcx.JdbcDataSource" => { > "URL" => "java.lang.String", > "description" => "java.lang.String", > "loginTimeout" => "int", > "password" => "java.lang.String", > "url" => "java.lang.String", > "user" => "java.lang.String" > }}] > } > {code} > This attribute is not an actual metric (that may change due to server activity). > It should be registered as runtime read-only attributes instead. > This change only impacts metadata and does not require resource transformation. > Additionally, I've checked with HAL team that this change has no impact on HAL UI (that does not distinguish between read-only runtime attribute and metric). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11194) NPE removing a pooled-connection-factory

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11194?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11194: --------------------------------- Fix Version/s: 15.0.0.Final > NPE removing a pooled-connection-factory > ---------------------------------------- > > Key: WFLY-11194 > URL: https://issues.jboss.org/browse/WFLY-11194 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Claudio Miranda > Assignee: ehsavoie Hugonnet > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > There is a NullPointerException when try to remove a pooled-connection-factory > {code} > /subsystem=messaging-activemq/in-vm-connector=invm1:add(server-id=123) > /subsystem=messaging-activemq/pooled-connection-factory=pool3:add(connectors=[invm1],entries=[foo]) > /subsystem=messaging-activemq/pooled-connection-factory=pool3:remove() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException", > "rolled-back" => true > } > {code} > {code} > 15:46:19,661 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("remove") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("pooled-connection-factory" => "pool3") > ]): java.lang.NullPointerException > at org.wildfly.extension.messaging.activemq.jms.JMSServices.getPooledConnectionFactoryBaseServiceName(JMSServices.java:64) > at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryRemove.performRuntime(PooledConnectionFactoryRemove.java:56) > at org.jboss.as.controller.AbstractRemoveStepHandler$1.execute(AbstractRemoveStepHandler.java:84) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11182) Upgrade to WildFly Galleon Plugins 2.0.2.Final and properly configure plugin dependencies

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11182?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11182: --------------------------------- Fix Version/s: 15.0.0.Final > Upgrade to WildFly Galleon Plugins 2.0.2.Final and properly configure plugin dependencies > ----------------------------------------------------------------------------------------- > > Key: WFLY-11182 > URL: https://issues.jboss.org/browse/WFLY-11182 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > This commit fixes the classpath of the maven plugin building Galleon feature-pack by moving feature-spec-gen artifact to its classpath. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11234) Since WildFly 14 i18n ResourceBundle properties file not found if without locale

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11234?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11234: --------------------------------- Fix Version/s: 15.0.0.Final > Since WildFly 14 i18n ResourceBundle properties file not found if without locale > -------------------------------------------------------------------------------- > > Key: WFLY-11234 > URL: https://issues.jboss.org/browse/WFLY-11234 > Project: WildFly > Issue Type: Bug > Affects Versions: 14.0.1.Final > Environment: Ubuntu 18.04, OpenJDK 8 and 11 > Reporter: Anton Pussep > Assignee: Brian Stansberry > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > As discussed in this thread > https://developer.jboss.org/message/985930 > my i18n properties have not been resolved on WildFly 14.0.1.Final - it was working fine through WildFly 10-13, however. I could solve the issue by renaming my properties file from messages.properties to messages_en.properties. Since this solved the issue, I suspect that WildFly 14 does not accept filenames without locale anymore. Since I'm not sure if this is by design, I'm posting this as a bug report here. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11202) Default ResourceBundle fails to load

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11202?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11202: --------------------------------- Fix Version/s: 15.0.0.Final > Default ResourceBundle fails to load > ------------------------------------ > > Key: WFLY-11202 > URL: https://issues.jboss.org/browse/WFLY-11202 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 14.0.1.Final > Reporter: Andrew Schmidt > Assignee: Brian Stansberry > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > Attachments: resourcebundle.zip > > > Wildfly 14 no longer loads the default message bundle when a locale is specified and the specific locale has no properties file. > For example, in the attached project, I have a messages.properties file, Wildfly 13 and previous releases would simply load the messages.properties if there is no messages_en.properties. But in wildfly 14 this is no longer the case (it appears it provides a different resourcebundle) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 2018