Exception when allowChaining is true and the strategies are defined via default auth value

In our use case, we are trying to define two auth strategies to be validated one before other. Defining hapi-auth-bearer-token validation as the first one, we have seen that it is possible using the flag allowChaining. If the bearer token received in not a valid token, try the second one before saying that the token is not valid.

server.auth.strategy('simple', 'bearer-access-token', { allowChaining: true, validateFunc });
server.auth.strategy('jwt', 'jwt', jwtValidation);

It we define the strategies in each route, it works as we expected:

{
      method: 'GET',
      options: {
        auth: {
          strategies: ['simple', 'jwt'],
        },
     }
}

But if we try to define the strategies as the default ones, we face an exception:

server.auth.default({ strategies: ['simple', 'jwt'] });

The exception comes from the following line of the scheme definition:

const message = (settings.allowChaining && request.route.settings.auth.strategies.length > 1) ? null : 'Bad token';

strategies is undefined.

Could we add support for default option when we define multiple strategies ?

johnbrett / hapi-auth-bearer-token

Exception when allowChaining is true and the strategies are defined via default auth value #171