Activities of "maliming"

hi

If your abp version >= 7.4.2, Payment module will support getting the current tenant URL

See https://abp.io/support/questions/6003/Stripe-payment-module-tenantName-resolver-issue

Thanks.

You're welcome. : )

hi

Please share your startup module code?

The correct middleware code/order should be:

app.UseRouting();
var configuration = context.GetConfiguration();
if (Convert.ToBoolean(configuration["AuthServer:IsOnK8s"]))
{
    app.Use(async (context, next) =>
    {
        if (context.Request.Path.Value != null &&
            context.Request.Path.Value.StartsWith("/appsettings", StringComparison.OrdinalIgnoreCase) &&
            context.Request.Path.Value.EndsWith(".json", StringComparison.OrdinalIgnoreCase))
        {
            // Set endpoint to null so the static files middleware will handle the request.
            context.SetEndpoint(null);
        }
        await next(context);
    });

    app.UseStaticFilesForPatterns("appsettings*.json");
}

app.MapAbpStaticAssets();

Thanks.

hi

What is your payment provider?

PayPal or TwoCheckout?

Thanks.

hi

Can you try to set Request.Scheme to https in your API website?

public override void OnApplicationInitialization(ApplicationInitializationContext context)
{
    var env = context.GetEnvironment();
    var app = context.GetApplicationBuilder();

    app.Use(async (ctx, next) =>
    {
        ctx.Request.Scheme = "https";
        await next();
    });     
    
    //...

Thanks.

hi

The Blazorise team response:

Hello! As mentioned in the previous discussion, there’s really no completely secure way to hide the product token in a Blazor WebAssembly application. A determined and technically skilled user could always inspect the compiled assemblies and extract it.

That said, the product token isn’t meant to be secret, unlike the license key that comes with your subscription. The token is time-limited and automatically expires after a certain period. In most cases, Blazorise is used in** line-of-business (LOB)** applications where the risk of token exposure is minimal. Only in large, public-facing apps with many technically savvy users could this become a concern.

As for storage, the best approach is to embed the product token directly in your assembly rather than loading it from an external source at runtime.

hi

I'm unable to reproduce the 499 error.

I have removed this custom code and the error is still there

Can you confirm your custom code has been removed?

Thanks.

thanks, I will check the ABP.7z project.

hi

I am still having the issues with the unsupported media types.

Could you please share your code and debug logs related to this issue?

https://abp.io/support/questions/8622/How-to-enable-Debug-logs-for-troubleshoot-problems

liming.ma@volosoft.com

Thanks.

hi

The ABP string Encryption may not be compatible with Blazor WASM. The browser doesn't support all encryption methods.

I will ask the Blazorise team for this case.

https://blazorise.com/support/issues/338/how-to-protect-our-producttoken-in-wasm-app

Thanks.