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

Could not find WWW-Authenticate header in response #10388

Closed
MrZakos opened this issue Aug 20, 2019 · 6 comments
Closed

Could not find WWW-Authenticate header in response #10388

MrZakos opened this issue Aug 20, 2019 · 6 comments
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-External The issue is caused by external component(s). WG-Cmdlets-Utility cmdlets in the Microsoft.PowerShell.Utility module

Comments

@MrZakos
Copy link

MrZakos commented Aug 20, 2019 •
edited
Loading

I'm using Skype for Business Online, Windows PowerShell Module , on .net core project I get
"Could not find WWW-Authenticate header in response" , when using .net 4.x project with System.Management.Automation it works fine.

  • running the script inside Powershell(ISE/normal/...) works fine as well.
  • Windows 10
@MrZakos MrZakos added the Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a label Aug 20, 2019
@MrZakos MrZakos changed the title My bug report Could not find WWW-Authenticate header in response Aug 20, 2019
@iSazonov
Copy link
Collaborator

@MrZakos Could you please share a simple repo?

@iSazonov iSazonov added the WG-Cmdlets-Utility cmdlets in the Microsoft.PowerShell.Utility module label Aug 20, 2019
@MrZakos
Copy link
Author

MrZakos commented Aug 20, 2019 •
edited
Loading

@iSazonov

image
this happens on $Session = line

@iSazonov
Copy link
Collaborator

@MrZakos Thanks! If you run PowerShell Core interactive session and execute your script there do you get the same error?

@MrZakos
Copy link
Author

MrZakos commented Aug 20, 2019 •
edited
Loading

seems same error
image

@MrZakos
Copy link
Author

MrZakos commented Aug 25, 2019

@iSazonov so is it
powershell .core bug
or a
SFB-PowerShell-Module problem ?

@iSazonov
Copy link
Collaborator

iSazonov commented Aug 26, 2019 •
edited by unfurl-links bot
Loading

@MrZakos I think you need to move the report to https://github.com/PowerShell/PowerShellModuleCoverage or report directly to SfB team to investigate the compatibility issue.

GitHub
Track issues related to using Windows PowerShell modules with PowerShell Core 6 - PowerShell/PowerShellModuleCoverage

@MrZakos MrZakos mentioned this issue Aug 26, 2019
Open
@MrZakos MrZakos closed this as completed Aug 26, 2019
@iSazonov iSazonov added the Resolution-External The issue is caused by external component(s). label Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-External The issue is caused by external component(s). WG-Cmdlets-Utility cmdlets in the Microsoft.PowerShell.Utility module
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MrZakos @iSazonov