Project

Profile

Help

Issue #6246

closed

ruby bindings seem to always set Authorization header

Added by dkliban@redhat.com about 4 years ago. Updated about 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
API Bindings
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/1871":https://github.com/pulp/pulpcore/issues/1871


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.

Also available in: Atom PDF