January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-899) Hash functions for MatchRule & AuthenticationConfiguration are not unordered

by David Lloyd (JIRA)

David Lloyd created ELY-899: ------------------------------- Summary: Hash functions for MatchRule & AuthenticationConfiguration are not unordered Key: ELY-899 URL: https://issues.jboss.org/browse/ELY-899 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: David Lloyd Assignee: David Lloyd Priority: Critical -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

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

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7984?page=com.atlassian.jira.plugin.... ] Hynek Švábek reassigned WFLY-7984: ---------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > Credential Store alias name in camel case leads to AssertionError. > ------------------------------------------------------------------ > > Key: WFLY-7984 > URL: https://issues.jboss.org/browse/WFLY-7984 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > 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)

9 years, 3 months

1
0
0 / 0

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

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-7984: ---------------------------------- Summary: Credential Store alias name in camel case leads to AssertionError. Key: WFLY-7984 URL: https://issues.jboss.org/browse/WFLY-7984 Project: WildFly Issue Type: Bug Components: Security Reporter: Hynek Švábek Assignee: Darran Lofthouse 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)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7983) Credential store file isn't created when we add there new entry in embed-server mode.

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-7983: ---------------------------------- Summary: Credential store file isn't created when we add there new entry in embed-server mode. Key: WFLY-7983 URL: https://issues.jboss.org/browse/WFLY-7983 Project: WildFly Issue Type: Bug Components: Security Reporter: Hynek Švábek Assignee: Darran Lofthouse Credential store file isn't created when we add there new entry in embed-server mode. * ./bin/jboss-cli.sh * embed-server * /subsystem=elytron/credential-store=store001:add(uri="cr-store://test/store001.jceks?create.storage=true", credential-reference={clear-text=pass123}) * /subsystem=elytron/credential-store=store001/alias=alias001:add(secret-value=secretValue) store001.jceks file should be created in JBOSS_HOME directory, but it doesn't. When I stop embedded server and start standalone server everything work fine. * stop-embedded-server * ./bin/standalone.sh * connect * /subsystem=elytron/credential-store=store001/alias=alias001:add(secret-value=secretValue) store001.jceks file is correctly created in JBOSS_HOME directory. *NOTE:* When I copy there store001.jceks file to JBOSS_HOME directory with same password to access as expected then entry is added correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7973) WildFlyDataSource needs implementation of isWrapperFor method

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-7973?page=com.atlassian.jira.plugin.... ] Stefano Maestri resolved WFLY-7973. ----------------------------------- Resolution: Won't Fix See [~istudens] 's comments > WildFlyDataSource needs implementation of isWrapperFor method > ------------------------------------------------------------- > > Key: WFLY-7973 > URL: https://issues.jboss.org/browse/WFLY-7973 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.1.0.Final > Reporter: Johnathon Lee > Assignee: Flavia Rainone > > inability to determine datasource vs xa-datasource after JNDI lookup. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1419) Make interface AccumulateFunction<S extends Serializable> to avoid downcasting verbosity in implementations

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-1419: ---------------------------------------- Summary: Make interface AccumulateFunction<S extends Serializable> to avoid downcasting verbosity in implementations Key: DROOLS-1419 URL: https://issues.jboss.org/browse/DROOLS-1419 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 6.5.0.Final Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: 7.0.0.CR1 Fix will NOT break backwards compatibility. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7970) Elytron keystore type default value

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7970?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned WFLY-7970: ----------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Elytron keystore type default value > ----------------------------------- > > Key: WFLY-7970 > URL: https://issues.jboss.org/browse/WFLY-7970 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Ilia Vassilev > > Make attribute type optional during key-store creation. If not set default value "JKS" can be used. > Basically in this issue is requesting same behaviour as legacy keystore in realms > {code:jsonl|title=ManagementModel} > "keystore-provider" => { > "type" => STRING, > "description" => "The provider for loading the keystore, defaults to JKS.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "JKS", > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > Extracted from WFLY-7125 and tracked as separate issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7977) Synchronize XSD and DMR description of obtain-kerberos-ticket attribute

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7977?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned WFLY-7977: ----------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Synchronize XSD and DMR description of obtain-kerberos-ticket attribute > ----------------------------------------------------------------------- > > Key: WFLY-7977 > URL: https://issues.jboss.org/browse/WFLY-7977 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Labels: user_experience > > Add this sentence "This is required to be true where credentials are delegated to the server." to description of obtain-kerberos-ticket attribute. > {code:Management Model} > "obtain-kerberos-ticket" => { > "type" => BOOLEAN, > "description" => "Should the KerberosTicket also be obtained and associated with the credential.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > As already is in XSD > {code:xml|title=wildfly-elytron.xsd} > <xs:attribute name="obtain-kerberos-ticket" type="xs:boolean" default="false"> > <xs:annotation> > <xs:documentation> > Should the KerberosTicket also be obtained and associated with the credential. > This is required to be true where credentials are delegated to the server. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-898) credential-reference not able to use masked passwords

by Hynek Švábek (JIRA)

Hynek Švábek created ELY-898: -------------------------------- Summary: credential-reference not able to use masked passwords Key: ELY-898 URL: https://issues.jboss.org/browse/ELY-898 Project: WildFly Elytron Issue Type: Bug Components: Credential Store Reporter: Hynek Švábek Assignee: Peter Skopek credential-reference cannot use PBE encrypted credentials AKA masked passwords (MASK-). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1987) Create request/response reporting mechanism

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1987?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFCORE-1987: -------------------------------------------- Simple test I've done with this was in "finishModelStage" of write attribute. For domain mode, if profile is active, I can see messages coming back, when attribute change. However when inactive profile is being edited nothing happens. When I alter server group profile, I get only response to that particular OP. WRT to include - it is kind of irrelevant, at least in this simple test. If parameter change, warning is sent in response, to check other parameters. If other profile has it set to proper value, no harm, if not, user knows what to do. This might not be the best way, but it is like that now. Might be something to improve on. Im trying to figure out how inactive profile are being handled. Is it relevant to report on those? > Create request/response reporting mechanism > ------------------------------------------- > > Key: WFCORE-1987 > URL: https://issues.jboss.org/browse/WFCORE-1987 > Project: WildFly Core > Issue Type: Enhancement > Components: Remoting > Reporter: Radim Hatlapatka > Assignee: Bartosz Baranowski > Labels: downstream_dependency > > In certain cases it is useful to send back, to client, some sort of context information about the outcome of operation. For instance, when change in configuration warrants another one and without it, after reload/restart server could not operate properly. For instance JBEAP-7284. > Scope of this enhancement are: > a) way to send back information > b) control level of "information" - just like in case of loggers > a) Information will be sent in response headers, under "warnings" key. Each entry, "warning" will contain operation, address, level/severity and i18n string with proper ID. > b) default level threshold would be "WARNING", if user requires more detailed information, he can request it via operation-headers->warninig-level > Example: > {noformat} > { > "outcome" => "success", > "response-headers" => { > "warnings" => [ > { > "warning" => "WFLYCTL0436: Couldn't convert 'XXX' into proper warning level, threshold falling back to 'ALL'. Possible values: SEVERE,WARNING,INFO,CONFIG,FINE,FINER,FINEST", > "level" => "ALL", > "operation" => { > "address" => [ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("http-listener" => "default") > ], > "operation" => "write-attribute" > } > }, > { > "warning" => "WFLYUT0090: Worker used in http-listener: 'puppet-master', must be used in remoting subsystem.", > "level" => "WARNING", > "operation" => { > "address" => [ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("http-listener" => "default") > ], > "operation" => "write-attribute" > } > } > ], > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017