hi
We have no experience in this case.
You can implement such a feature in EF Core, and then ABP will be automatically compatible with it, because ABP completely uses EF Core as the data source.
If you have any problem with this feature and abp. You can give feedback here.
Thanks.
hi
This is Chrome's behavior. It tries to get all map files. I think you can ignore it.
Or you can copy node_modules/moment/min/moment.min.js.map
to your libs folder.
hi
AbpAuditLogActions Table Detail;
The logs exit in the Logs\Logs.txt
file.
Can you delete this file and reproduce the problem share share it.
Thanks
hi
Even though there is a "selectedTenant" query parameter, the tenant is not selected.
You can add a new tenant resolver to get tenant from ReturnUrl
https://abp.io/docs/latest/framework/architecture/multi-tenancy?_redirected=B8ABF606AA1BDF5C629883DF1061649A#default-tenant-resolvers
hi
The authentication request was rejected because invalid scopes were specified: ["role"].
The scope
for the role is roles
.
scope: 'offline_access openid profile roles email phone PartnerPortal',
hi
You can use IPermissionChecker
to check the permissions of the current users in microservices.
namespace Volo.Abp.Authorization.Permissions;
public interface IPermissionChecker
{
Task<bool> IsGrantedAsync([NotNull] string name);
Task<bool> IsGrantedAsync(ClaimsPrincipal? claimsPrincipal, [NotNull] string name);
Task<MultiplePermissionGrantResult> IsGrantedAsync([NotNull] string[] names);
Task<MultiplePermissionGrantResult> IsGrantedAsync(ClaimsPrincipal? claimsPrincipal, [NotNull] string[] names);
}
You can see the requests are taking too much time, and return 499
The request must be blocked at some step.
Request finished HTTP/1.1 GET https://api..com/api/app/notifications/get-user-notification - 499 null null 59171973.8186ms
Request finished HTTP/1.1 GET https://api..com/api/abp/application-configuration?includeLocalizationResources=false - 499 null null 59146523.8819ms
Request finished HTTP/1.1 GET https://api..com/api/app/dashboard/recent-newsletters?count=20 - 499 null null 59170152.7414ms
You can change the log level to .MinimumLevel.Debug()
so we can get more information next time when this problem occurs again.
public class Program
{
public async static Task Main(string[] args)
{
IdentityModelEventSource.ShowPII = true;
IdentityModelEventSource.Logger.LogLevel = EventLevel.Verbose;
var wilsonTextLogger = new TextWriterEventListener("Logs/identitymodel.txt");
wilsonTextLogger.EnableEvents(IdentityModelEventSource.Logger, EventLevel.Verbose);
Log.Logger = new LoggerConfiguration()
.MinimumLevel.Debug()
.MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning)
.Enrich.FromLogContext()
.WriteTo.Async(c => c.File("Logs/logs.txt"))
.CreateLogger();
If your app uses OpenIddict you can get a token from connect/token
endpoint
https://abp.io/support/questions/6747/How-to-generate-access-token-in-backend-only-with-user-email
Great