Hope this helps!

It helped immensely thank you...
It forced me to go and find where I had got push_header() from. In doing that search of source code it twigged that it was not the header that needed token_type but the content. With that realisation, the rest sort of fell into place.

Here is the working overridden sub in case anyone has a similar problem and comes across this in future:

sub construct_tokens {
    my ($self, $oauth2, $response) = @_;
    
    my $content = eval {decode_json($response->content)};
    unless ($@) {
        $content->{'token_type'} = 'bearer';
        $response->content(encode_json($content));
    }
    
    $self->SUPER::construct_tokens($oauth2, $response);
}
[download]

Can anyone explain what the documentation means when is says to contribute one should submit a git pull request? I would like to contribute my LinkedIn solution when it is complete and tested as I am sure I am not the only person wanting to connect to LinkedIn with Perl.

> Can anyone explain what the documentation means

I can try. It means you can get your provider included in the distribution, instead of creating a distribution of your own. Currently, there are several providers in the dist: LWP::Authen::OAuth2::ServiceProvider::Google, LWP::Authen::OAuth2::ServiceProvider::Dwolla, LWP::Authen::OAuth2::ServiceProvider::Line, LWP::Authen::OAuth2::ServiceProvider::Strava, and LWP::Authen::OAuth2::ServiceProvider::Yahoo.

If you want to create LWP::Authen::OAuth2::ServiceProvider::LinkedIn and have it included in the distribution, you need to fork the GitHub repository and create a pull request satisfying all the listed conditions.

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

you need to fork the GitHub repository and create a pull request

That's the bit I'm not sure what I'm doing...
But I guess the starting point is to create a GitHub account and go from there.

Hi, "not managing to get the injection to work" doesn't really describe the problem well

Sorry - yes, re-reading my question shows it is not very clear.

What I meant was that injecting the token_type parameter is not working. My sub doesn't throw an error but causes the super class sub to throw an error that token_type is missing.

push_header() since that does not appear as a documented method on an HTTP::Response object

HTTP::Response extends HTTP::Message which requires's HTTP::Headers and push_header() is a method of this class.

Although looking at the link you provided sparked the realisation that token_type is not a header at all. It needs to be added to the content rather than the header. So I think I am going to have to decode the JSON content to a Perl data structure, add the token_type parameter before encoding it back to JSON and passing that to the super class' sub.

I can see running into propblems with the encoding as there doesn't appear to be a way to reverse the effects of decoded_content

Never mnind, sry, not enough coffee.

You misunderstand how the inheritance works. See the doc I linked to and run some minimal tests.



The way forward always starts with a minimal test.