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

Enhancement: Authentication is currently only via user/pass, request API Client, too #28

Open
QuaCKeReD opened this issue Sep 2, 2020 · 0 comments
Open

Enhancement: Authentication is currently only via user/pass, request API Client, too #28

QuaCKeReD opened this issue Sep 2, 2020 · 0 comments

Comments

@QuaCKeReD
Copy link
Contributor

Currently, access is stored as user@customer:password, and calls with header values to match.

API Clients requires the header to pass bearer values, using access tokens obtained via OAuth.
@QuaCKeReD QuaCKeReD changed the title Authentication is currently only via user/pass, request API Client, too Enhancement: Authentication is currently only via user/pass, request API Client, too Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@QuaCKeReD