[
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)