When an tenant has 2FA enabled, it's not able for automation API testing. So when a tenant has 2FA enabled, could particular user account has it disabled? If yes, which database table shall I check the value? Is there admin UI for it?
Or do you have any other better idea for backend API automation testing?
Hi,
We noticed that when the application (Micro Service template) is deployed to Azure Kubernetes, Applications insight show the application throw 401 exception, the error details as below:
Failed to refresh remote claims for user: ae264b2c-aa17-336e-500c-3a0f39672a03 Volo.Abp.AspNetCore.Authentication.JwtBearer.DynamicClaims.WebRemoteDynamicClaimsPrincipalContributorCache
Do you have any clue about the error?
Thanks,
We have a distributed lock code like this, but it seems, the second thread didn't wait till first thread finished db insert
await using var handle = await _distributedLock.TryAcquireAsync($"api-lock", TimeSpan.FromMinutes(5));
try {
if (handle != null)
{
var rtCertifcate = _apiClient.CallApi (); //external API
if (!string.IsNullOrWhiteSpace(rtCertifcate ))
{
//insert into database for rtCertifcate
return rtCertifcate
}
}
else
{
// If we can't acquire the lock, fall back to database lookup
Logger.LogWarning("....");
}
}
catch
{
}
//Code read certificate from database
ABP 8 MicroService architect, when backend throw an UserFriendlyException, the message not showing in Angular client, instead an Internal error message is shown
ABP framework 9, the customize Login page can remove self registration link, how to disable this feature so that swagger API also has no this API (api/account/register)
Since our EF core Mapping use some syntax not supporting SqlLite, we need to mock each repository / app service when write test code for an AppService. However, while doing this way, AppService's Logger is null and throw exception for all places using it in the AppService. I guess any place using CurrentUser, CurrentTenant, CurrentUnitOfWork would also throw null reference exception
After upgrade the application 4 to ABP 8, the new user doesn't work with Single Sign On with Azure AD. Application: No Multi-tenancy, Layered application
All existing users, the login looks fine. From AbpUserLogin table we can tell the provider is Azure AD. However, when create a new user via admin UI (enter user info and assigned roles), the AbpUsers and AbpUserRoles table data looks good. But when login into the application via single sign-on from Azure AD, the application is navigated to user registration page.
We have such use cases: Micro serivce A publish a event to distributed bus (set userId property in event) , Micro server B handle the event, Micro service B need to call Micro Service C's API to get some data, that API is not anonymous, in this case, Service C would reject the API call because of missing access token.
How to handle such case?
Our UAT environment throw this exception when a batch messages (around 2k) sent to distributed event bus: " MessageTemplate Cannot access a disposed object. Object name: 'RabbitMQ.Client.Impl.AutorecoveringModel'. SourceContext Volo.Abp.RabbitMQ.RabbitMqMessageConsume
System.ObjectDisposedException: at Volo.Abp.RabbitMQ.RabbitMqMessageConsumer+<HandleIncomingMessageAsync>d__46.MoveNext (Volo.Abp.RabbitMQ, Version=8.2.3.0, Culture=neutral, PublicKeyToken=null)
"
I noticed even in ABP 8 application (Micro Service), Abp Audit Log has a lot of exception:
/api/account/my-profile [ { "code": "Volo.Authorization:010001", "message": "Authorization failed! Given policy has not granted.", "details": null, "data": {}, "validationErrors": null } ]