Activities of "terrycullen"

Hi,

Minor improvement:

1. Please trim URLs pasted into the Identity Server configuration screen.
2. When copying URLs from an existing Identity Server configuration, they are padded with whitespace... please make them not padded for easier copying.
3. Please add a 'Duplicate' button to aid in copying Identity Server clients.

The problem is that if the URL in the 'RedirectUrl' field has some white space on it, it creates reallly hard to identify issues.

Thanks!

Terry

Hi,

I've got a stock instance of ABP Commercial running in a docker container on port 80. I've got another docker container running Caddy (HTTPS web server) which proxies the web requests to ABP.

It all works fine except that identity server doesn't know that the app is running with HTTPS (port 443) so the discovery document ( https://stage.example.com.au/.well-known/openid-configuration ) is incorrect as it shows HTTP (not HTTPS) based links.

I've read that you can configure identity server to either use the X-Forwarded-For header to determine the protocol or use an explicit configuration value to set the HTTPS links (https://github.com/IdentityServer/IdentityServer4/issues/1331) but I can't see where I'd go about configuring that in ABP.

Terry

Thanks! Solution 1 worked.

Hi,

I'm trying to deploy the first instance of our application to our development server using docker containers. It's based on the project created from an untiered MVC pro template.. I have moved it to using Postgres instead of SQL Server and it works fine on my dev laptop (Mac).

I'm logged into a shell on a linux VM with not much more installed but docker/docker-compose.

I've previously built the docker containers (app & migrator) and have deployed the built containers to AWS ECR.

I run the below docker command to run the migrations -

docker run \
    --rm -i --network=web-network \
    -v "$(pwd)/migratorsettings.json:/app/appsettings.json" \
    -v "$(pwd)/data/log:/app/Logs" \
    -e "ASPNETCORE_ENVIRONMENT=Development" \
    <our aws acc id>.dkr.ecr.ap-southeast-2.amazonaws.com/web/migrator:Development-0000000006

Which produces the following error:

[03:05:38 ERR] ABP-LIC-0008 - License check failed for 'Volo.Abp.LanguageManagement.Domain.Shared-v2.3.0.0'.
You need to log in using the command `abp login <username>`.
For more information, contact to license@abp.io.

My assumption is that if I've provided an appsetting.json file that contains the AbpLicenceCode to the web server I've deployed this to, it should not need to login to ABP. I've included the file below and redected the secrets:

{
  "ConnectionStrings": {
    "Default": "Host=<redacted>;Database=<redacted>;Username=<redacted>;Password=<redacted>;Port=5432;Pooling=true;"
  },
  "IdentityServer": {
    "Clients": {
      "Web_Web": {
        "ClientId": "Web_Web",
        "RootUrl": "https://<redacted>.com.au/"
      },
      "Web_App": {
        "ClientId": "Web_App"
      }
    }
  },
  "AbpLicenseCode": "<redacted>"
}

I know that the docker container can find my appsettings.json because if I make the json invalid the migrator errors out saying that the JSON is invalid.

So, my question is - Is having the AbpLicenceCode parameter set in the appsetting file enough to get licencing working? If so, what might be wrong with this?

Terry