March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8137) Credential store alias with upper-case letters can't be added when Java assertions are enabled

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8137?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-8137: -------------------------------------- Assignee: Brian Stansberry (was: Darran Lofthouse) The downstream JIRA is unassigned, so I'm assigning it to myself. > Credential store alias with upper-case letters can't be added when Java assertions are enabled > ---------------------------------------------------------------------------------------------- > > Key: WFLY-8137 > URL: https://issues.jboss.org/browse/WFLY-8137 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Brian Stansberry > Priority: Critical > > When Java assertions are enable then adding credential store entry (alias) with upper case letters fails with assertion error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8290) Switch to using Elytron Subsystem from WildFly Core

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-8290: -------------------------------------- Summary: Switch to using Elytron Subsystem from WildFly Core Key: WFLY-8290 URL: https://issues.jboss.org/browse/WFLY-8290 Project: WildFly Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8276) Upgrade JBeret from 1.2.2.Final to 1.2.3.Final

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-8276?page=com.atlassian.jira.plugin.... ] Cheng Fang commented on WFLY-8276: ---------------------------------- JBeret 1.2.3.Final is now out. For details, see JIRA release info: https://issues.jboss.org/projects/JBERET/versions/12333072 > Upgrade JBeret from 1.2.2.Final to 1.2.3.Final > ---------------------------------------------- > > Key: WFLY-8276 > URL: https://issues.jboss.org/browse/WFLY-8276 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > > Once JBeret 1.2.3.Final is released and upgrade of the component should be done. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7618) Fix code to not use default platform dependant encoding

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7618?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-7618: ---------------------------------------- [~ctomc] Can you link or attach that analysis? > Fix code to not use default platform dependant encoding > ------------------------------------------------------- > > Key: WFLY-7618 > URL: https://issues.jboss.org/browse/WFLY-7618 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Tomaz Cerar > > WFLY codebase depends in some cases on system default encoding. This should be fixed to use de facto standard UTF8. > This JIRA is followup of WFCORE-1510 in the main codebase. Main concern (proven by history too) is Windows. > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8289) FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8289?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved WFCORE-1351 to WFLY-8289: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-8289 (was: WFCORE-1351) Component/s: Remoting Security (was: Remoting) (was: Security) Fix Version/s: (was: 3.0.0.Beta8) > FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-8289 > URL: https://issues.jboss.org/browse/WFLY-8289 > Project: WildFly > Issue Type: Bug > Components: Remoting, Security > Reporter: Ondrej Kotek > Assignee: Ivo Studensky > Priority: Critical > Attachments: 1-no-createEndpoint-permission.stacktrace, 2-no-createXnioWorker-permission.stacktrace, 3-no-addConnectionProvider-permission.stacktrace, 4-no-accessDeclaredMembers-permission.stractrace, 5-no-suppressAccessChecks-permission.stracktrace > > > # Running _NestedRemoteContextTestCase_ (from WildFly _testsuite/integration/basic_) with security manager, like > {noformat} > ./integration-tests.sh -Dts.basic -Dts.noSmoke -Dtest=NestedRemoteContextTestCase -Dsecurity.manager > {noformat} > results in exception: > {noformat} > java.io.IOException: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found > {noformat} > To make it work, permissions like following need to be added to _permissions.xml_ of _ejb.ear_: > {noformat} > new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/xnio/nio/main/*", "read"), > new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/marshalling/river/main/*", "read"), > new RemotingPermission("createEndpoint"), > new RuntimePermission("createXnioWorker"), > new RemotingPermission("addConnectionProvider"), > new RuntimePermission("modifyThread"), > new RuntimePermission("accessDeclaredMembers"), > new ReflectPermission("suppressAccessChecks") > {noformat} > which is very confusing. > Why do I need add seemingly unrelated permissions, like _FilePermission_ for XNIO and marshalling or _RuntimePermission_ for createXnioWorker? Such behavior should be fixed or properly documented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1351) FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1351?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1351: ------------------------------------------ Hmm, so there isn't a WFLY issue for this, as this is WFLY-5989 moved to core. > FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1351 > URL: https://issues.jboss.org/browse/WFCORE-1351 > Project: WildFly Core > Issue Type: Bug > Components: Remoting, Security > Reporter: Ondrej Kotek > Assignee: Ivo Studensky > Priority: Critical > Fix For: 3.0.0.Beta8 > > Attachments: 1-no-createEndpoint-permission.stacktrace, 2-no-createXnioWorker-permission.stacktrace, 3-no-addConnectionProvider-permission.stacktrace, 4-no-accessDeclaredMembers-permission.stractrace, 5-no-suppressAccessChecks-permission.stracktrace > > > # Running _NestedRemoteContextTestCase_ (from WildFly _testsuite/integration/basic_) with security manager, like > {noformat} > ./integration-tests.sh -Dts.basic -Dts.noSmoke -Dtest=NestedRemoteContextTestCase -Dsecurity.manager > {noformat} > results in exception: > {noformat} > java.io.IOException: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found > {noformat} > To make it work, permissions like following need to be added to _permissions.xml_ of _ejb.ear_: > {noformat} > new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/xnio/nio/main/*", "read"), > new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/marshalling/river/main/*", "read"), > new RemotingPermission("createEndpoint"), > new RuntimePermission("createXnioWorker"), > new RemotingPermission("addConnectionProvider"), > new RuntimePermission("modifyThread"), > new RuntimePermission("accessDeclaredMembers"), > new ReflectPermission("suppressAccessChecks") > {noformat} > which is very confusing. > Why do I need add seemingly unrelated permissions, like _FilePermission_ for XNIO and marshalling or _RuntimePermission_ for createXnioWorker? Such behavior should be fixed or properly documented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1965) Remove the jboss-logging-annotations dependency where it is not used

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1965?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1965: ---------------------------------- Summary: Remove the jboss-logging-annotations dependency where it is not used (was: Remove the jboss-logging-annotations dependency from the core feature pack.) > Remove the jboss-logging-annotations dependency where it is not used > -------------------------------------------------------------------- > > Key: WFCORE-1965 > URL: https://issues.jboss.org/browse/WFCORE-1965 > Project: WildFly Core > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: James Perkins > Priority: Critical > Fix For: 3.0.0.Beta8 > > > This was added inadvertently with some other changes: - > {noformat} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging-annotations</artifactId> > </dependency> > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2301) Mount point not found exception raised by createTempFileWithAttributes on overlayfs [JDK-8165852]

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2301?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2301: ------------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta8) > Mount point not found exception raised by createTempFileWithAttributes on overlayfs [JDK-8165852] > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-2301 > URL: https://issues.jboss.org/browse/WFCORE-2301 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Environment: WildFly via KeyCloak 2.5.1.Final > {code:xml} > <eap.version>7.0.0.Beta</eap.version> > <jboss.as.version>7.2.0.Final</jboss.as.version> > <wildfly.version>10.0.0.Final</wildfly.version> > {code} > on Docker with overlayfs or overlayfs2 as storage driver > \# docker info | grep -i storage > aufs: works (e.g., boot2docker, legacy minikube) > overlay (e.g., CoreOS, current minikube): problem > devicemapper (e.g., CentOS): works > overlay2 (e.g., Docker for Mac): problem > Reporter: Bjoern Stuetz > Assignee: Brian Stansberry > Fix For: 3.0.0.Beta3, 2.2.1.CR2 > > > Mount point not found exception raised by createTempFileWithAttributes on overlayfs [JDK-8165852], i.e., > /opt/jboss/bin/jboss-cli.sh --file=/opt/jboss/jboss-config.cli > inside a Docker container running on overlayfs as storage driver > causes (full stack trace below): > {code:java} > java.io.IOException: Mount point not foundImage > at sun.nio.fs.LinuxFileStore.findMountEntry(LinuxFileStore.java:91) > {code} > triggered by > {code:java} > at org.jboss.as.controller.persistence.FilePersistenceUtils.createTempFileWithAttributes(FilePersistenceUtils.java:117) > at org.jboss.as.controller.persistence.FilePersistenceUtils.writeToTempFile(FilePersistenceUtils.java:104) > {code} > due to OpenJDK bug/overlayfs bug. > We acknowledge that this is in fact an OpenJDK AND/OR overlayfs bug. However everything seems to run fine in WildFly except once the backup of the config is triggered, for example by using the cli. Hence WildFly is of limited functionality when the more and more popular overlayfs storage driver is used, and the WildFly team might be interested in providing a workaround on their side since there is no indication the OpenJDK bug will be promptly fixed. We are happy to help in any way, we are still trying to find a workaround on the Java or WildFly side; but we might need insights on why findMountEntry is invoked. > Full Stack Trace: > {code:java} > java.io.IOException: Mount point not foundImage > at sun.nio.fs.LinuxFileStore.findMountEntry(LinuxFileStore.java:91) > at sun.nio.fs.UnixFileStore.<init>(UnixFileStore.java:65) > at sun.nio.fs.LinuxFileStore.<init>(LinuxFileStore.java:44) > at sun.nio.fs.LinuxFileSystemProvider.getFileStore(LinuxFileSystemProvider.java:51) > at sun.nio.fs.LinuxFileSystemProvider.getFileStore(LinuxFileSystemProvider.java:39) > at sun.nio.fs.UnixFileSystemProvider.getFileStore(UnixFileSystemProvider.java:368) > at java.nio.file.Files.getFileStore(Files.java:1461) > at org.jboss.as.controller.persistence.FilePersistenceUtils.getPosixAttributes(FilePersistenceUtils.java:129) > at org.jboss.as.controller.persistence.FilePersistenceUtils.createTempFileWithAttributes(FilePersistenceUtils.java:117) > at org.jboss.as.controller.persistence.FilePersistenceUtils.writeToTempFile(FilePersistenceUtils.java:104) > at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.doCommit(ConfigurationFilePersistenceResource.java:55) > at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.commit(AbstractFilePersistenceResource.java:58) > at org.jboss.as.controller.ModelControllerImpl$4.commit(ModelControllerImpl.java:781) > at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204) > at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:659) > at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:649) > at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerClient.java:63) > at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.execute(ThreadContextsModelControllerClient.java:59) > at org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle(BatchRunHandler.java:91) > at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:88) > at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:776) > at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:799) > at org.jboss.as.cli.impl.CliLauncher.processFile(CliLauncher.java:334) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:262) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.modules.Module.run(Module.java:329) > at org.jboss.modules.Main.main(Main.java:507) > {code} > Java Bug Overview: > https://bugs.openjdk.java.net/browse/JDK-8165852 > http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u... > Wildfly Stack Overflow issue, not solved: > https://stackoverflow.com/questions/41022393/mount-point-not-found > Background Info: > http://mail.openjdk.java.net/pipermail/nio-dev/2016-October/003915.html > A) chroot environment [1] > B) Docker container with overlay and overlay2 storage drivers [2] > C) btrfs file system with an unmounted sub-volume [2] > [1] https://bugs.openjdk.java.net/browse/JDK-8165323 - cannot get FileStore in chroot environment > [2] https://bugs.openjdk.java.net/browse/JDK-8165852 - cannot get FileStore for a file in overlayfs in Docker > Docker file system/storage driver: > https://docs.docker.com/engine/userguide/storagedriver/selectadriver/) > Yum yum-plugin-ovl, similar problem: > https://github.com/CentOS/sig-cloud-instance-images/issues/15 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2361) [2.x] Upgrade XNIO to 3.4.3

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2361?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2361: ------------------------------------------ The merge commit for WFCORE-2361 references WFCORE-2116, but in the end it was about 2361. > [2.x] Upgrade XNIO to 3.4.3 > --------------------------- > > Key: WFCORE-2361 > URL: https://issues.jboss.org/browse/WFCORE-2361 > Project: WildFly Core > Issue Type: Component Upgrade > Components: IO > Reporter: Brian Stansberry > Assignee: Frank Langelage > Fix For: 2.2.1.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2361) [2.x] Upgrade XNIO to 3.4.3

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2361: ---------------------------------------- Summary: [2.x] Upgrade XNIO to 3.4.3 Key: WFCORE-2361 URL: https://issues.jboss.org/browse/WFCORE-2361 Project: WildFly Core Issue Type: Component Upgrade Components: IO Reporter: Brian Stansberry Assignee: Frank Langelage Fix For: 2.2.1.CR2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 March 2017