I get to situation where in method GSSCredentialSecurityFactory.createGSSCredential() the cause of LoginException is hidden from user.

In log there is

14:26:07,751 TRACE [org.wildfly.security] (default task-1) java.security.GeneralSecurityException: ELY01121: Unable to perform initial JAAS login.

But with debugger I get to obvious cause javax.security.auth.login.LoginException: Bad JAAS configuration: credsType and keytab values are not compatible, but this is not logged into log.

Setting to high priority, because logging useful information is essential for troubleshooting fragile Kerberos setup.

Mesage

    @Message(id = 1121, value = "Unable to perform initial JAAS login.")
    GeneralSecurityException unableToPerformInitialLogin(@Cause LoginException cause);

is created in

	    } catch (LoginException e) {
                throw log.unableToPerformInitialLogin(e);
            }

and logged into log by

                        } catch (GeneralSecurityException e) {
                            // skip this credential
                            log.trace(e);
                        }

An more importantly. Question here is if some global issue should follow up? Because problem is in usage of log.trace(e) where although cause exception is avalaible, effectivelly is called log.trace(e.toString()) and cause is hidden; So probably some global check should be performed in elytron codebase if other such occurences aren't also problematic.