Issue #3164
Requesting a JWT token doesn't support basic auth
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Description
Currently, you have to pass username and password in the body of the POST request to /api/v3/jwt. It should probably use basic auth.
Related issues
History
#1
Updated by daviddavis almost 2 years ago
There's some debate around whether to use basic auth in addition to allowing users to submit username/password as POST params or just basic auth.
#2
Updated by daviddavis almost 2 years ago
- Subject changed from Requesting a JWT token should have basic auth to Requesting a JWT token should support basic auth
#3
Updated by daviddavis almost 2 years ago
- Subject changed from Requesting a JWT token should support basic auth to Requesting a JWT token doesn't support basic auth
#4
Updated by dalley almost 2 years ago
- Triaged changed from No to Yes
#5
Updated by bmbouter almost 2 years ago
I think we should only accept basic auth. Having one endpoint accept another one seems inconsistent.
#6
Updated by daviddavis almost 2 years ago
- Related to Story #3163: As a user, I can refresh an unexpired JWT. added
#7
Updated by daviddavis almost 2 years ago
JWT got removed from the MVP. Going to revisit again in 3.1+ with new user stories.
#8
Updated by daviddavis almost 2 years ago
- Status changed from NEW to CLOSED - WONTFIX
#9
Updated by dkliban@redhat.com over 1 year ago
- Sprint/Milestone set to 3.0
Please register to edit this issue
.