Bug 1265492 - Information about creation of authorization/authentication in security domain is lost after reload/restart
Information about creation of authorization/authentication in security domain...
Status: CLOSED DUPLICATE of bug 1029928
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI (Show other bugs)
6.4.3
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Joe Wertz
Petr Kremensky
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-23 01:29 EDT by Juraj Duráni
Modified: 2016-01-04 00:08 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
standalone mode
Last Closed: 2015-09-23 03:48:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Juraj Duráni 2015-09-23 01:29:49 EDT
Description of problem:
If user creates a new security domain and authentication/authorization resource, subsequent reload/restart clears those resources.

Steps to Reproduce:
1. start the server
2. connect to cli
3. run commands:
/subsystem=security/security-domain=new:add
/subsystem=security/security-domain=new/authentication=classic:add
:reload
/subsystem=security/security-domain=new/authentication=classic/login-module=Remoting:add(flag=optional)

Actual results:
{
    "outcome" => "failed",
    "failure-description" => "JBAS014766: Resource [
    (\"subsystem\" => \"security\"),
    (\"security-domain\" => \"new\"),
    (\"authentication\" => \"classic\")
] does not exist; a resource at address [
    (\"subsystem\" => \"security\"),
    (\"security-domain\" => \"new\"),
    (\"authentication\" => \"classic\"),
    (\"login-module\" => \"Remoting\")
] cannot be created until all ancestor resources have been added",
    "rolled-back" => true
}

Expected results:
There is no element <authentication>/<authorization> in relevant section of standalone.xml. Maybe empty elements could help.
Comment 1 Chao Wang 2015-09-23 03:48:32 EDT

*** This bug has been marked as a duplicate of bug 1029928 ***

Note You need to log in before you can comment on or make changes to this bug.