Fix update error

[colq2]

This pull request solves #15 .

The problem was parseResponse function from AbstractProvider which force the reponse to be an array and have no possibility to parse application/jwt.
If we use encrypted userinfo endpoint we are getting only the jwt token which is a simple string.

This results in an UnexpectedValueException with the message An OAuth server error was encountered that did not contain a JSON body. Also see AbstractProvider line 694.

[Airforce111]

Any chance we can get this merged?

[Zaszczyk]

@stevenmaguire can you merge it?

[stevenmaguire]

@colq2 Thanks for your patience on this. I have been reluctant to simply merge this as is because of the lack of test cases that demonstrate the specific use case that is being addressed here. Would you mind adding some specific tests to cover this use case?

[colq2]

Yes, I will add some tests soon.

[stevenmaguire]

Thank you!

[walva]

@colq2 do you need help on this? What is the current status?

[colq2]

Hello @lobodol and @stevenmaguire,
I looked into it again today. Every test you need is already there. If we remove the parseResponse function from Keycloak.php two test will fail:

"Invalid response received from Authorization Server. Expected JSON." is an exception which occurs because, as I said, keycloak responses with just a string.

I think there is no reason why you would not merge this.

[stevenmaguire]

I'm happy to add another contributor to this project - #27 (comment)

[arthurtemple]

@mstefan21 Any chance to get it merged after all this time? Downstream projects might not be able to update past 2.0.0 because of conflicting dependency constraints.

[mstefan21]

@arthurtemple Sorry for late reply, I will look at the end of this week and prepare relase of new version

[mstefan21]

@arthurtemple Released as version 2.2.2

[arthurtemple]

@arthurtemple Released as version 2.2.2

Very nice, thanks!