EAP 7 authentication mechanism silently fails with custom login module although module call is a success

Solution Verified - Updated -

Issue

  • We are using a custom login module on EAP 7. Calls to the login module are successful and no errors are seen, but still the user is not authenticated. Undertow just logs a message like the following:
TRACE [org.wildfly.extension.undertow] (default task-1) User: org.wildfly.extension.undertow.security.AccountImpl$AccountPrincipal@35c124 is authenticated
12:31:34,698 DEBUG [io.undertow.request.security] (default task-1) Authentication outcome was NOT_AUTHENTICATED with method

Environment

  • JBoss Enterprise Application Platform (EAP) 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content