[JBoss JIRA] (WFCORE-2566) Subsystem parsing tests ignores wrong END_ELEMENT
by Jan Kalina (JIRA)
Jan Kalina created WFCORE-2566:
----------------------------------
Summary: Subsystem parsing tests ignores wrong END_ELEMENT
Key: WFCORE-2566
URL: https://issues.jboss.org/browse/WFCORE-2566
Project: WildFly Core
Issue Type: Bug
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Minor
Tests based on *AbstractSubsystemBaseTest* ignores bugs like excessive {code}requireNoContent(reader);{code}
Tests will fail only if some next element follows - its parsing fails in such case correctly.
Would be better to add same check in the end of *<test>* parsing, which would check not only there is END_ELEMENT, but also that its name really equals *test*.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-647) MechanismDatabase create SSL_ aliases incompletely
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-647?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-647:
---------------------------------
Fix Version/s: 1.0.4.CR1
1.1.0.Beta10
> MechanismDatabase create SSL_ aliases incompletely
> --------------------------------------------------
>
> Key: ELY-647
> URL: https://issues.jboss.org/browse/ELY-647
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
> Fix For: 1.1.0.Beta10, 1.0.4.CR1
>
>
> SSL MechanismDatabase should create alias for every TLS_* from SSL_*. It create them only for direct entries, not for other aliases.
> MechanismDatabase.properties contains for example:
> {code:java}
> TLS_RSA_FIPS_WITH_3DES_EDE_CBC_SHA = alias:TLS_RSA_WITH_3DES_EDE_CBC_SHA
> {code}
> The *TLS_RSA_FIPS_WITH_3DES_EDE_CBC_SHA* works ok, but *SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA* doesnt exist.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2565) Incorrect permission class-name should throw exception at runtime
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFCORE-2565:
------------------------------------
Summary: Incorrect permission class-name should throw exception at runtime
Key: WFCORE-2565
URL: https://issues.jboss.org/browse/WFCORE-2565
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
In case when some permission mapper (tried with constant-permission-mapper and simple-permission-mapper) includes permission with non-existent class-name then it seems that no exception is thrown during runtime.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2565) Incorrect permission class-name should throw exception at runtime
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2565?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2565:
---------------------------------
Steps to Reproduce:
Add non-existent permission into default-permission-mapper:
{code}
/subsystem=elytron/constant-permission-mapper=default-permission-mapper:write-attribute(name=permissions[4],value={class-name=WrongName})
{code}
and use this mapper at runtime. No exception is thrown.
was:
Add non-existent permission into default {default-permission-mapper}:
{code}
/subsystem=elytron/constant-permission-mapper=default-permission-mapper:write-attribute(name=permissions[4],value={class-name=WrongName})
{code}
and use this mapper at runtime. No exception is thrown.
> Incorrect permission class-name should throw exception at runtime
> -----------------------------------------------------------------
>
> Key: WFCORE-2565
> URL: https://issues.jboss.org/browse/WFCORE-2565
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
>
> In case when some permission mapper (tried with constant-permission-mapper and simple-permission-mapper) includes permission with non-existent class-name then it seems that no exception is thrown during runtime.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2564) Customize resolve-path handle to handle absolute paths
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFCORE-2564:
-----------------------------------
Summary: Customize resolve-path handle to handle absolute paths
Key: WFCORE-2564
URL: https://issues.jboss.org/browse/WFCORE-2564
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Beta9
Reporter: Jeff Mesnil
Assignee: Brian Stansberry
The :resolve-path operation will always resolve the path based on the relative-to attribute.
In the messaging subsystem, we have a different behaviour where the relative-to attribute is *ignored* (whether it is defined or not) when the path value correponds to an absolute path.
To be consistent with this behaviour, the :resolve-path operation builder would need customization and specify that the relative-to attribute must be ignored when the path is absolute.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month