Skip to content

Move default header generation from msal-common to msal-node #1473

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
Closed
3 of 15 tasks
sangonzal opened this issue Apr 7, 2020 · 1 comment
Closed
3 of 15 tasks

Move default header generation from msal-common to msal-node #1473

sangonzal opened this issue Apr 7, 2020 · 1 comment
Labels
internal Issues created by MSAL.js team for internal tracking.

Comments

@sangonzal
Copy link
Contributor

Please follow the issue template below.

Library

Upcoming Library

Type

  • Bug
  • Feature
  • Enhancement
  • Tooling
  • Documentation
  • Samples
  • Other (please describe)

Source

  • Internal (MSAL.js team)
  • Customer request

Description

A clear and concise description of the work to be completed.
Move over default library headers from msal-common to msal-node

Priority

How important is this work? When should it be completed (e.g. current quarter, next quarter)?

Acceptance Criteria

Describe the conditions that must met for this work to be considered complete.

  1. Default headers should be sent on requests to all endpoints
  2. Default headers should be set in msal-node
@sangonzal sangonzal added the internal Issues created by MSAL.js team for internal tracking. label Apr 7, 2020
@sangonzal
Copy link
Contributor Author

#1482

@pkanher617 pkanher617 mentioned this issue May 14, 2020
Closed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
internal Issues created by MSAL.js team for internal tracking.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pkanher617 @sangonzal