WildFly Security Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 64: Line 64:


Otherwise, the secret's value is displayed during the process of adding the user to the Management Realm on the domain controller (as described here: [[Adding Users to WildFly Security Realms#Add_a_User_to_the_Management_Realm|Adding a User to the Management Realm]]). The value displayed by <tt>add-user.sh</tt> is identical with the one calculated by <tt>openssl enc -base64</tt>. They can be used interchangeably.
Otherwise, the secret's value is displayed during the process of adding the user to the Management Realm on the domain controller (as described here: [[Adding Users to WildFly Security Realms#Add_a_User_to_the_Management_Realm|Adding a User to the Management Realm]]). The value displayed by <tt>add-user.sh</tt> is identical with the one calculated by <tt>openssl enc -base64</tt>. They can be used interchangeably.
==Secret Value==
The "secret value" generated by the procedure described above is actually the "<tt>openssl enc -base64</tt>" of the password.
<pre>
echo -n "myPassword" | openssl enc -base64
</pre>


==Configuration==
==Configuration==

Revision as of 01:27, 19 February 2016




in process of being migrated from https://home.feodorov.com:9443/wiki/Wiki.jsp?page=JBoss7SecurityConcepts




Internal

Relevance

  • EAP 6.4 August 2015

Security Realms

Security Realms

The Security Subsystem

Security Subsystem Concepts

Relationship between a Security Realm and a Security Domain

Subordinated Host Controller Identity

Subordinated host controllers must authenticate against the domain controller's Management Realm in order to be able to interact with it. The host controller identity is associated to a domain controller's Management Realm user whose name is identical with the host controller's host name (the <host name="..."> element in the host controller's host.xml.

From the domain controller's perspective, the host controller identity is established by adding a regular Management Realm user. This is done with the add-user.sh utility, as described here:

Adding a User to the Management Realm

Secret

A Management Realm user authenticates with a regular password, so the host controllers will also have to use the same mechanism - password - to authenticate. The password is is known as server identity secret on the host controller, and it is specified in its host.xml:

<host name="..." ...>
  <management>
    <security-realms>
      <security-realm name="ManagementRealm">
        ...
        <server-identities>
          <secret value="bjFfMTIz"/>
        </server-identities>
      </security-realm>
    ...
</host>

The secret maintained in the <server-identities> section of host.xml is the hashed value of the domain controller Management Realm user's password. Given the password value, the secret value can be calculated as follows:

echo -n "myPassword" | openssl enc -base64

Otherwise, the secret's value is displayed during the process of adding the user to the Management Realm on the domain controller (as described here: Adding a User to the Management Realm). The value displayed by add-user.sh is identical with the one calculated by openssl enc -base64. They can be used interchangeably.

Configuration

Subordinated Host Controller Identity Configuration