This issue is related to upgrading from a version prior to 2022.1 to 2022.2.
During the upgrade process or the installation process of Devolutions Server, we must provide an Access URI. This URI is a redirect URL that is used by the OAuth system and redirects the authentication traffic to the Access URI.
Settings
- In the Devolutions Server Console, go to Server - Edit - IIS.
- Enter the Access URI in the text field following the format provided in the Scenarios.
The Access URI is case sensitive and must respect the certificate host name. Ensure that there is no '/' at the end of the URL.
There can be more than one Access URI. Click the ellipsis button to add or manage additional Access URI.
- Click OK.
Scenarios
Multiple format can be set and you must choose the right one.
- The Devolutions Server instance is available only internally and is hosted on one server. Then the Access URI should be set with the FQDN of the machine and ends with the Devolutions Server IIS Application if it is not installed on the root of the web site. https://myservername.mydomain.loc/dvls
- The Devolutions Server instance is available externally on the web or behind a Load Balanced environment. Then the Access URI should be set with the URL you use to reach the instance from internet. https://myorganisation.com/dvls
- If Devolutions Server is installed at the root of the IIS web site. Then the Access URI should only be the FQDN of the machine. https://myorganization.com
- If Devolutions Server is using a non-standard port (80 for http, 443 for https). Then the Access URI will need to contain the port number after a colon. https://myorganization.com:4443/dvls