Search

Appendix A. Reference Material

download PDF

A.1. Example wildfly-config.xml

The wildlfly-config.xml file is one way for clients to use Elytron Client, which allows clients to use security information when making connections to JBoss EAP. For more details on using Elytron Client, see Configure Client Authentication with Elytron Client.

Example: custom-config.xml

<configuration>
  <authentication-client xmlns="urn:elytron:1.0.1">
    <authentication-rules>
      <rule use-configuration="monitor">
        <match-host name="127.0.0.1" />
      </rule>
      <rule use-configuration="administrator">
        <match-host name="localhost" />
      </rule>
    </authentication-rules>
    <authentication-configurations>
      <configuration name="monitor">
        <sasl-mechanism-selector selector="DIGEST-MD5" />
        <providers>
          <use-service-loader />
        </providers>
        <set-user-name name="monitor" />
        <credentials>
          <clear-password password="password1!" />
        </credentials>
        <set-mechanism-realm name="ManagementRealm" />
      </configuration>

      <configuration name="administrator">
        <sasl-mechanism-selector selector="DIGEST-MD5" />
        <providers>
          <use-service-loader />
        </providers>
        <set-user-name name="administrator" />
        <credentials>
          <clear-password password="password1!" />
        </credentials>
        <set-mechanism-realm name="ManagementRealm" />
      </configuration>
    </authentication-configurations>

    <net-authenticator/>

    <!-- This decides which SSL context configuration to use -->
    <ssl-context-rules>
      <rule use-ssl-context="mycorp-client">
        <match-host name="mycorp.com"/>
      </rule>
    </ssl-context-rules>
    <ssl-contexts>
      <default-ssl-context name="mycorp-context"/>
      <ssl-context name="mycorp-context">
        <key-store-ssl-certificate key-store-name="store1" alias="mycorp-client-certificate"/>
        <!-- This is an OpenSSL-style cipher suite selection string; this example is the expanded form of DEFAULT to illustrate the format -->
        <cipher-suite selector="ALL:!EXPORT:!LOW:!aNULL:!eNULL:!SSLv2"/>
        <protocol names="TLSv1.2"/>
      </ssl-context>
    </ssl-contexts>
  </authentication-client>
</configuration>

For more information about how to configure clients using the wildfly-config.xml file, see Client Configuration Using the wildfly-config.xml File in the Development Guide for JBoss EAP.

A.2. Reference for Single Sign-on Attributes

An SSO authentication mechanism configuration.

This is the reference for the setting=single-sign-on resource of the application-security-domain in the undertow subsystem.

A.2.1. Single Sign-on

Table A.1. single-sign-on Attributes
AttributeDescription

domain

The cookie domain to be used.

path

The cookie path.

http-only

For setting cookie’s httpOnly attribute.

secure

For setting cookie’s secure attribute.

cookie-name

The name of the cookie.

key-store

The reference to keystore containing a private key entry.

key-alias

The alias of the private key entry used for signing and verifying back-channel logout connection.

credential-reference

The credential reference to decrypt the private key entry.

credential-reference has the following attributes:

  • store : The name of the credential store holding the alias to credential.
  • alias : The alias which denotes stored secret or credential in the store.
  • type : The type of credential this reference is denoting.
  • clear-text : The secret specified using clear text. Checks the credential store way of supplying credential or secrets to services.

client-ssl-context

The reference to the SSL context used to secure back-channel logout connection.





Revised on 2018-10-11 12:32:41 UTC

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.