Skip to content

Error running command local-extension.login: Personal Access Token is required #349

Open

Description

@michaelhenningersrb

Hello,

I wanted to login to my BAS with the VSCode Extension.
It worked already a few days ago.

Now I got the following error:

image

Any ideas to solve this issue?

Activity

  1. dimdusart commented on Feb 10, 2025

    @dimdusart

    Hello,

    I actually have the same issue. Whether I want to connect to any landscape (enterprise or internal BAS), I get this error about PAT required.

    It doesn't want to connect correctly to BAS :

    Image

    Image

  2. alex-gilin commented on Feb 11, 2025

    @alex-gilin
    Contributor

    @michaelhenningersrb, @dimdusart , Is the issue still happening? This can happen when you have multiple instances of VSCode open. To resolve this, you can either close the other open instances but keep only the one you want to authenticate with, or make sure the instance that started the authentication process is focused.

  3. phdaucourt commented on Apr 3, 2025

    @phdaucourt

    In my case, I get the "Personal Acces Token is required" error when i try to copy-paste the authentication url in my browser from the login popup.

    But if I choose the "Open" button in the login popup instead of copying-pasting the url, it works like a charm.

    It sounds like bug, doesn't it?

  4. alex-gilin commented on Apr 6, 2025

    @alex-gilin
    Contributor

    @phdaucourt why do you need to copy paste the authentication url ? can you elaborate on your process?

  5. sammok83 commented on Feb 15, 2026

    @sammok83

    I'm now getting this since this Monday. Was ok last week.

    Image

    I've already signed out of my profile in vscode

  6. alex-gilin commented on Feb 16, 2026

    @alex-gilin
    Contributor

    @sammok83 It looks like the issue is that you have multiple instances of VS Code open. Have you tried closing all instances of VS Code, leaving only the one you want to authenticate with?

  7. rafaelcaziraghi commented on Mar 2, 2026

    @rafaelcaziraghi

    Hello!
    I'm having exactly the same issue, and I'm sure I have only one instance with status "running". Any suggestions I could try?
    Thank you.

  8. alex-gilin commented on Mar 3, 2026

    @alex-gilin
    Contributor

    @rafaelcaziraghi : The authorization process may have stalled. To resolve this issue, please restart VS Code by terminating all active VS Code processes and relaunching your workspace. I hope this works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions