Adding the option to use the 'response' attirbute of server.auth.scheme

[jppellerin]

http://hapijs.com/api#serverauthschemename-scheme

This addition will allow to use the hapi-auth-jwt2 plugin to leverage the response attribute of the hapi api (see link above).

Using this strategy something like so is now feasible :

...
server.auth.strategy('jwt', 'jwt', true,
{
    key: "sshhhh",
    validateFunc: validate,
    verifyOptions: {
        algorithms: [ 'HS256' ]
    },
    responseFunc: function(request, reply) {
        request.response.header('new-header', 'added here');
    }
});
...

[nelsonic]

@jppellerin did someone request this feature or are you planning on using it in your projects?
would you mind creating a test to exercise this new functionality and add it to your branch/PR ?

[jppellerin]

@nelsonic Tests are added. Thoughts?

[nelsonic]

@jppellerin looks good.
this feature has not been requested by anyone in the issues or gitter,
but if you are going to use it in your projects we can merge it in. 👍

[nelsonic]

The most important thing is that existing users of the plugin will not have to make any modifications to their existing code. and unless their server calls the response method they will not even know this feature is available...

[jppellerin]

Thank you. Yes, that was the desired outcome. Where we can add that feature without affecting anything else. We are using it - and thus I implemented the feature. Thought I'd contribute it back in case anyone was in our situation.

The use case is that we are using tokens for our web app authentication. We are sending a refreshed version of the token back through the authorization header to keep the session alive if the user is still active. This was the cleanest way of doing it. If not we were stuck changing our response objects.

[nelsonic]

@jppellerin agreed.
I will be preparing the release notes tonight. 👍