forcedotcom / try-acb-feedback

BSD 3-Clause "New" or "Revised" License
3 stars 1 forks source link

Windows - Desktop IDE / VSCode extension - Can't authenticate git push #51

Closed s0up2up closed 11 months ago

s0up2up commented 12 months ago

Describe the bug

To Reproduce Steps to reproduce the behavior:

  1. Load VS Code and Open MuleSoft Anypoint Code Builder extension (see Screenshot 4)
  2. Click "Design an API" and enter Project details
  3. Make changes to a RAML file
  4. Commit changes via Source Control panel (or git CLI) then sync changes (git push)
  5. Get prompted for credentials via Windows Git Credentials Manager, and enter them in
  6. Git output shows a failed authentication message

Expected behavior Be able to push stagged commits to Anypoint platform.

Impact Crash/Data Loss - Unable to deploy changes (i.e., RAML changes) to Anypoint platform.

Frequency Always

Screenshots/Recordings

Please complete the following information:

Additional context Add any other context about the problem here.

github-actions[bot] commented 12 months ago

Hello @s0up2up , thank you for submitting an issue - we appreciate your time. Our product team will take a look and give you an update as soon as we can. We aim for a 3 day response time but please be patient if we take longer.

jimdandrews commented 12 months ago

I had the same problem with as Brendan. I even tried to redirect my Design Center to my own GitHub repo and use those credentials but that didn't work either. I'm wondering if it's a token thing and we need to use connected apps or something. but it pulls down existing designs just fine.

Also, if i create a new Design project from within ACB, it gets created in Design Center (an initial version) but then any changes i make i can't push (for the same reason as above). but that initial creation doesn't ask fro credentials.

SantiSuarezMS commented 12 months ago

Hi @s0up2up !! We had a similar issue reported where an attempt to push will fail on the first attempt with a401 but subsequent tries would go through (as long as you're already logged in to Anypoint). Could you please try this and let me know if you can push?

  1. Load VS Code and Open MuleSoft Anypoint Code Builder extension
  2. Click "Design an API" and enter Project details (log in to Anypoint if prompted)
  3. Make changes to a RAML file
  4. Commit changes via Source Control panel (or git CLI) then sync changes (git push)
  5. Get prompted for credentials via Windows Git Credentials Manager, ignore and close Git Credential Manager
  6. Git output shows a failed authentication message
  7. Attempt to push changes again

Let me know if this allows you to push your changes, this is not only a workaround, but also I want to check if it is related to an internal bug we already addressed.

Thanks in advance!

cc @simoneegeib

simoneegeib commented 12 months ago

Also, which OS are you on?

s0up2up commented 12 months ago

@SantiSuarezMS - looks like that worked, ignoring the Git Cred Mgr prompt seems to allow it to push the changes as I would expect.

image

Saying that, the source control panel in VSCode didn't track the changes, it had to be actioned via the Git CLI manually.

@simoneegeib - Fully patched Windows 11 Enterprise (v 10.0.22000 Build 22000, managed via Intune policies (so no local Admin privileges)), w/ the following versioning on VS Code: image

simoneegeib commented 11 months ago

Thanks for getting back to us. This issue has now been fixed and will be available in the new release next month