Closed ErmakovDmitriy closed 1 year ago
that fix was propagated, but suffers from an error here: https://github.com/zmartzone/liboauth2/blob/v1.4.5.2/src/server/apache.c#L459 instead of adding a header, it should overwrite the existing one, so the single header will correctly be removed here: https://github.com/zmartzone/mod_oauth2/blob/v3.3.0/src/mod_oauth2.c#L230-L231
Thank you for the fix! =)
For now, I get only 1 line with the error in the response (< www-authenticate: Bearer error="insufficient_scope", error_description="Different scope(s) or other claims required."
) which does not break our HTTP load balancer.
I might have done something wrong but am I supposed to get even the one line despite the fact that the access is allowed? Anyway, one line should not be a problem for us, I think.
hm, I thought it was quick to fix; I'll properly reproduce and fix it now, it is not supposed to be there when the overall access result is "allowed"
I had to revert the patch from liboauth2 1.4.5.3 (pulled now) in 1.4.5.4 and released mod_oauth2 3.3.1 that solves this issue
We use Apache 2.4, mod_oauth 3.3.0.
In the Apache configuration we have access control configuration as below:
When we get access to the protected directory (Apache autoindex) using a valid bearer token, we get access but the response contains plenty of header as below:
Corresponding debug logs:
It seems that this issue might have been fixed in https://github.com/zmartzone/mod_auth_openidc/commit/8ed00cc8baec964e8730e8069fd748437584ab4c but was not propagated to the OAuth2 module.
Could you, please, take a look at it and fix or recommend a solution for us?
/cc @manfuin