[JBoss JIRA] (WFLY-6263) Apostrophe in an attribute with multiple EL parts breaks function lookup
by Helmut Seruega (JIRA)
[ https://issues.jboss.org/browse/WFLY-6263?page=com.atlassian.jira.plugin.... ]
Helmut Seruega commented on WFLY-6263:
--------------------------------------
same problem here with WildFly 10.1.0.Final
> Apostrophe in an attribute with multiple EL parts breaks function lookup
> ------------------------------------------------------------------------
>
> Key: WFLY-6263
> URL: https://issues.jboss.org/browse/WFLY-6263
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.Final
> Reporter: Paul Pogonyshev
> Assignee: Jason Greene
> Priority: Critical
> Attachments: jastow-bug.war.zip, jastow.diff
>
>
> Certain EL pieces result in unexplained org.apache.jasper.JasperException "contains invalid expression(s)" (the exception _does not_ explain what is invalid). After lots of tries, I have narrowed it down: 1) there must be several EL pieces in one string; 2) there must be an apostrophe in between.
> This looks very similar to bug WFLY-4455. It breaks several pages in our application, blocking upgrade to WildFly 10.
> Example is attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7218) Unable to setup CLIENT_CERT authentication with elytron.
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7218?page=com.atlassian.jira.plugin.... ]
Martin Choma moved JBEAP-6206 to WFLY-7218:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7218 (was: JBEAP-6206)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR5)
> Unable to setup CLIENT_CERT authentication with elytron.
> --------------------------------------------------------
>
> Key: WFLY-7218
> URL: https://issues.jboss.org/browse/WFLY-7218
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> Following Zach's notes on [How to setup 2 way TLS|https://gitlab.cee.redhat.com/zrhoads/kbase/blob/master/eap71.elytron...] I am unable to setup it properly. User is not requested by browser for specifying client certificate and get access to application without certificate.
> In log you there is:
> 1. Server send request for certificate
> {code}
> ^[[0m^[[0m13:55:33,309 INFO [stdout] (default task-1) *** CertificateRequest
> ^[[0m^[[0m13:55:33,309 INFO [stdout] (default task-1) Cert Types: RSA, DSS, ECDSA
> ^[[0m^[[0m13:55:33,309 INFO [stdout] (default task-1) Cert Authorities:
> ^[[0m^[[0m13:55:33,310 INFO [stdout] (default task-1) <CN=client>
> {code}
> 2. And client responds with empty certificate chain. Without asking for certificate
> {code}
> ^[[0m^[[0m13:55:33,432 INFO [stdout] (default task-2) *** Certificate chain
> ^[[0m^[[0m13:55:33,432 INFO [stdout] (default task-2) <Empty>
> ^[[0m^[[0m13:55:33,432 INFO [stdout] (default task-2) ***
> {code}
> I am attaching:
> * server.log - server log with -Djavax.net.debug=all turn on.
> * 2wayTLS.pcap - wireshark recording of port 8443
> * secured-app - tested application
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ELY-631) Wrong description of missing target-name in simple-permission-mapper
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-631?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina edited comment on ELY-631 at 9/26/16 8:35 AM:
---------------------------------------------------------
The problem is:
* Subsystem does not know if Permission should have a name (depends on class name)
* The Permission doesnt know anything about subsystem attributes (like target-name)
Ideas:
* Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) ?
was (Author: honza889):
The error message mean parameter *name* of *AbstractNamedPermission*.
The problem is:
* Subsystem does not know if Permission should have a name (depends on class name)
* The Permission doesnt know anything about subsystem attributes (like target-name)
Ideas:
* Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) ?
> Wrong description of missing target-name in simple-permission-mapper
> --------------------------------------------------------------------
>
> Key: ELY-631
> URL: https://issues.jboss.org/browse/ELY-631
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta9
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
>
> In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ELY-631) Wrong description of missing target-name in simple-permission-mapper
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-631?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina edited comment on ELY-631 at 9/26/16 8:32 AM:
---------------------------------------------------------
The error message mean parameter *name* of *AbstractNamedPermission*.
The problem is:
* Subsystem does not know if Permission should have a name (depends on class name)
* The Permission doesnt know anything about subsystem attributes (like target-name)
Ideas:
* Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) ?
was (Author: honza889):
The error message mean parameter *name* of *AbstractNamedPermission*.
The problem is:
* Subsystem does not know if Permission should have a name (depends on class name)
* The Permission doesnt know anything about subsystem attributes
Ideas:
* Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) ?
> Wrong description of missing target-name in simple-permission-mapper
> --------------------------------------------------------------------
>
> Key: ELY-631
> URL: https://issues.jboss.org/browse/ELY-631
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta9
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
>
> In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ELY-631) Wrong description of missing target-name in simple-permission-mapper
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-631?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina edited comment on ELY-631 at 9/26/16 8:31 AM:
---------------------------------------------------------
The error message mean parameter *name* of *AbstractNamedPermission*.
The problem is:
* Subsystem does not know if Permission should have a name (depends on class name)
* The Permission doesnt know anything about subsystem attributes
Ideas:
* Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) ?
was (Author: honza889):
Note: The error message mean parameter *name* of *AbstractNamedPermission*.
> Wrong description of missing target-name in simple-permission-mapper
> --------------------------------------------------------------------
>
> Key: ELY-631
> URL: https://issues.jboss.org/browse/ELY-631
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta9
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
>
> In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFCORE-1824) Can not parse object attributes that contains a Properties attribute
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFCORE-1824:
-----------------------------------
Summary: Can not parse object attributes that contains a Properties attribute
Key: WFCORE-1824
URL: https://issues.jboss.org/browse/WFCORE-1824
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha8
Reporter: Jeff Mesnil
Assignee: Brian Stansberry
My resource defines an attribute which is a LIST of OBJECT that corresponds to a class (class name + module) and Properties that are passed to the created instance:
{noformat}
private static final String CLASS = "class";
private static final String MODULE = "module";
public static final PropertiesAttributeDefinition PROPERTIES = new PropertiesAttributeDefinition.Builder("properties", true)
.setAllowExpression(true)
.build();
public static final ObjectTypeAttributeDefinition PROCESS_STATE_LISTENER = ObjectTypeAttributeDefinition.Builder.of("process-state-listener",
SimpleAttributeDefinitionBuilder.create(CLASS, ModelType.STRING, false)
.setAllowExpression(false)
.build(),
SimpleAttributeDefinitionBuilder.create(MODULE, ModelType.STRING, false)
.setAllowExpression(false)
.build(),
PROPERTIES)
.setRestartAllServices()
.setAllowNull(true)
.build();
public static final AttributeDefinition PROCESS_STATE_LISTENERS = ObjectListAttributeDefinition.Builder.of("listeners", PROCESS_STATE_LISTENER)
.setAllowNull(false)
.setRuntimeServiceNotRequired()
.build();
{noformat}
I can create the resource from the CLI:
{noformat}
/subsystem=core-management/service=process-state-listeners:add(listeners=[{class=org.foo.Listener, module=org.foo,, properties = {foo = true, bar = ${bar.prop:2}}}])
{"outcome" => "success"}
{noformat}
And the resource and its attribute is properly marshalled to the XML configuration:
{noformat}
<process-state-listeners>
<listeners>
<process-state-listener class="org.foo.Listener" module="org.foo">
<properties>
<property name="foo" value="true"/>
<property name="bar" value="${bar.prop:2}"/>
</properties>
</process-state-listener>
</listeners>
</process-state-listeners>
{noformat}
However the resource can not be parsed and it fails with the exception:
{noformat}
boss.as.server.parsing.StandaloneXml_5.readElement(StandaloneXml_5.java:144)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
... 3 more
09:45:00,537 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.{noformat}
The code in org.jboss.as.controller.AttributeParser#parseElement:197 to parse a list of objects assumes that the object's value are all represented by XML attributes. In my case, that's not correct as the "properties" attribute is represented by XML elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ELY-631) Wrong description of missing target-name in simple-permission-mapper
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-631?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina edited comment on ELY-631 at 9/26/16 8:23 AM:
---------------------------------------------------------
Note: The error message mean parameter *name* of *AbstractNamedPermission*.
was (Author: honza889):
Note: The error message mean parameter *name* of *AbstractNameOnlyPermission*.
> Wrong description of missing target-name in simple-permission-mapper
> --------------------------------------------------------------------
>
> Key: ELY-631
> URL: https://issues.jboss.org/browse/ELY-631
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta9
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
>
> In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7203) Elytron - inconsistency between DMR and XSD representation of regex-name-validating-rewriter
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7203?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7203:
----------------------------------
Match should be optional - it has default value. (in both - XSD and in model)
> Elytron - inconsistency between DMR and XSD representation of regex-name-validating-rewriter
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-7203
> URL: https://issues.jboss.org/browse/WFLY-7203
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Jan Tymel
> Assignee: Darran Lofthouse
> Priority: Optional
>
> There is an inconsistency between DMR and XSD representation of {{regex-name-validating-rewriter}}.
> According to XSD[1] is {{match}} attribute optional. On the other hand DMR[2] says that {{match}} attribute is mandatory (_"nillable" => false_).
> {{Match}} attribute is currently required if user adds a new regex-name-validating-rewriter. Is it an intentional behaviour or should {{match}} be optional (=according to XSD definition)?
> [1] https://github.com/wildfly-security/elytron-subsystem/blob/master/src/mai...
> [2] {{/subsystem=elytron:read-resource-description(recursive=true)}}
> {code}
> "regex-name-validating-rewriter" => {
> "description" => "A regular expression based Name Rewriter which uses the regular expression to validate the name.",
> "model-description" => {"*" => {
> "description" => "A regular expression based Name Rewriter which uses the regular expression to validate the name.",
> "capabilities" => [{
> "name" => "org.wildfly.security.name-rewriter",
> "dynamic" => true
> }],
> "attributes" => {
> "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"
> },
> "pattern" => {
> "type" => STRING,
> "description" => "The regular expression to use to locate the portion of the name to be replaced.",
> "expressions-allowed" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {}
> }}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months