[JBoss JIRA] (WFLY-7477) Elytron dir-context not updatable
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7477?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFLY-7477:
-------------------------------
Labels: (was: user_experience)
> Elytron dir-context not updatable
> ---------------------------------
>
> Key: WFLY-7477
> URL: https://issues.jboss.org/browse/WFLY-7477
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
>
> All attributes of {{dir-context}} resource are read-only.
> Attempt to update:
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/dir-context=dc:write-attribute(name=url, value=ldap://localhost:10389)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0048: Attribute url is not writable",
> "rolled-back" => true
> }
> {code}
> Model description:
> {code}
> "url" => {
> "type" => STRING,
> "description" => "The connection url.",
> "expressions-allowed" => true,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-only",
> "storage" => "configuration"
> }
> {code}
> Make {{dir-context}} updatable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7477) Elytron dir-context not updatable
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7477?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFLY-7477:
-------------------------------
Labels: user_experience (was: )
> Elytron dir-context not updatable
> ---------------------------------
>
> Key: WFLY-7477
> URL: https://issues.jboss.org/browse/WFLY-7477
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Labels: user_experience
>
> All attributes of {{dir-context}} resource are read-only.
> Attempt to update:
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/dir-context=dc:write-attribute(name=url, value=ldap://localhost:10389)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0048: Attribute url is not writable",
> "rolled-back" => true
> }
> {code}
> Model description:
> {code}
> "url" => {
> "type" => STRING,
> "description" => "The connection url.",
> "expressions-allowed" => true,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-only",
> "storage" => "configuration"
> }
> {code}
> Make {{dir-context}} updatable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7477) Elytron dir-context not updatable
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7477?page=com.atlassian.jira.plugin.... ]
Martin Choma moved JBEAP-6891 to WFLY-7477:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7477 (was: JBEAP-6891)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
(was: User Experience)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR7)
> Elytron dir-context not updatable
> ---------------------------------
>
> Key: WFLY-7477
> URL: https://issues.jboss.org/browse/WFLY-7477
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
>
> All attributes of {{dir-context}} resource are read-only.
> Attempt to update:
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/dir-context=dc:write-attribute(name=url, value=ldap://localhost:10389)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0048: Attribute url is not writable",
> "rolled-back" => true
> }
> {code}
> Model description:
> {code}
> "url" => {
> "type" => STRING,
> "description" => "The connection url.",
> "expressions-allowed" => true,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-only",
> "storage" => "configuration"
> }
> {code}
> Make {{dir-context}} updatable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7476) Complicated failure-descriptions in Elytron properties-realm
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7476?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7476:
-------------------------------
Affects Version/s: 11.0.0.Alpha1
> Complicated failure-descriptions in Elytron properties-realm
> ------------------------------------------------------------
>
> Key: WFLY-7476
> URL: https://issues.jboss.org/browse/WFLY-7476
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Labels: user_experience
>
> There are complicated failure-descriptions in Elytron properties-realm. They include some details from exceptions which are not needed and can be confused for non-java administrators. Please handle these exceptions and provide some user friendly failure-description.
> Examples of complicated failure-description in properties-realm:
> * Adding path which does not exist:
> {code}
> /subsystem=elytron/properties-realm=realm:add(users-properties={path=/wrong/path/a.properties})
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.security-realm.realm" => "org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.realm: WFLYELY00014: Unable to load the properties files required to start the properties file backed realm.
> Caused by: java.io.FileNotFoundException: /wrong/path/a.properties (No such file or directory)"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.realm"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> * Adding file with missing $REALM:
> {code}
> /subsystem=elytron/properties-realm=realm:add(users-properties={path=/some/path/roles.properties})
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.security-realm.realm" => "org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.realm: WFLYELY00014: Unable to load the properties files required to start the properties file backed realm.
> Caused by: java.io.IOException: ELY01006: No realm name found in properties file"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.realm"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> * path mentiond in relative-to does not exist:
> {code}
> /subsystem=elytron/properties-realm=realm:add(users-properties={path=users.properties,relative-to=non.exist})
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.realm is missing [jboss.server.path.\"non.exist\"]"]
> },
> "rolled-back" => true
> }
> {code}
> Suggestion for improvement:
> * use only description of failure, e.g. something like "file /wrong/path/a.properties was not found"
> * do not use any unneeded information - e.g. "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7476) Complicated failure-descriptions in Elytron properties-realm
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-7476:
----------------------------------
Summary: Complicated failure-descriptions in Elytron properties-realm
Key: WFLY-7476
URL: https://issues.jboss.org/browse/WFLY-7476
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
There are complicated failure-descriptions in Elytron properties-realm. They include some details from exceptions which are not needed and can be confused for non-java administrators. Please handle these exceptions and provide some user friendly failure-description.
Examples of complicated failure-description in properties-realm:
* Adding path which does not exist:
{code}
/subsystem=elytron/properties-realm=realm:add(users-properties={path=/wrong/path/a.properties})
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.security-realm.realm" => "org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.realm: WFLYELY00014: Unable to load the properties files required to start the properties file backed realm.
Caused by: java.io.FileNotFoundException: /wrong/path/a.properties (No such file or directory)"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.realm"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
* Adding file with missing $REALM:
{code}
/subsystem=elytron/properties-realm=realm:add(users-properties={path=/some/path/roles.properties})
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.security-realm.realm" => "org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.realm: WFLYELY00014: Unable to load the properties files required to start the properties file backed realm.
Caused by: java.io.IOException: ELY01006: No realm name found in properties file"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.realm"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
* path mentiond in relative-to does not exist:
{code}
/subsystem=elytron/properties-realm=realm:add(users-properties={path=users.properties,relative-to=non.exist})
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist\""],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.realm is missing [jboss.server.path.\"non.exist\"]"]
},
"rolled-back" => true
}
{code}
Suggestion for improvement:
* use only description of failure, e.g. something like "file /wrong/path/a.properties was not found"
* do not use any unneeded information - e.g. "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7476) Complicated failure-descriptions in Elytron properties-realm
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7476?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7476:
-------------------------------
Labels: user_experience (was: )
> Complicated failure-descriptions in Elytron properties-realm
> ------------------------------------------------------------
>
> Key: WFLY-7476
> URL: https://issues.jboss.org/browse/WFLY-7476
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Labels: user_experience
>
> There are complicated failure-descriptions in Elytron properties-realm. They include some details from exceptions which are not needed and can be confused for non-java administrators. Please handle these exceptions and provide some user friendly failure-description.
> Examples of complicated failure-description in properties-realm:
> * Adding path which does not exist:
> {code}
> /subsystem=elytron/properties-realm=realm:add(users-properties={path=/wrong/path/a.properties})
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.security-realm.realm" => "org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.realm: WFLYELY00014: Unable to load the properties files required to start the properties file backed realm.
> Caused by: java.io.FileNotFoundException: /wrong/path/a.properties (No such file or directory)"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.realm"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> * Adding file with missing $REALM:
> {code}
> /subsystem=elytron/properties-realm=realm:add(users-properties={path=/some/path/roles.properties})
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.security-realm.realm" => "org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.realm: WFLYELY00014: Unable to load the properties files required to start the properties file backed realm.
> Caused by: java.io.IOException: ELY01006: No realm name found in properties file"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.realm"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> * path mentiond in relative-to does not exist:
> {code}
> /subsystem=elytron/properties-realm=realm:add(users-properties={path=users.properties,relative-to=non.exist})
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.realm is missing [jboss.server.path.\"non.exist\"]"]
> },
> "rolled-back" => true
> }
> {code}
> Suggestion for improvement:
> * use only description of failure, e.g. something like "file /wrong/path/a.properties was not found"
> * do not use any unneeded information - e.g. "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1935) Add :read-attribute-description operation
by Pavel Jelinek (JIRA)
Pavel Jelinek created WFCORE-1935:
-------------------------------------
Summary: Add :read-attribute-description operation
Key: WFCORE-1935
URL: https://issues.jboss.org/browse/WFCORE-1935
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Pavel Jelinek
Assignee: Brian Stansberry
In resource with many attributes which may or may not be ordered in _:read-resource-description_ operation result it's very hard to find description of a particular attribute.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (ELY-720) Definition Credential Store with non-existent storage file causes ugly failure-description with Exception.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-720:
--------------------------------
Summary: Definition Credential Store with non-existent storage file causes ugly failure-description with Exception.
Key: ELY-720
URL: https://issues.jboss.org/browse/ELY-720
Project: WildFly Elytron
Issue Type: Bug
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Definition Credential Store with non-existent storage file causes ugly failure-description with Exception.
When I define Credential
Store for non-existent JCEKS file
{code}
/subsystem=elytron/credential-store=cs_not_found_exception:add(uri="cr-store://test/cs/keystore-non-existent.jceks?store.password=pass123")
{code}
then I got very ugly failure description
{code}
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.credential-store-client.cs_not_found_exception" => "org.jboss.msc.service.StartException in service org.wildfly.security.credential-store-client.cs_not_found_exception: WFLYELY00004: Unable to start the service.
Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09506: Cannot read credential storage file '/home/hsvabek/securityworkspace/VERIFICATION/2016_11_02_UX_testing/jboss-eap-7.1.0.DR7/standalone/data/cs/keystore-not_exists.jceks' for the store named 'cs_not_found_exception'
Caused by: java.io.FileNotFoundException: /home/hsvabek/securityworkspace/VERIFICATION/2016_11_02_UX_testing/jboss-eap-7.1.0.DR7/standalone/data/cs/keystore-not_exists.jceks (No such file or directory)"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.credential-store-client.cs_not_found_exception"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
*Suggestion for solution*
failure-description must not contain Exception or snippet stacktrace.
Description like that "Credential store file XYZ doesn't exist.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (ELY-720) Definition Credential Store with non-existent storage file causes ugly failure-description with Exception.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-720?page=com.atlassian.jira.plugin.sy... ]
Hynek Švábek reassigned ELY-720:
--------------------------------
Assignee: Peter Skopek (was: Darran Lofthouse)
> Definition Credential Store with non-existent storage file causes ugly failure-description with Exception.
> ----------------------------------------------------------------------------------------------------------
>
> Key: ELY-720
> URL: https://issues.jboss.org/browse/ELY-720
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
>
> Definition Credential Store with non-existent storage file causes ugly failure-description with Exception.
> When I define Credential
> Store for non-existent JCEKS file
> {code}
> /subsystem=elytron/credential-store=cs_not_found_exception:add(uri="cr-store://test/cs/keystore-non-existent.jceks?store.password=pass123")
> {code}
> then I got very ugly failure description
> {code}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.credential-store-client.cs_not_found_exception" => "org.jboss.msc.service.StartException in service org.wildfly.security.credential-store-client.cs_not_found_exception: WFLYELY00004: Unable to start the service.
> Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09506: Cannot read credential storage file '/home/hsvabek/securityworkspace/VERIFICATION/2016_11_02_UX_testing/jboss-eap-7.1.0.DR7/standalone/data/cs/keystore-not_exists.jceks' for the store named 'cs_not_found_exception'
> Caused by: java.io.FileNotFoundException: /home/hsvabek/securityworkspace/VERIFICATION/2016_11_02_UX_testing/jboss-eap-7.1.0.DR7/standalone/data/cs/keystore-not_exists.jceks (No such file or directory)"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.credential-store-client.cs_not_found_exception"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> *Suggestion for solution*
> failure-description must not contain Exception or snippet stacktrace.
> Description like that "Credential store file XYZ doesn't exist.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7475) Complicated failure-descriptions in Elytron simple-permission-mapper
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7475?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7475:
-------------------------------
Description:
There are complicated failure-descriptions in Elytron simple-permission-mapper. They include some details from exceptions which are not needed and can be confused for non-java administrators. Please handle these exceptions and provide some user friendly failure-description.
Examples of complicated failure-description in simple-permission-mapper:
* Wrong name of permission class:
{code}
/subsystem=elytron/simple-permission-mapper=mapper:add(permission-mappings=[{permissions=[{action=read,class-name=org.wildfly.security.auth.permission.WrongLoginPermission,target-name=someName}]}])
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.permission-mapper.mapper" => "org.jboss.msc.service.StartException in service org.wildfly.security.permission-mapper.mapper: WFLYELY00021: Exception while creating the permission object for the permission mapping. Please check [class-name], [target-name] (name of permission) and [action] of [org.wildfly.security.auth.permission.WrongLoginPermission].
Caused by: org.wildfly.security.permission.InvalidPermissionClassException: ELY03015: Could not load permission class \"org.wildfly.security.auth.permission.WrongLoginPermission\"
Caused by: java.lang.ClassNotFoundException: org.wildfly.security.auth.permission.WrongLoginPermission from [Module \"org.wildfly.extension.elytron:main\" from local module loader @5479e3f (finder: local module finder @27082746 (roots: /home/olukas/workspace/uxcli/jboss-eap-7.1/modules,/home/olukas/workspace/uxcli/jboss-eap-7.1/modules/system/layers/base))]"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.permission-mapper.mapper"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
* Adding permission, but non existing module is used:
{code}
/subsystem=elytron/simple-permission-mapper=mapper:add(permission-mappings=[{permissions=[{action=read,class-name=org.wildfly.security.auth.permission.LoginPermission,target-name=someName,module=some.nonexist.module}]}])
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.permission-mapper.mapper" => "org.jboss.msc.service.StartException in service org.wildfly.security.permission-mapper.mapper: org.jboss.modules.ModuleNotFoundException: some.nonexist.module:main
Caused by: org.jboss.modules.ModuleNotFoundException: some.nonexist.module:main"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.permission-mapper.mapper"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
Suggestion for improvement:
* use only description of failure, e.g. something like "module a.b.c. does not exist"
* do not use any unneeded information - e.g. "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
was:
There are complicated failure-descriptions in Elytron simple-permission-mapper. They include some details from exceptions which are not needed and can be confused for non-java administrators. Please handle these exceptions and provide some user friendly failure-description.
Examples of complicated failure-description in simple-permission-mapper:
* Wrong name of permission class:
{code}
/subsystem=elytron/simple-permission-mapper=mapper:add(permission-mappings=[{permissions=[{action=read,class-name=org.wildfly.security.auth.permission.WrongLoginPermission,target-name=someName}]}])
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.permission-mapper.mapper" => "org.jboss.msc.service.StartException in service org.wildfly.security.permission-mapper.mapper: WFLYELY00021: Exception while creating the permission object for the permission mapping. Please check [class-name], [target-name] (name of permission) and [action] of [org.wildfly.security.auth.permission.WrongLoginPermission].
Caused by: org.wildfly.security.permission.InvalidPermissionClassException: ELY03015: Could not load permission class \"org.wildfly.security.auth.permission.WrongLoginPermission\"
Caused by: java.lang.ClassNotFoundException: org.wildfly.security.auth.permission.WrongLoginPermission from [Module \"org.wildfly.extension.elytron:main\" from local module loader @5479e3f (finder: local module finder @27082746 (roots: /home/olukas/workspace/uxcli/jboss-eap-7.1/modules,/home/olukas/workspace/uxcli/jboss-eap-7.1/modules/system/layers/base))]"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.permission-mapper.mapper"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
* Adding permission, but non existing module is used:
{code}
/subsystem=elytron/simple-permission-mapper=mapper:add(permission-mappings=[{permissions=[{action=read,class-name=org.wildfly.security.auth.permission.LoginPermission,target-name=someName,module=some.nonexist.module}]}])
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.security.permission-mapper.mapper" => "org.jboss.msc.service.StartException in service org.wildfly.security.permission-mapper.mapper: org.jboss.modules.ModuleNotFoundException: some.nonexist.module:main
Caused by: org.jboss.modules.ModuleNotFoundException: some.nonexist.module:main"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.permission-mapper.mapper"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
> Complicated failure-descriptions in Elytron simple-permission-mapper
> --------------------------------------------------------------------
>
> Key: WFLY-7475
> URL: https://issues.jboss.org/browse/WFLY-7475
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Labels: user_experience
>
> There are complicated failure-descriptions in Elytron simple-permission-mapper. They include some details from exceptions which are not needed and can be confused for non-java administrators. Please handle these exceptions and provide some user friendly failure-description.
> Examples of complicated failure-description in simple-permission-mapper:
> * Wrong name of permission class:
> {code}
> /subsystem=elytron/simple-permission-mapper=mapper:add(permission-mappings=[{permissions=[{action=read,class-name=org.wildfly.security.auth.permission.WrongLoginPermission,target-name=someName}]}])
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.permission-mapper.mapper" => "org.jboss.msc.service.StartException in service org.wildfly.security.permission-mapper.mapper: WFLYELY00021: Exception while creating the permission object for the permission mapping. Please check [class-name], [target-name] (name of permission) and [action] of [org.wildfly.security.auth.permission.WrongLoginPermission].
> Caused by: org.wildfly.security.permission.InvalidPermissionClassException: ELY03015: Could not load permission class \"org.wildfly.security.auth.permission.WrongLoginPermission\"
> Caused by: java.lang.ClassNotFoundException: org.wildfly.security.auth.permission.WrongLoginPermission from [Module \"org.wildfly.extension.elytron:main\" from local module loader @5479e3f (finder: local module finder @27082746 (roots: /home/olukas/workspace/uxcli/jboss-eap-7.1/modules,/home/olukas/workspace/uxcli/jboss-eap-7.1/modules/system/layers/base))]"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.permission-mapper.mapper"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> * Adding permission, but non existing module is used:
> {code}
> /subsystem=elytron/simple-permission-mapper=mapper:add(permission-mappings=[{permissions=[{action=read,class-name=org.wildfly.security.auth.permission.LoginPermission,target-name=someName,module=some.nonexist.module}]}])
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.permission-mapper.mapper" => "org.jboss.msc.service.StartException in service org.wildfly.security.permission-mapper.mapper: org.jboss.modules.ModuleNotFoundException: some.nonexist.module:main
> Caused by: org.jboss.modules.ModuleNotFoundException: some.nonexist.module:main"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.permission-mapper.mapper"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> Suggestion for improvement:
> * use only description of failure, e.g. something like "module a.b.c. does not exist"
> * do not use any unneeded information - e.g. "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months