Issues upgrading DVLS to 2025.1.9.0

Issues upgrading DVLS to 2025.1.9.0

avatar

Hi everyone,

I'm currently running DVLS version 2024.3.8.0, along with authentication via Entra ID. All is working correctly.

Today I attempted to upgrade DVLS to version 2025.1.9.0. After the upgrade, the DVLS Scheduler service wasn't able to start anymore.
I rolled back to the last Stable release, 2024.3.17.0, which was successful and the Scheduler service was running again.
However, this broke the authentication via Entra ID.
The following error was shown in the logs:
OAuthTokenEndpointException - OAuth token endpoint error: {"error":"invalid_client","error_description":"AADSTS700025: Client is public so neither 'client_assertion' nor 'client_secret' should be presented."}

I saw the same error here:
DVLS with EntraID App Proxy experiencing OAuth token endpoint error
However, there is no update on this thread or a solution.

So I manually redownloaded DVLS version 2024.3.8.0 and downgraded to this one. And everything is up and running again.

However, I also noticed an issue with licensing. During the upgrade, my Gateway license was invalidated. We've checked our firewall logs, adjusted some rules and the Gateway license is usable once again.

Also, while trying to be prepared for the DVLS upgrade, I've upgraded RDM to version 2025.1.38.0.
When DVLS was back online, my RDM license was invalidated.
Rolling RDM back to 2024.3.31.0 fixed the licensing issue.

I saw in the release notes that, since DVLS 2025.1.3.0, the license validation URL was changed.
We've checked together with my colleagues and the connection is allowed (no blocked traffic) to the new URL. But still, the license did not get validated.

Any help in clarifying the issue will be greatly appreciated!

All the best,
Victor.

avatar

Recommended Answer

OK, so I fixed it :)

  1. Issue with the update: seems there were some .NET prerequisites that weren't available. I've repaired all installations and that fixed the issues.
  2. Issue with authentication: I've checked multiple times to ensure that the configuration in Entra ID was correct. And it was.

In the end, I just removed the Redirect URI and added it again. That solved the issue.

Leaving this here, maybe it helps others in the future.

Thank you!

All Comments (2)

avatar

OK, so I fixed it :)

  1. Issue with the update: seems there were some .NET prerequisites that weren't available. I've repaired all installations and that fixed the issues.
  2. Issue with authentication: I've checked multiple times to ensure that the configuration in Entra ID was correct. And it was.

In the end, I just removed the Redirect URI and added it again. That solved the issue.

Leaving this here, maybe it helps others in the future.

Thank you!

avatar

Hello!

Thanks a lot for the feedback!
We're glad you figured it out, and thanks for posting the solution.

Best regards,

Alex Belisle