You can modify your login button with returnUrl=/Dashboard
.
Okay, we'll try to reproduce this issue on v4.3.2 and let you know about the progress.
ABP uses permission-based authorization by the Permission Management Module for in-application authorization. You can extend the permission module as your business need. If you have custom business logic on permissions like overriding permission with custom policy or permission depending on condition/feature you can check Authorization documentation.
For authentication between applications, we use Identity Server Management Module.
It seems like a business logic with multiple ways to achieve it.
You can add ICountry
marker interface for Items and add a custom data filter checking if ICurrentUser
has the country custom claim when the user logs in.
Sorry, I don't follow. Can you explain your issue in detail?
To use Data Filtering, Country
should be a property in your Entity. It should be an existing field to be queried on the database level.
What will you use the custom claim against on the database? I suppose there is a corresponding field in an entity to check this field.
Can you explain more about your intentions like how do you implement ICountry
or how do you want to query?
What is the result when you run npm -v
PS C:\Users\passp> npm -v npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. 8.11.0 PS C:\Users\passp>
The dev-certs is only working on domain localhost, can you share the full logs?
PS C:\Users\passp> cd D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS PS D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS> .\etc\dev-cert\create-certificate.ps1 Trusting the HTTPS development certificate was requested. A confirmation prompt will be displayed if the certificate was not previously trusted. Click yes on the prompt to trust the certificate. [1] Listing certificates from CurrentUser\My [2] Found certificates: 1 certificate 1) D6A8FF9E96302EC89AC86045A5F8EBC6EAA62D35 - CN=localhost - Valid from 2022-06-02 15:18:41Z to 2023-06-02 15:18:41Z - IsHttpsDevelopmentCertificate: true - IsExportable: true [3] Checking certificates validity [4] Valid certificates: 1 certificate 1) D6A8FF9E96302EC89AC86045A5F8EBC6EAA62D35 - CN=localhost - Valid from 2022-06-02 15:18:41Z to 2023-06-02 15:18:41Z - IsHttpsDevelopmentCertificate: true - IsExportable: true [5] Invalid certificates: no certificates [6] Finished listing certificates. [1] Listing certificates from LocalMachine\My [2] Found certificates: no certificates [3] Checking certificates validity [4] Valid certificates: no certificates [5] Invalid certificates: no certificates [6] Finished listing certificates. [8] Filtered certificates: 1 certificate 1) D6A8FF9E96302EC89AC86045A5F8EBC6EAA62D35 - CN=localhost - Valid from 2022-06-02 15:18:41Z to 2023-06-02 15:18:41Z - IsHttpsDevelopmentCertificate: true - IsExportable: true [9] Excluded certificates: no certificates [14] Valid certificates: 1 certificate 1) D6A8FF9E96302EC89AC86045A5F8EBC6EAA62D35 - CN=localhost - Valid from 2022-06-02 15:18:41Z to 2023-06-02 15:18:41Z - IsHttpsDevelopmentCertificate: true - IsExportable: true [15] Selected certificate: D6A8FF9E96302EC89AC86045A5F8EBC6EAA62D35 - CN=localhost - Valid from 2022-06-02 15:18:41Z to 2023-06-02 15:18:41Z - IsHttpsDevelopmentCertificate: true - IsExportable: true [23] Saving certificate 'D6A8FF9E96302EC89AC86045A5F8EBC6EAA62D35 - CN=localhost - Valid from 2022-06-02 15:18:41Z to 2023-06-02 15:18:41Z - IsHttpsDevelopmentCertificate: true - IsExportable: true' to localhost.pfx with private key. [27] Writing the certificate to: localhost.pfx. [29] Trusting the certificate to: D6A8FF9E96302EC89AC86045A5F8EBC6EAA62D35 - CN=localhost - Valid from 2022-06-02 15:18:41Z to 2023-06-02 15:18:41Z - IsHttpsDevelopmentCertificate: true - IsExportable: true. [45] Adding certificate to the trusted root certification authority store. [0] Event 30 was called with 1 argument(s), but it is defined with 0 parameter(s). [30] A valid HTTPS certificate is already present. The certificate was exported to D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\localhost.pfx PS D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS> dotnet dev-certs https --clean Cleaning HTTPS development certificates from the machine. A prompt might get displayed to confirm the removal of some of the certificates. HTTPS development certificates successfully removed from the machine. PS D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS> dotnet dev-certs https --trust Trusting the HTTPS development certificate was requested. A confirmation prompt will be displayed if the certificate was not previously trusted. Click yes on the prompt to trust the certificate. The HTTPS developer certificate was generated successfully. PS D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS>
Did you install that certificate? Your problem seems to be related to localhost certification. You can check Microsoft Generate self-signed certificates with the .NET CLI docs for more information.
Can you try it on version 5.3 template?
If you didn't alter the Clock Skew, it won't be a healthy test. Since clock skew defaults to 5 mins, I would suggest setting access token to 6 mins for testing. Or altering the clock skew.
I built A new Form And I but Blazorise textbox inside the Form in the end added button to save data as you see in the picture
And in Another case I built A method to get list of data by id on the debugger I got the same problem
Sorry, we couldn't understand.
Can you explain step by step what you are trying to do and how can we reproduce?