Publishing Site on AWS Fargate

Questions
1

we are publishing our website that we have developed over Umbraco 15, so far we have developed all the pages and populated the contents. all this have been done using a SQL RDS on AWS and where the pages are on our local computer. it works just fine by visiting https://localhost/umbraco, however when porting it to docker over AWS fargate the backend page doesn’t display correctly :grimacing: and shows :
“error:invalid_request
error_description:The specified ‘redirect_uri’ is not valid for this client application.
error_uri:https://documentation.openiddict.com/errors/ID2043

we tried multiple ways to resolve it by modifying the appsettings.json

"Umbraco": {
  "CMS": {
    "WebRouting": {
      "UmbracoApplicationUrl": "https://site.com/"
    },
    "Security": {
      "BackOfficeHost": "https://site.com/"
    }
  }
},

anyone have encountered this issue and managed to resolve it. please let me know what further to look at? :

2

The issue is that you are using the same database for multiple instances. For OpenId, a redirect_url is required and Umbraco handles this by registering the redirect_url of the first request is receives in the database. When you use that database from another URL, you will get the error you described.

See this topic:

3

thanks Luuk,
so now that we have developed our website and whish to proceed with it, what can we do to fix the redirect_url?

4

If you have access to the database, then you can modify the entries in the umbracoOpenIddictApplications table.

But be very careful with this ,as changes here could impact the platform.

There’s a bit more interesting information on the various OpenID issues and workarounds here:

5

Setting the “BackOfficeHost” should override whatever the database thinks is the application URL and is used directly in the OpenId manager. You should set the hostname that the Docker instance actually sees as the host, for example it may be “localhost” or something similar.

I think the address should not end with a forward slash as that seems to be hardcoded in many places in the source code of Umbraco, so I would honestly try setting it to a few different values to see if that solves the problem:

"Umbraco": {
  "CMS": {
    "Security": {
      "BackOfficeHost": "https://site.com"
    }
  }
},

or

"Umbraco": {
  "CMS": {
    "Security": {
      "BackOfficeHost": "http://localhost"
    }
  }
},

You can more or less deduce how it is used in this area of the source code to set the allowed redirect URLs:

1 Like