1 2 Previous Next 17 Replies Latest reply on Dec 11, 2012 11:05 PM by Richard Robinson Go to original post
      • 15. Re: Unable to authenitcate to remote domain controller
        Wolf-Dieter Fink Master

        You should see the second HC in the management console of the DC.

        If I'm unsure I start a second HC on the same machine as the DC this will normally work without any problem and you can see the log entries and explore the management console.

        • 16. Re: Unable to authenitcate to remote domain controller
          Michael G Novice

          Ok, i fixed that last issue, forgot to update the module in the second server.


          Also, i do see it in the console, apparently this version of the console looks slightly different form 7.0.2.


          Thanks everyone for helping me get this going.  Time to dive in deeper to get a better understanding.

          • 17. Re: Unable to authenitcate to remote domain controller
            Richard Robinson Newbie

            Kairi Henry's posting is correct (as of "JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1)").



            By "node02" is meant the slave host.xml, of which relevant parts are emboldened:


            <host name="slaveHostName" xmlns="urn:jboss:domain:1.3">

                          <security-realm name="RemoteManagementRealm">
                                <local default-user="slaveHostName" />
                                <properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>
                                <secret value="base64encodedPasswordOfSlaveHostName" /> <!-- password base-64 encoded for user 'slaveHostName') -->




            The master host/domain must have a mgmt-users.properties entry for slaveHostName user that where password is encrypted (password here is encrypted, but it's base-64 encoded in the slave):





            1 2 Previous Next