Bug 1085228 - In domain mode, when security realm for management interface is undefined the reload of the server is neccessary but the user is not prompted to do so.
Summary: In domain mode, when security realm for management interface is undefined the...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR8
: EAP 6.4.0
Assignee: Chao Wang
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-08 07:07 UTC by Martin Velas
Modified: 2019-08-19 12:45 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3565 0 Critical Resolved Incorrect use of ReloadRequiredWriteAttributeHandler for host resources 2016-02-02 09:32:56 UTC

Description Martin Velas 2014-04-08 07:07:28 UTC 
Description of problem:
In domain mode, when security realm for http management interface is undefined the reload of the server is neccessary but the user is not prompted to do so.

Version-Release number of selected component (if applicable):
EAP 6.3.0.ER1

How reproducible:
allways

Steps to Reproduce:
1. start server in domain mode
2. start CLI client ./jboss-cli.sh -c
3. run CLI command /host=master/core-service=management/management-interface=http-interface:undefine-attribute(name=security-realm)

Actual results:
command result but no prompt/warning, that the reload is required

Expected results:
prompt/warning, that the reload is required
Comment 4 Chao Wang 2014-10-27 12:09:44 UTC 
6.x PR : https://github.com/jbossas/jboss-eap/pull/1849
Comment 5 Petr Kremensky 2014-11-05 13:22:34 UTC 
Verified on EAP 6.4.0.DR8.

We don't have to reload a host to take effect of :undefine-attribute invocation on security-realm.
Note You need to log in before you can comment on or make changes to this bug.