Skip to content

Use proper Authn header when contacting capi-d #18

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

oahayder
Copy link

@oahayder oahayder commented Jan 10, 2019

We should be sending the oauth_* tokens in the header form Authorization: Bearer * as is described here: https://github.com/plangrid/customer_api_dispatcher#oauth-authentication

We will support the existing authn in centauth but should move to the documented protocol.

Any way to test this? Have no experience with this repo or c#. Need to be sure that AuthenticationHeaderValue doesn't b64 encode the token value. The server expects Bearer oauth_token

Found this doc which may help: https://github.com/AzureAD/azure-activedirectory-library-for-dotnet/wiki/Using-the-acquired-token-to-call-a-protected-Web-API


This change is Reviewable

We should be sending the oauth_* tokens in the header form ```Authorization: Bearer *``` as is described here: https://github.com/plangrid/customer_api_dispatcher#oauth-authentication

We will support the existing authn in centauth but should move to the documented protocol.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants