JBREM000308: Authentication failed (no mechanisms left), tried: (none) in EAP 7

Solution Verified - Updated

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 7.1

Issue

  • Getting JBREM000308 with no authentication mechanisms (i.e. tried: (none))
  • JBREM000308: Authentication failed (no mechanisms left), tried: (none) in EAP 7
  • We have recently done migration from JBoss 7.0.7 to JBoss7.1.6, after migration we are getting below exception in our code "Caused by: org.wildfly.security.auth.AuthenticationException: JBREM000308: Authentication failed (no mechanisms left), tried: (none)". Please suggest on it.

Resolution

Check the configured security configuration for mistakes the connector being used. For example, you may have a typo in the realm name.

The following shows an extra space in "Application Realm":

    <http-authentication-factory name="application-http-authentication" http-server-mechanism-factory="global" security-domain="ApplicationDomain">
        <mechanism-configuration>
            <mechanism mechanism-name="BASIC">
                <mechanism-realm realm-name="Application Realm"/>
            </mechanism>
           <mechanism mechanism-name="FORM"/>
        </mechanism-configuration>
    </http-authentication-factory>

Root Cause

Misconfiguration on the server side, such that the security-realm specified on the remoting http-connector does not match and thus there is nothing for it to authenticate against.

Diagnostic Steps

Check the JBoss server side configuration and make sure the security-realm specified on the remoting subsystem http-connector is defined and spelled correctly in the security-domains section.

SBR
Product(s)
Category
Tags

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.