Activities of "gterdem"

This may be related to https://github.com/openiddict/openiddict-core/issues/1613

Please contact me via email at galip.erdem@volosoft.com so we can schedule a remote meeting that I can check.

Did you solve this problem?

You may try checking kubectl describe deployment/auth-serverto see if the App__CorsOrigins is properly overwritten.

For testing purposes, you can also remove app.UseCors() midware on AuthServer module OnApplicationInitialization or let any origin.

Ingress caching shouldn't effect the application cors midware. Check if the request hits to server (authserver) even if you disabled CORS for authserver.

Otherwise you can try configuring ingress with CORS configuration to see the difference as in this SO question.

It is not about ingress configuration actually. You need to add https://admineventtix.smartcube.co to CORS settings in the AuthServer (https://autheventtix.smartcube.co) appsettings.json (or override this enviroment variable).

See https://github.com/abpframework/abp-samples/pull/213#issuecomment-1362230680

I have removed the link of the project from the public repository. You shouldn't be adding your commercial templates to public repositories which contains information of your credentials.

Please update your repository settings to private.

Refresh tokens are handled in the same endpoint as token endpoint: https://github.com/abpframework/abp/blob/dev/modules/openiddict/src/Volo.Abp.OpenIddict.AspNetCore/Volo/Abp/OpenIddict/Controllers/TokenController.cs#L32

It seems you have granted refresh_token flow for the application. Can you check if the application also requests the offline_access scope?

IDX20803: Unable to obtain configuration from: 'https://192.168.100.36:44356/.well-known/openid-configuration'.

The error indicates your application can not reach to https://192.168.100.36:44356 public address. We suggest having a public DNS address for the AuthServer since it needs to be reached publicly.

Can you also share the logs from localhost:44374 to make it sure it is up and running?

This is about modules using angular v15. We have fixed this problem and will be corrected in the next release.

You can also make manual changes if you don't want to wait for the next release:

angular.json:

  ...
  "defaultProject": "MyProjectName",
  // ADD schematics
  "schematics": {
    "@angular-eslint/schematics:application": {
      "setParserOptionsProject": true
    },
    "@angular-eslint/schematics:library": {
      "setParserOptionsProject": true
    }
  }

package.json:

    "@angular/animations": "^14.2.3",
    "@angular/common": "^14.2.3",
    "@angular/compiler": "^14.2.3",
    "@angular/core": "^14.2.3",
    "@angular/forms": "^14.2.3",
    "@angular/localize": "^14.2.3",
    "@angular/platform-browser": "^14.2.3",
    "@angular/platform-browser-dynamic": "^14.2.3",
    "@angular/router": "^14.2.3",
===    UPDATE AS BELOW ===
    "@angular/animations": "^15.0.4",
    "@angular/common": "^15.0.4",
    "@angular/compiler": "^15.0.4",
    "@angular/core": "^15.0.4",
    "@angular/forms": "^15.0.4",
    "@angular/localize": "^15.0.4",
    "@angular/platform-browser": "^15.0.4",
    "@angular/platform-browser-dynamic": "^15.0.4",
    "@angular/router": "^15.0.4",
    
"devDependencies": {
...
    "@angular-devkit/build-angular": "^14.2.3",
    "@angular-eslint/builder": "~14.1.2",
    "@angular-eslint/eslint-plugin": "~14.1.2",
    "@angular-eslint/eslint-plugin-template": "~14.1.2",
    "@angular-eslint/schematics": "~14.1.2",
    "@angular-eslint/template-parser": "~14.1.2",
    "@angular/cli": "^14.2.3",
    "@angular/compiler-cli": "^14.2.3",
    "@angular/language-service": "^14.2.3",
    "@typescript-eslint/eslint-plugin": "^5.36.2",
    "@typescript-eslint/parser": "^5.36.2",
    "eslint": "^8.23.0",
    "ng-packagr": "^14.2.1",
===    UPDATE AS BELOW ===
    "@angular-devkit/build-angular": "^15.0.4",
    "@angular-eslint/builder": "~15.1.0",
    "@angular-eslint/eslint-plugin": "~15.1.0",
    "@angular-eslint/eslint-plugin-template": "~15.1.0",
    "@angular-eslint/schematics": "~15.1.0",
    "@angular-eslint/template-parser": "~15.1.0",
    "@angular/cli": "^15.0.4",
    "@angular/compiler-cli": "^15.0.4",
    "@angular/language-service": "^15.0.4",
    "@typescript-eslint/eslint-plugin": "^5.43.0",
    "@typescript-eslint/parser": "^5.43.0",
    "eslint": "^8.28.0",
    "ng-packagr": "^15.0.3",
    

app-routing.module.ts:

@NgModule({
  imports: [RouterModule.forRoot(routes, {})],--> remove `relativeLinkResolution: 'legacy`
  exports: [RouterModule],

tsconfig.json:

"target": "ES2022", ---> Update from ES2020
...
"paths": {
  "@proxy": [
    "src/app/proxy/index.ts"
  ],
  "@proxy/*": [
    "src/app/proxy/*"
  ]
},
"useDefineForClassFields": false --> Add this line

If you follow the DDD guides to set the ID when creating the entity with GuidGenerator instead of leaving to autogeneration, you can simply check the db before inserting it in the event handler. That will prevent same entity to get inserted.