How to configure EJB standalone client application security in EAP 7.1

Environment

Red Hat Enterprise Application Platform (EAP) 7.1

Issue

• How to configure EJB standalone client application security in EAP 7.1

Resolution

Using the wildfly-client.xml configuration

• Package a wildfly-client.xml configuration file in the META-INF of the application

<configuration>
  <!--  <authentication-client xmlns="urn:elytron:1.0">
        <authentication-rules>
            <rule use-configuration="default"/>
        </authentication-rules>
        <authentication-configurations>
            <configuration name="default">
                <allow-all-sasl-mechanisms/>
                <set-mechanism-properties>
                    <property key="wildfly.sasl.local-user.quiet-auth" value="true"/>
                </set-mechanism-properties>
            </configuration>
        </authentication-configurations>
    </authentication-client>-->
    <authentication-client xmlns="urn:elytron:1.0">
        <authentication-rules>
            <rule use-configuration="default"/>
        </authentication-rules>
        <authentication-configurations>
            <configuration name="default">
                <allow-sasl-mechanisms names="DIGEST-MD5"/>
                <set-user-name name="joe"/>
                <credentials>
                    <clear-password password="joeIsAwesome2013!"/>
                </credentials>
            </configuration>
        </authentication-configurations>
    </authentication-client>
    <jboss-ejb-client xmlns="urn:jboss:wildly-client-ejb:3.0">
        <connections>
            <connection uri="remote+http://127.0.0.1:8080" />
        </connections>
    </jboss-ejb-client>
</configuration>

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.