Bug 1272011 - [GSS](6.4.z) Configuring security-domain causes JBAS014803 Duplicate resource error
Summary: [GSS](6.4.z) Configuring security-domain causes JBAS014803 Duplicate resource...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.4.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.7
Assignee: Chao Wang
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks: 1274291 eap647-payload
TreeView+ depends on / blocked
 
Reported: 2015-10-15 09:33 UTC by Takayuki Konishi
Modified: 2019-08-15 05:40 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 11:54:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2190941 0 None None None 2016-03-07 03:28:43 UTC

Description Takayuki Konishi 2015-10-15 09:33:36 UTC
Description of problem:
Configuring security-domain causes JBAS014803 Duplicate resource error

How reproducible: 100%

Steps to Reproduce:
1. Start JBoss EAP  
2. Open http://localhost:9990/console/App.html#security-domains from a browse
3. Add a security domain
4. Click "View" link of the created security domain
5. Add an authentication login module (ex. Code: foo, Flag: required)
6. Add a module option

Actual results:
The module option is added.

Expected results:
"Failed to modify login-modules" [1] was shown in the notification center area.
The module option was not added.

Additional info:
After I went back to Security Domains page then clicked "View" link, I could add a module option. So it seems login module "foo" is registered halfway before I moved to other page.

Module options in Authorization, Mapping and Audit tab also cause same error.


[1]
Failed to modify login-modules

Unexpected HTTP response: 500

Request
{
    "operation" => "composite",
    "address" => [],
    "steps" => [
        {
            "operation" => "add",
            "address" => [
                ("subsystem" => "security"),
                ("security-domain" => "foo"),
                ("authentication" => "classic")
            ]
        },
        {
            "operation" => "write-attribute",
            "address" => [
                ("subsystem" => "security"),
                ("security-domain" => "foo"),
                ("authentication" => "classic")
            ],
            "name" => "login-modules",
            "value" => [{
                "code" => "bar",
                "flag" => "required",
                "module-options" => [("baz" => "hoge")]
            }]
        }
    ]
}

Response

Internal Server Error
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "failure-description" => "JBAS014803: Duplicate resource [
    (\"subsystem\" => \"security\"),
    (\"security-domain\" => \"foo\"),
    (\"authentication\" => \"classic\")
]",
            "rolled-back" => true
        },
        "step-2" => {"outcome" => undefined}
    },
    "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [
    (\"subsystem\" => \"security\"),
    (\"security-domain\" => \"foo\"),
    (\"authentication\" => \"classic\")
]"}},
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}

Comment 5 Michael Cada 2016-03-03 15:36:18 UTC
Verified on EAP 6.4.7.CP.CR2

Comment 6 Petr Penicka 2017-01-17 11:54:43 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.


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