-
Notifications
You must be signed in to change notification settings - Fork 204
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
Using --azure-credential with service principal to publish raises an ERROR You need to be logged in with your corporate credentials to perform this action. #1023
Comments
What task/version are you using to run vsce? It's interesting that verify-pat succeeds but publishing does not.
|
Looks like vsce did not spit out the version. At the time, it should have been the latest version. |
@lszomoru , We finally had a release and so we tried it with the additional logging. |
Also posting the logging here: |
Hi there. I am trying out the new changes to vsce to use a federated service connection to publish to the marketplace and use the --azure-credential switch.
It looks like I am using version 2.31.0 of the vsce toolset.
I first validated using the verify-pat command that using the federated service connection is working:
vsce verify-pat [publishid] --azure-credential
The Personal Access Token verification succeeded for the publisher '[publishid]'.
But.... When I actually try to publish some vsix's for real, I get the following error:
vsce publish --azure-credential --pre-release --packagePath package1.vsix package2.vsix package3.vsix package4.vsix
INFO Publishing '[publishid].package1 v1.0.0'...
ERROR You need to be logged in with your corporate credentials to perform this action.
Does anyone have any ideas as to what is preventing me from publishing to the marketplace using an SP?
Thanks much!
CC: @lszomoru
The text was updated successfully, but these errors were encountered: