Project

Profile

Help

Send by e-mail

Issue #6246

ruby bindings seem to always set Authorization header

Added by dkliban@redhat.com 7 months ago. Updated 6 months ago.

Status:
NEW
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

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.

Associated revisions

Revision d53b27b0 View on GitHub
Added by dkliban@redhat.com 7 months ago

Updates openapi-generator-cli to 4.2.3

This release contains a fix related to Basic auth header.

re: #6246 https://pulp.plan.io/issues/6246

History

#1 Updated by fao89 7 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 67

#2 Updated by fao89 7 months ago

  • Tags API Bindings added

#3 Updated by dkliban@redhat.com 7 months ago

  • Status changed from NEW to POST
  • Assignee set to dkliban@redhat.com

#4 Updated by rchan 7 months ago

  • Sprint changed from Sprint 67 to Sprint 68

#5 Updated by dkliban@redhat.com 6 months ago

  • Status changed from POST to NEW
  • Assignee deleted (dkliban@redhat.com)

Newer version of openapi-generator did not resolve the issue. I am setting this back to NEW.

#6 Updated by rchan 6 months ago

  • Sprint deleted (Sprint 68)

#7 Updated by rchan 6 months ago

Less of a concern with the newest version of dynaconf. Still an issue but less of a priority.

Please register to edit this issue

Send by e-mail

Also available in: Atom PDF