Activities of "m.aliozkaya"

Hi @shedspotter

Can you tell me where you published your project? (Folder, azure or docker)

Hi @winhost

In new version of Devexpress something changed. We will update the document. You can solve your problem by following the solution below.

• Create a CustomWebDocumentViewerController like this

using DevExpress.AspNetCore.Reporting.WebDocumentViewer;
using DevExpress.AspNetCore.Reporting.WebDocumentViewer.Native.Services;

namespace WebApplication1.Controllers
{
    public class CustomWebDocumentViewerController : WebDocumentViewerController
    {
        public CustomWebDocumentViewerController(IWebDocumentViewerMvcControllerService controllerService)
            : base(controllerService)
        {
        }
    }
}

• Go to your [YOURAPPNAME]WebMvcModule
• Add this class dependency injection into PreInitialize function IocManager.Register(typeof(CustomWebDocumentViewerController), DependencyLifeStyle.Transient);

Merhaba,

Power Tools'un yeni versiyonuyla birlikte hata çözüldü, bir sorun olması halinde tekrar iletişime geçebilirsiniz.

Teşekkürler,

Hi @ayoyusuf

I tested it. Normally your DTO should be GLCOGAaccount. Does this problem only occur in DTO's that you produce or in all created DTO's?

Hi @shedspotter

Can you try following steps?

Edit the relevant code in the AuthConfigurer class in the Startup folder as below:

if (bool.Parse(configuration["IdentityServer:IsEnabled"]))
{
    IdentityModelEventSource.ShowPII = true;

    // authenticationBuilder.AddIdentityServerAuthentication("IdentityBearer", options =>
    // {
    //     options.Authority = configuration["IdentityServer:Authority"];
    //     options.ApiName = configuration["IdentityServer:ApiName"];
    //     options.ApiSecret = configuration["IdentityServer:ApiSecret"];
    //     options.RequireHttpsMetadata = false;
    // });

    authenticationBuilder.AddJwtBearer(options =>
    {
        options.Authority = configuration["IdentityServer:Authority"];
        options.RequireHttpsMetadata = false;
        options.Audience = configuration["Authentication:JwtBearer:Audience"];
        options.TokenValidationParameters.ValidIssuers = configuration.GetSection("Authentication:JwtBearer:ValidIssuers").Get<string[]>();
        options.SecurityTokenValidators.Clear();
        options.SecurityTokenValidators.Add(new JwtSecurityTokenHandler
        {
            MapInboundClaims = false
        });
        options.TokenValidationParameters.NameClaimType = "name";
        options.TokenValidationParameters.RoleClaimType = "role";
    });
}

Go to app settings and ValidIssuers like this:

"JwtBearer": {
  "IsEnabled": "true",
  "SecurityKey": "AbpZeroTemplate_8CFB2EC534E14D56",
  "Issuer": "AbpZeroTemplate",
  "Audience": "AbpZeroTemplate",
  "ValidIssuers": [
    "https://localhost:44301/",
    "https://localhost:44302/"
  ]
}

Hello, I couldn't reproduce it. Maybe you missed some steps. Did you run npm run create-bundles after updating?

Could you update this line like this authenticationBuilder.AddJwtBearer("IdentityBearer", options =>

Hello,

We plan to work on .NET MAUI in version 11.4 or later

Hello,

We plan to work on .NET MAUI in version 11.4 or later. We don't plan to work on Blazor in the short term. I would say not this year.

Hi olmy90,

It is only considered to be the same if the protocol, host and port is the same: [Same Origin Policy]

You can update your settings to

"CorsOrigins": "http://*.myURL.de, http://myURL.de:85"