Hi,
2025-04-11 05:59:08.993 +00:00 [INF] Client validation failed because 'https://saas-fe-bcc7btejdefpf6gy.canadacentral-01.azurewebsites.net' was not a valid redirect_uri for DiyarSaaS_App. 2025-04-11 05:59:08.993 +00:00 [INF] The authorization request was rejected because the redirect_uri was invalid: 'https://saas-fe-bcc7btejdefpf6gy.canadacentral-01.azurewebsites.net'.
I think this is the reason, you can check the appsettings and the database table to check if redirect_uri is correct
Hi,
Yes, this may be related to your configuration. But we need to check the logs.
I guess the log may be disabled in production, you can check it in the Program class
.
Hi,
Maybe you can try using Kudu to download logs https://learn.microsoft.com/en-us/azure/app-service/resources-kudu
Hi,
Try get log from this.
Hi,
I'm asking for the application logs, not the web server.
Hi,
The latest version is 9.1.1, you can try upgrading to 9.1.1.
And what's your Blazorise version?
Hi,
Could you share the full logs?
Hi
Can you confirm that our goal is to get here
Oh, this is used to redirect to the external provider(azure ad), when you disable local login and only configure an external login provider, it will directly redirect.
And when some tenant is using AzureAd we don't want to let users to self register locally. So would this be wrong? "Here is the logic: you have to enable local login and self-register both."
This issue has been fixed, you can upgrade your abp version to 8.3.1
I'm trying to figure out logic here. Why this is returning true and not false?
ABP allows external users to confirm their information(username, email address), which you can understand as external user registration.
Hi,
To achieve this, you can override the account layout and login pages.
Get the source code
You can use the ABP Suite to download the leptonx and account pro source code.
Override page
Copy pages to your project (Authserver) using the same folder path.
Here is the document how to override page: https://abp.io/docs/latest/framework/ui/mvc-razor-pages/customization-user-interface
Hi,
Here is the logic: you have to enable local login and self-register both.
You can override the CheckSelfRegistrationAsync method if you needed
