Devolutions ForumDevolutions Forum

VS Code Extension: Connections fails if the API Token has too many roles / the API Token has too many chars?

VS Code Extension: Connections fails if the API Token has too many roles / the API Token has too many chars?

avatar
(anonymous user)

Hello

First, I think this is an important note about the VS Code plugin:

  • It would be very useful if users could find information on how to configure the API token so that the connection between the VS Code plugin and PowerShell Universal works perfectly.
  • For example: How should “System Identity” and “Roles” be configured?
  • The best place to document this information would probably be the Plugin Marketplace Info Page: PowerShell Universal - Visual Studio Marketplace

Secondly, I think I found a bug in the VS Code plugin:

  • The more roles an API token has, the longer the token becomes / the more characters it has.
  • If an API token has too many roles (and the token becomes too long), the connection from the VS Code plugin to PowerShell Universal does not work. As a test, I generated a token that had all roles.

Thanks a lot, kind regards,
Thomas

All Comments (3)

avatar

I have created this issue:

github.com/ironmansoftware/powershell-universal

avatar
Secondly, I think I found a bug in the VS Code plugin:
  • The more roles an API token has, the longer the token becomes / the more characters it has.
  • If an API token has too many roles (and the token becomes too long), the connection from the VS Code plugin to PowerShell Universal does not work. As a test, I generated a token that had all roles.

Thanks a lot, kind regards,

Thomas

I have added this Issue, too:

avatar
pss127

This is not an inherit bug to VS Code I am thinking. We hit an issue with cookie limit 4093 and group membership. Basically, roles would act the same way. If the persons cookie limit is hit with the return then yeah the claim returned would look empty. You would want to limit the scope of your roles returned.