November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7038) License files issues

by Petr Sakař (JIRA)

[ https://issues.jboss.org/browse/WFLY-7038?page=com.atlassian.jira.plugin.... ] Petr Sakař reopened WFLY-7038: ------------------------------ Another issues reported by QE > License files issues > -------------------- > > Key: WFLY-7038 > URL: https://issues.jboss.org/browse/WFLY-7038 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 10.1.0.Final > Reporter: Petr Sakař > Assignee: Petr Sakař > Fix For: 11.0.0.Alpha1 > > > Various problems with licenses were found. > - bsd.txt file contains BSD license template > - some licenses are incorrect -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7465) JGroups channel operations using allow-resource-service-restart causes duplicate service exception

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7465: ---------------------------------- Summary: JGroups channel operations using allow-resource-service-restart causes duplicate service exception Key: WFLY-7465 URL: https://issues.jboss.org/browse/WFLY-7465 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7463) Infinispan cache-container operations using allow-resource-service-restart causes duplicate service exception

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7463: ---------------------------------- Summary: Infinispan cache-container operations using allow-resource-service-restart causes duplicate service exception Key: WFLY-7463 URL: https://issues.jboss.org/browse/WFLY-7463 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7464) Infinispan cache operations using allow-resource-service-restart causes duplicate service exception

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7464: ---------------------------------- Summary: Infinispan cache operations using allow-resource-service-restart causes duplicate service exception Key: WFLY-7464 URL: https://issues.jboss.org/browse/WFLY-7464 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1912) Redeploy deployment if all missing dependencies for deployment are corrected

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1912: ------------------------------------------ Can you file a separate JIRA for that, Deployment Scanner component? [~ehugonnet] can check it out. > Redeploy deployment if all missing dependencies for deployment are corrected > ----------------------------------------------------------------------------- > > Key: WFCORE-1912 > URL: https://issues.jboss.org/browse/WFCORE-1912 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Miroslav Novak > Assignee: Jason Greene > Labels: user_experience > > If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. This behavior could be configurable. > For example if you deploy EJB which injects queue like: > {code} > @Resource(mappedName = "java:/jms/queue/OutQueue") > private Queue outQueue; > {code} > and administrator deploys queue later then EJB would automatically get redeployed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7146) Elytron, regex-name-validating-rewriter - 'match' attribute required and unclear description

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7146?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned WFLY-7146: ----------------------------------- Assignee: Ilia Vassilev (was: Jan Kalina) > Elytron, regex-name-validating-rewriter - 'match' attribute required and unclear description > -------------------------------------------------------------------------------------------- > > Key: WFLY-7146 > URL: https://issues.jboss.org/browse/WFLY-7146 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Ilia Vassilev > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > Attribute 'match' is required when adding 'regex-name-validating-rewriter' although when reading the resource description via CLI, I can see that it has defined default value (true) and in [XSD file|https://github.com/wildfly-security/elytron-subsystem/blob/1.0.0.Alp...] it is not stated as a 'required'. Try: > {code} > /subsystem=elytron/regex-name-validating-rewriter=nameRewriter:add(pattern=".*") > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0172: match is required", > "rolled-back" => true > } > {code} > When you try to add also with 'match' attribute then rewriter is added successfully. > Also - the 'match' attribute description in CLI is not quite clear: > {code} > /subsystem=elytron/regex-name-validating-rewriter=nameRewriter:read-resource-description > ... > "match" => { > "type" => BOOLEAN, > "description" => "Should names that match the pattern be rejected or names that don't", > "expressions-allowed" => true, > "nillable" => false, > "default" => true, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > ... > {code} > After reading the description I still don't know what happens when pattern matches the name and value of 'match' attribute is set to 'true' - will it be rejected or not? > Expected behaviour: > # 'match' attribute to be arbitrary (or change XSD so it is in sync with model) > # more clear description of 'match' attribute -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7146) Elytron, regex-name-validating-rewriter - 'match' attribute required and unclear description

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7146?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reopened WFLY-7146: --------------------------------- > Elytron, regex-name-validating-rewriter - 'match' attribute required and unclear description > -------------------------------------------------------------------------------------------- > > Key: WFLY-7146 > URL: https://issues.jboss.org/browse/WFLY-7146 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Ilia Vassilev > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > Attribute 'match' is required when adding 'regex-name-validating-rewriter' although when reading the resource description via CLI, I can see that it has defined default value (true) and in [XSD file|https://github.com/wildfly-security/elytron-subsystem/blob/1.0.0.Alp...] it is not stated as a 'required'. Try: > {code} > /subsystem=elytron/regex-name-validating-rewriter=nameRewriter:add(pattern=".*") > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0172: match is required", > "rolled-back" => true > } > {code} > When you try to add also with 'match' attribute then rewriter is added successfully. > Also - the 'match' attribute description in CLI is not quite clear: > {code} > /subsystem=elytron/regex-name-validating-rewriter=nameRewriter:read-resource-description > ... > "match" => { > "type" => BOOLEAN, > "description" => "Should names that match the pattern be rejected or names that don't", > "expressions-allowed" => true, > "nillable" => false, > "default" => true, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > ... > {code} > After reading the description I still don't know what happens when pattern matches the name and value of 'match' attribute is set to 'true' - will it be rejected or not? > Expected behaviour: > # 'match' attribute to be arbitrary (or change XSD so it is in sync with model) > # more clear description of 'match' attribute -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-719) Support custom nonce handling strategies

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-719: ------------------------------------ Summary: Support custom nonce handling strategies Key: ELY-719 URL: https://issues.jboss.org/browse/ELY-719 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI, HTTP Reporter: Darran Lofthouse Fix For: 2.0.0.Alpha1 Realistically we are not going to expose this as SPI in the 1.1.x releases and current implementations are private so we visit exposing a custom SPI at a later point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-716) Password Transformations

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-716?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-716: ------------------------------------ Assignee: (was: David Lloyd) > Password Transformations > ------------------------ > > Key: ELY-716 > URL: https://issues.jboss.org/browse/ELY-716 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > There may be reasons that still make this impossible so some research will be required first. > However take mechanisms like Digest SASL: - > https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/... > Here the mechanism queries different password types and converts as needed. > Instead the mechanism should be able to query the most specific time and a set of registered transformers kick in to convert between the different types. > The credential support methods should also take into account transformations that the transformers can perform. > The one thing however that may make this impossible is if the specific form of a credential needs additional information e.g. the mechanism could support arbitrary realms and use it to create the digested form. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1927) There is inconsistency in Elyton mapped-regex-realm-mapper model between DMR and XSD.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1927?page=com.atlassian.jira.plugi... ] Hynek Švábek closed WFCORE-1927. -------------------------------- Resolution: Rejected > There is inconsistency in Elyton mapped-regex-realm-mapper model between DMR and XSD. > ------------------------------------------------------------------------------------- > > Key: WFCORE-1927 > URL: https://issues.jboss.org/browse/WFCORE-1927 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > There is inconsistency in Elyton mapped-regex-realm-mapper model between DMR and XSD. > There is mappedRegexRealmMapperType with "realm-mapping" element in XSD [1] but > in DMR is "realm-map" attribute. > Base on this are wrong information in XSD about "from", "to" attributes > These inconsistencies should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/580569d17cb6c3... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016