Skip to content

feat: expose response headers, username+password authentication #302

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

Merged
merged 6 commits into from
Feb 2, 2021

Conversation

sranka
Copy link
Contributor

@sranka sranka commented Feb 1, 2021

This PR

  • allows receiving HTTP response headers in all APIs
  • allows authenticating users with username+password in all APIs
  • adds tokens.js example that shows how to use username+password authentication to establish authenticated session to manage authorization tokens

Checklist

  • CHANGELOG.md updated
  • Rebased/mergeable
  • A test has been added if appropriate
  • yarn test completes successfully
  • Commit messages are in semantic format

Sorry, something went wrong.

@sranka sranka requested a review from vlastahajek February 2, 2021 08:25
@sranka sranka marked this pull request as ready for review February 2, 2021 08:26
@sranka sranka linked an issue Feb 2, 2021 that may be closed by this pull request
@sranka sranka changed the title feat: expose response headers feat: expose response headers, username+password authentication Feb 2, 2021
Copy link
Contributor

@vlastahajek vlastahajek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@sranka sranka merged commit d2e9a59 into master Feb 2, 2021
@sranka sranka deleted the feat/apis_expose_response_headers branch February 2, 2021 13:08
@bednar
Copy link
Contributor

bednar commented Feb 2, 2021

👍

@bednar bednar added this to the 1.11.0 milestone Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Getting token using username & password from the client (2.X)
3 participants