[JBoss JIRA] (ELY-652) There isn't possibility set entry-type for new entry in Credential Store.
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-652?page=com.atlassian.jira.plugin.sy... ]
Farah Juma resolved ELY-652.
----------------------------
Resolution: Migrated to another ITS
Resolving this one since it's already been fixed via WFCORE-2553.
> There isn't possibility set entry-type for new entry in Credential Store.
> -------------------------------------------------------------------------
>
> Key: ELY-652
> URL: https://issues.jboss.org/browse/ELY-652
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Reporter: Hynek Švábek
> Priority: Critical
>
> There isn't possibility set entry-type for new entry in Credential Store
> This CLI command
> {code}
> /subsystem=elytron/credential-store=testCS/alias=aliasEntryType:add(secret-value=secretVALUE, entry-type=org.wildfly.security.credential.PasswordCredential)
> {code}
> ends with
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: WFLYELY00909: Credential store 'testCS' does not support given credential store entry type 'org.wildfly.security.credential.PasswordCredential'",
> "rolled-back" => true
> }
> {code}
> *Server log:*
> {code}
> 10:30:39,074 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 18) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("credential-store" => "testCS"),
> ("alias" => "aliasEntryType")
> ]): java.lang.IllegalArgumentException: WFLYELY00909: Credential store 'testCS' does not support given credential store entry type 'org.wildfly.security.credential.PasswordCredential'
> at org.wildfly.extension.elytron.CredentialStoreAliasDefinition$AddHandler.performRuntime(CredentialStoreAliasDefinition.java:166)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> 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
[JBoss JIRA] (ELY-1098) WildFly Elytron Client Configuration File created based on elytron-1_0.xsd is not valid for clients
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-1098?page=com.atlassian.jira.plugin.s... ]
Farah Juma resolved ELY-1098.
-----------------------------
Resolution: Won't Fix
Resolving this one as "Won't Fix" since the corresponding JBEAP issue was resolved with no XSD changes planned.
> WildFly Elytron Client Configuration File created based on elytron-1_0.xsd is not valid for clients
> ---------------------------------------------------------------------------------------------------
>
> Key: ELY-1098
> URL: https://issues.jboss.org/browse/ELY-1098
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta34
> Reporter: Ondrej Lukas
> Priority: Blocker
>
> There are some issues which causes that WildFly Elytron Client Configuration File created based on elytron-1_0.xsd is not valid for clients:
> * root element {{configuration}} is not included in elytron-1_0.xsd, it means that configuration with {{configuration}} are handled as invalid and configuration which has {{authentication-client}} as root element as valid
> * XSD elytron-1_0.xsd includes some elements on the highest level of XSD, which for example means that configuration file which includes only element {{<set-user-name name="someUser"/>}} is valid according to XSD.
> We request blocker because validated configuration file will not work correctly in clients. Moreover XSD is source of information which can be used by users for creating wildfly-config.xml correctly or validate their configuration file before using it. Mentioned issues can cause that this validation using elytron-1_0.xsd becomes unusable for users.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9342) managed-executor-service does not create more than core-threads
by Ravi Shankar Nori (JIRA)
Ravi Shankar Nori created WFLY-9342:
---------------------------------------
Summary: managed-executor-service does not create more than core-threads
Key: WFLY-9342
URL: https://issues.jboss.org/browse/WFLY-9342
Project: WildFly
Issue Type: Bug
Components: EE
Affects Versions: 11.0.0.CR1
Environment: Fedora 25
Reporter: Ravi Shankar Nori
<managed-executor-service
name="commandCoordinator"
jndi-name="java:jboss/ee/concurrency/executor/commandCoordinator"
core-threads="1"
max-threads="10"
queue-length="1000"
/>
Creates only one executable thread, does not create additional threads when new tasks are submitted.
Expected result: When new tasks are submitted more threads should be created capped by max-threads.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1242) External CS, create attribute is ignored
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-1242?page=com.atlassian.jira.plugin.s... ]
Farah Juma resolved ELY-1242.
-----------------------------
Resolution: Out of Date
Resolving this one since the corresponding JBEAP issue was resolved as out of date.
> External CS, create attribute is ignored
> ----------------------------------------
>
> Key: ELY-1242
> URL: https://issues.jboss.org/browse/ELY-1242
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Martin Choma
> Priority: Blocker
>
> {{location=secretdatafile}} have to exists, otherwise there occures NoSuchFileException
> {code}
> 09:13:34,368 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.security.credential-store.fips-credential-store: org.jboss.msc.service.StartException in service org.wildfly.security.credential-store.fips-credential-store: WFLYELY00004: Unable to start the service.
> at org.wildfly.extension.elytron.CredentialStoreService.start(CredentialStoreService.java:123)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> 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)
> Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09514: Unable to initialize credential store
> at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.setupExternalStorage(KeyStoreCredentialStore.java:945)
> at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.load(KeyStoreCredentialStore.java:821)
> at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.initialize(KeyStoreCredentialStore.java:213)
> at org.wildfly.security.credential.store.CredentialStore.initialize(CredentialStore.java:159)
> at org.wildfly.extension.elytron.CredentialStoreService.start(CredentialStoreService.java:117)
> ... 5 more
> Caused by: java.nio.file.NoSuchFileException: /home/mchoma/workspace/git-repositories/tests-security/fips/target/fips-cs-workdir/secure-data-file
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel(Files.java:361)
> at java.nio.file.Files.newByteChannel(Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream(Files.java:152)
> at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.setupExternalStorage(KeyStoreCredentialStore.java:936)
> ... 9 more
> 09:13:34,372 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("credential-store" => "fips-credential-store")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.credential-store.fips-credential-store" => "WFLYELY00004: Unable to start the service.
> Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09514: Unable to initialize credential store
> Caused by: java.nio.file.NoSuchFileException: /home/mchoma/workspace/git-repositories/tests-security/fips/target/fips-cs-workdir/secure-data-file"}}
> {code}
> There is missing branch in code when {{create = true}} and {{dataLocation != null}}
> {code}
> if (useExternalStorage) {
> dataLocation = externalPath;
> setupExternalStorage(type, location);
> } else {
> dataLocation = location;
> keyStore = getKeyStoreInstance(type);
> }
> if (create) {
> if (dataLocation == null) {
> try {
> keyStore.load(null, null);
> } catch (CertificateException | IOException | NoSuchAlgorithmException e) {
> throw log.cannotInitializeCredentialStore(e);
> }
> }
> }
> {code}
> This issue pops up in ER1, because file based external CS feature was delivered in ER1 (JBEAP-10803)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (LOGMGR-174) Filter expressions do not allow all types of regular expressions
by James Perkins (JIRA)
James Perkins created LOGMGR-174:
------------------------------------
Summary: Filter expressions do not allow all types of regular expressions
Key: LOGMGR-174
URL: https://issues.jboss.org/browse/LOGMGR-174
Project: JBoss Log Manager
Issue Type: Bug
Reporter: James Perkins
Some filter expressions require regex as an argument. The parsing of the regex does not allow for all expressions to be used. For example you can't use:
{code}
substituteAll("\\s", "replaced")
{code}
The pattern fails to be parsed. Using {{substituteAll("\s", "replaced")}} results in a pattern of {{s}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3273) sharedState is passed null by PluginAuthenticationCallbackHandler
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3273?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-3273:
------------------------------------------
I may see the bug, do you have the configuration for this realm available as well? I suspect you are seeing this when there is no authorization component?
We currently don't make the shared state available in that case as there is nothing to share state with but as existing plug-ins can experience a NPE we should ensure we always pass it in even if we know there is nothing to share.
> sharedState is passed null by PluginAuthenticationCallbackHandler
> -----------------------------------------------------------------
>
> Key: WFCORE-3273
> URL: https://issues.jboss.org/browse/WFCORE-3273
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Environment: Fedora 26, using ovirt-engine-wildfly package
> Reporter: Roy Golan
> Assignee: Darran Lofthouse
>
> oVirt's ovirt-engine uses an authorization plugin [1] for management interface that recently after upgrading to Wildfly 11 stopped working. The reason is the sharedState passed to the plugin's init method is now null.
> A current workaround this would be to avoid adding to plugin into the shareState but that means any delegating plugin would fail to find this plugin and possibly other bad stuff I'm not aware of.
> [1] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=backend/manag...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months