Bug 910322
| Summary: | Cannot add security role to security-setting using CLI | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Miroslav Novak <mnovak> |
| Component: | Security | Assignee: | Jeff Mesnil <jmesnil> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | brian.stansberry, rsvoboda |
| Target Milestone: | ER2 | ||
| Target Release: | EAP 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When adding a `security-role` using the CLI or API, it was required that the user specify both the roles that it should have, and all the roles that it should not. This was because the `:add` operation for this resource did not have default values for these parameters. These parameters now default to `false`. Adding a role now only requires that you specify the roles that the security-role must have by setting them to `true`. All other roles default to `false`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Jeff Mesnil <jmesnil> made a comment on jira AS7-6515 PR for master branch PR for EAP: https://github.com/jbossas/jboss-eap/pull/3 This was merged twelve days ago, so moving to ON_QA. This did not get to any EAP 6.1.0.ERx release yet. Setting status Modified. This blocks testing automation. Taking back. I hit another issue in my tests. Setting as verified. |
Not possible to add security role to security-setting using CLI: [standalone@localhost:9999 hornetq-server=default] ./security-setting=#/role=franta:add() { "outcome" => "failed", "failure-description" => "JBAS014746: send may not be null", "rolled-back" => true }