Michael Taylor

Who refreshes this like every hour? https://devolutions.net/powershell-universal/release-notes/ is it just me :P

@Matthew Morrow

Nah not just you

Its halted my upgrade plans to the "prod" instance for a bit, hoping this gets fixed quick and I don't have to do another round of paperwork to reschedule the main upgrade 🙏

Seeing the same thing but with implicit secrets that one of our scripts call... Same IIS setup but no LB

what is going on?

I was kind of happy meanwhile using the ironmansoftware.powershell-universal 2026.2.3

This morning vscode told me the extension is deprecated and I should "Migrate" to the Devolutions version.

So I tried, and got devolutionsinc.devolutions-powershell-universal 2026.1.1

And that version has the old 5.x look and feel again and is not any better.

So I installed the "deprecated" version again, that funny enough holds the highest version number.

code --install-extension ironmansoftware.powershell-universal

Sorry to hijack this support request but genuinely echoing @deroppi words here, what's going on here?

The extension to migrate to looks like it was last updated 6 months ago according to the marketplace and the new "Devolutions, Inc" publisher on the marketplace is unverified with just this extension.

Is this the genuine new extension and publisher or should we be avoiding this migration? There has not been any news of a migration ahead of time so this is out of the blue and highly suspicious.

A bit of a big ask, but would be a nice to have, not critical.

Currently for API access a user either has to supply some credentials or an API token that has been pre-made ahead of time. But for OIDC based deployments only a pre-made API key is the only real option, which means you have to login to the admin ui, make the token (preferably short lived) and then put that back into your console securely.

Instead for this, similar to how HashiCorp vault handles this, we're asking if Connect-PSUServer could activate a OIDC flow, whereby a flag like

Connect-PSUServer -ComputerName 'https://some.psu.server.domain.com' -OIDCMakeToken

Could exist, that provides a browser link, the user goes to the browser link, goes through their OIDC flow configured in PSU and then lands at a consent screen in PSU asking for authorization to make a App Token for your current powershell session (limited by some short-lived expiry and tied to the user account that completed the flow).

This in total will reduce the amount of screens an OIDC user has to go through to use the Universal module while utilizing as much of the current systems as I can think off to help with dev time.

To take this a step further, this could also be tied to permissions, so that only certain users would be able to use the OIDC flow to quickly generate a App Token and/or it being a separate permission means that people can generate their own but not be permitted to control others app tokens or system app tokens because they wouldn't have access to the main app tokens area.

Anyway, sorry, lots of words.

The Tl;Dr:

Have new flag on Connect-PSUServer to allow a user to make a API Token from the terminal with minimal browser interaction while still being secure.

Would love to know what you think.

In PSU Triggers, you are unable to set the parameters that a trigger provides to its trigger script,

meaning that if I want to use the same trigger script but with different parameters to the default then I must copy the entire script and change the defaults to those parameters, even though the same logic is running, it just needs different parameters.

This would help with script reuse for similar resulting triggers but with the goal of sending things to other destinations.