July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3091) ListValidator should implement MinMaxValidator

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3091?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3091: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2637 (was: https://github.com/wildfly/wildfly-core/pull/2638) > ListValidator should implement MinMaxValidator > ---------------------------------------------- > > Key: WFCORE-3091 > URL: https://issues.jboss.org/browse/WFCORE-3091 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > If the kernel detects an attribute uses MinMaxValidator it uses the min and max to report min/max or min-length/max-length metadata, with the "-length" option used for model types where that is appropriate. So MinMaxValidator is appropriate for LIST attributes since the data will be reported correctly. > But the primary validator for lists, ListValidator does not implement MinMaxValidator even though it stores and uses a min and max for its validation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3091) ListValidator should implement MinMaxValidator

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3091: ---------------------------------------- Summary: ListValidator should implement MinMaxValidator Key: WFCORE-3091 URL: https://issues.jboss.org/browse/WFCORE-3091 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry If the kernel detects an attribute uses MinMaxValidator it uses the min and max to report min/max or min-length/max-length metadata, with the "-length" option used for model types where that is appropriate. So MinMaxValidator is appropriate for LIST attributes since the data will be reported correctly. But the primary validator for lists, ListValidator does not implement MinMaxValidator even though it stores and uses a min and max for its validation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2422) Credential Store alias name in camel case leads to AssertionError.

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2422?page=com.atlassian.jira.plugi... ] Paul Ferraro commented on WFCORE-2422: -------------------------------------- [~dlofthouse] What change was associated with resolving this issue? JBEAP-11521 fails with the same exception, and has similar symptoms, i.e. commands succeed using CLI, but fail when executed by a test. > Credential Store alias name in camel case leads to AssertionError. > ------------------------------------------------------------------ > > Key: WFCORE-2422 > URL: https://issues.jboss.org/browse/WFCORE-2422 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > Fix For: 3.0.0.Beta29 > > > Credential Store alias name in camel case leads to AssertionError. > I am not able to reproduce it over jboss-cli but I can reproduce it in tests. > You can see to attachment. > *How to reproduce* > * unzip uppercasealias.zip to wildfly/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/security/credential/store > * cd wildfly/testsuite/integration/basic > * mvn test -Dtest=CredentialStoreTestCase > In log you can see this: > {code} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("credential-store" => "testCamelCase"), > ("alias" => "camelcasenotationalias") > ]): java.lang.AssertionError > at org.jboss.as.controller.access.permission.ManagementPermissionAuthorizer.authorize(ManagementPermissionAuthorizer.java:87) > at org.jboss.as.controller.access.management.DelegatingConfigurableAuthorizer.authorize(DelegatingConfigurableAuthorizer.java:99) > at org.jboss.as.controller.OperationContextImpl.getBasicAuthorizationResponse(OperationContextImpl.java:1841) > at org.jboss.as.controller.OperationContextImpl.authorize(OperationContextImpl.java:1739) > at org.jboss.as.controller.OperationContextImpl.authorize(OperationContextImpl.java:1698) > at org.jboss.as.controller.OperationContextImpl.getResourceRegistration(OperationContextImpl.java:575) > at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:270) > at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:146) > at org.wildfly.extension.elytron.CredentialStoreAliasDefinition$AddHandler.execute(CredentialStoreAliasDefinition.java:209) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:921) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:664) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:383) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1390) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:419) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:240) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:193) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:212) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:185) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157) > 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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2003) replacement expression in access-control

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2003?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-2003. -------------------------------------- Resolution: Won't Do We won't do this. We didn't allow expressions on the RBAC attributes because that opens up the possibility of inconsistent RBAC configuration across a managed domain. > replacement expression in access-control > ---------------------------------------- > > Key: WFCORE-2003 > URL: https://issues.jboss.org/browse/WFCORE-2003 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 2.1.0.Final > Environment: EAP7.0.3 > Reporter: Hisanobu Okuda > Assignee: Brian Stansberry > > Our customer wants to use replacement expression in `<access-control/>`: > {code} > ${env.VARNAME} for environemt vars > ${VARNAME} for system properties > ${VAULT::BLOCK::attribute::1} for vars stored inside jboss vault > {code} > Example: > while adding group in for any role like (SuperUser) . > {code} > /core-service=management/access=authorization/role-mapping=SuperUser/include="group_admin":add(name="${ldap_admin_grp}", type=GROUP) > {code} > resulting : > {code} > <role name="SuperUser"> > <include> > <user name="$local"/> > <group alias="group_admin" name="${ldap_admin_grp}"/> > </include> > </role> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9121) QS: Synchronize quickstart-documentation-plugin configuration with downstream

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9121: ------------------------------------ Summary: QS: Synchronize quickstart-documentation-plugin configuration with downstream Key: WFLY-9121 URL: https://issues.jboss.org/browse/WFLY-9121 Project: WildFly Issue Type: Bug Components: Quickstarts Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1299) X509EvidenceVerificationSuiteChild.testX509Auth() fails on IBM JDK

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/ELY-1299?page=com.atlassian.jira.plugin.s... ] Peter Palaga commented on ELY-1299: ----------------------------------- bq. {{Pem.parsePemX509Certificate()}} does not accept PEM files with paintext prefix either. Should I file that as a separate issue? I have filed ELY-1300 and ELY-1301. > X509EvidenceVerificationSuiteChild.testX509Auth() fails on IBM JDK > ------------------------------------------------------------------ > > Key: ELY-1299 > URL: https://issues.jboss.org/browse/ELY-1299 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > > {code} > export JAVA_HOME=path/to/ibm/java8 > $JAVA_HOME/bin/java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR3_20160915_0912_B318796 > JIT - tr.r14.java.green_20160818_122998 > GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS > J9CL - 20160915_318796) > JCL - 20160914_01 based on Oracle jdk8u101-b13 > mvn clean test -Dtest=LdapTestSuite > {code} > Expected: the selected test suite passes > Actual: {{X509EvidenceVerificationSuiteChild.testX509Auth()}} fails with the following exception: > {code} > java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data > at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268) > at java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:407) > at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.loadCertificate(X509EvidenceVerificationSuiteChild.java:74) > at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:508) > at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:61) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1168) Wildfly Elytron Tool, credential-store command "add" option with --entry-type without argument value pass.

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/ELY-1168?page=com.atlassian.jira.plugin.s... ] Peter Skopek resolved ELY-1168. ------------------------------- Resolution: Done Resolved with https://issues.jboss.org/browse/ELY-1165 > Wildfly Elytron Tool, credential-store command "add" option with --entry-type without argument value pass. > ---------------------------------------------------------------------------------------------------------- > > Key: ELY-1168 > URL: https://issues.jboss.org/browse/ELY-1168 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Chao Wang > > Wildfly Elytron Tool, credential-store command "add" option with --entry-type without argument value pass. > It seems to be little confusing. I prefer error message rather than success. > Reason why it works now is because as a value is used default value for entry-type. > *How to reproduce* > {code} > java -jar ./bin/wildfly-elytron-tool.jar credential-store --add secret_alias --create -l store123.jceks --password pass123 -x test -n > Alias "secret_alias" has been successfully stored > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9120) Upgrade RESTEasy to 3.0.24.Final

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-9120: ------------------------------------- Summary: Upgrade RESTEasy to 3.0.24.Final Key: WFLY-9120 URL: https://issues.jboss.org/browse/WFLY-9120 Project: WildFly Issue Type: Component Upgrade Components: REST Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2205) DISCARD ignores the DONT_LOOPBACK transient flag

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2205?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2205: --------------------------- Fix Version/s: 4.0.5 > DISCARD ignores the DONT_LOOPBACK transient flag > ------------------------------------------------ > > Key: JGRP-2205 > URL: https://issues.jboss.org/browse/JGRP-2205 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.4 > Reporter: Dan Berindei > Assignee: Bela Ban > Fix For: 4.0.5 > > > When {{discard_all = true}}, {{DISCARD}} does its own loopback, and doesn't check for {{DONT_LOOPBACK}} like {{TP}}. It always sends the message back up, even if {{excludeItself = false}}. > If possible, {{DISCARD}} should just set the message destination to the local address and pass the message down. That way, {{TP}} would decide make the loopback decision, and using the {{TP}} thread pool would also make the thread name nicer in the logs. (Currently the thread name is {{Thread-n}}, which means searching for the test name in our test suite's log misses some messages.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3085) Update license related information

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3085?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3085: ------------------------------------------ [~kabirkhan] +1 [~psakar] Any relicensing of WildFly Core is definitely out of scope for our current work. :) It's been under consideration for years now and hasn't happened due to the amount of effort involved. > Update license related information > ---------------------------------- > > Key: WFCORE-3085 > URL: https://issues.jboss.org/browse/WFCORE-3085 > Project: WildFly Core > Issue Type: Task > Affects Versions: 3.0.0.Beta28 > Reporter: Petr Sakař > > Please change name of license in root pom file licenses tag to comply with the name from the first column of the license list https://spdx.org/licenses/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 July 2017