Bug 1326165 - How to reorder JBoss LoginModules via CLI?
Summary: How to reorder JBoss LoginModules via CLI?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.4.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Bartek Spyrko-Smietanko
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 02:49 UTC by xuzhan
Modified: 2019-10-10 11:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-28 10:24:10 UTC
Type: Feature Request


Attachments (Terms of Use)

Description xuzhan 2016-04-12 02:49:12 UTC
Description of problem:
Customer want to have CLI command to reorder the sequence of <login-module> from standlane.xml/domain.xml

Version-Release number of selected component (if applicable):


How reproducible:

For example, customer has login-modules as below:
~~~
<security-domain name="other" cache-type="infinispan">
    <authentication>
        <login-module code="Remoting" flag="optional">
            <module-option name="password-stacking" value="useFirstPass"/>
        </login-module>
        <login-module code="RealmDirect" flag="required">
            <module-option name="password-stacking" value="useFirstPass"/>
        </login-module>
        <login-module code="RoleMapping" flag="optional">
            <module-option name="rolesProperties" value=Mapping.properties"/>
            <module-option name="replaceRole" value="true"/>
        </login-module>  
        <login-module code="abc.jboss.XYZ" flag="optional" module="abc.e">
            <module-option name="password-stacking" value="useFirstPass"/>
        </login-module>        
    </authentication>
</security-domain>
~~~

Customer wants to move the last <login-module> to the first place through CLI command.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Can this be done as a feature request in next release or near future?


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