We are trying to connect to the PSU server after switching from Windows auth to OIDC but are running into the following error when trying to run Connect-PSUServer. " [Response could not be deserialized to JSON" We’ve tried changing Connect-PSUServer to use the app token but still have the same err…

I am dealing with this same issue. I thought it was just me. @adam { "Kestrel": { "Endpoints": { "HTTPS": { "Url": "https://*:443", "Certificate": { "Subject": "localhost", "Store": "My", …

I know we have integration tests to validate this behavior works v5 as of 5.5.5 but I wouldn’t be surprised this is still an issue in v4. I will open an issue.

Thanks Adam, I think at this point we should be looking at migrating to v5

I’m not sure and will have to try on v4. It could be an order of operations thing within PSU that is causing the problem and might not work with a bug fix.

Connect-PSUServer after switching to OIDC

PowerShell Universal

mikedhanson July 15, 2025, 7:12pm 6

@adam

is there a work around or something else I could do to get this to work while being on v4 still?

Topic		Replies	Views
Connect-PSUServer : Response could not be deserialized to JSON: GET https://universal.companyname.com/api/v1/accessible PowerShell Universal	13	666	August 15, 2023
Connecting to an endpoint when using OIDC / Entra ID PowerShell Universal	0	36	April 10, 2025
PSU Node keeps enabling OIDC when connecting to SQL PowerShell Universal	0	203	November 15, 2023
OpenID Connect with Certificate Credentials? PowerShell Universal	8	775	May 17, 2024
OIDC - Broken with 5.0.0 PowerShell Universal	11	447	August 28, 2024

Connect-PSUServer after switching to OIDC

Related topics