Coverage decreased (-0.8%) to 99.167% when pulling da6b8e975c14ae3722219ce3894e4395608582a7 on basz:invalid-token-error into 470eea74277ed2b54cc7ec968bbf61377ca33660 on zf-fr:master.
Coverage remained the same at 100.0% when pulling f7b0f03cb01c45747259afb0bd83eb02d341face on basz:invalid-token-error into 470eea74277ed2b54cc7ec968bbf61377ca33660 on zf-fr:master.
Coverage remained the same at 100.0% when pulling f7b0f03cb01c45747259afb0bd83eb02d341face on basz:invalid-token-error into 470eea74277ed2b54cc7ec968bbf61377ca33660 on zf-fr:master.
returned payload by resource middleware is now
{"error" : "invalid_token", "error_description": "Access token has expired or has been deleted"}
instead of
{"error": "Access token has expired or has been deleted"}
Resource server still returns an InvalidAccessTokenException but now has a string code of
invalid_token