Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"Authorization" header support for endpoints #1203

Closed
jazzybluesea opened this issue May 21, 2020 · 1 comment · Fixed by #1563
Closed

"Authorization" header support for endpoints #1203

jazzybluesea opened this issue May 21, 2020 · 1 comment · Fixed by #1563
Assignees
@achamayou
Labels
enhancement
Milestone
MAA support

Comments

@jazzybluesea
Copy link

Currently when a Bearer token is in to an HTML request to a CCF node the server will nack with the following error:

Error parsing request: Unable to parse signature params from: Bearer eyJ0eXAiOiJKV...

In order to support access tokens from AAD. The server would have to change to allow such Bearer tokens in the HTML header.

Ideally, there could be some functions for decoding, validating such tokens.
@achamayou achamayou self-assigned this Jul 14, 2020
@achamayou
Copy link
Member

CCF needs to allow the header through when it's not a client signature, and the application can handle decoding as required.

@achamayou achamayou added this to the MAA support milestone Jul 14, 2020
@letmaik letmaik changed the title JWT token support "Authorization" header support for endpoints Sep 3, 2020
@letmaik letmaik mentioned this issue Sep 3, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@achamayou achamayou

Labels
enhancement
Projects
None yet
Milestone
MAA support
Development

Successfully merging a pull request may close this issue.

Support custom authorization header in client requests letmaik/CCF
2 participants
@achamayou @jazzybluesea