-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PXP-10229 Client auth mapping #153
Conversation
arborist/server.go
Outdated
username = usernameQS[0] | ||
} else if authHeader := r.Header.Get("Authorization"); authHeader != "" { | ||
// Fall back to JWT for username. Added for Arborist UI integration... | ||
if authHeader := r.Header.Get("Authorization"); authHeader != "" { | ||
server.logger.Info("No username in query args; falling back to jwt...") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably remove this log or update the language
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see other logs below too, ensure wording doesn't imply "falling back" to jwt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see minor comments
Jira Ticket: PXP-10229
New Features
POST /auth/mapping
endpoint now supports aclientID
parameter to get the auth mapping for a client. It accepts either ausername
parameter or aclientID
parameter (not both).Breaking Changes
GET /auth/mapping
endpoint does not acceptusername
as a query parameter anymore. It only supports parsing the username from the provided JWT. To specify a username, use thePOST /auth/mapping
endpoint.Bug Fixes
Improvements
Dependency updates
Deployment changes