ruby bindings seem to always set Authorization header
It seems that even when the client is configured with aclient cert and key, the client bindings are setting Authorization header. If the BasicAuthorization is enabled on the server, the user is not able to authenticate using the client cert and key. Removing the BasicAuthorization resolves the problem.
#3 Updated by email@example.com 11 months ago
- Status changed from NEW to POST
- Assignee set to firstname.lastname@example.org
Please register to edit this issue