Hi,
You can try this:
AuthServerUrl/api/account/profile-picture/3a56f8d5-bf2b-ba87-433d-3a1130099bff
We have released the 8.1 stable version, could you upgrade your project and try again
Please try
// inject IOptions<AbpIdentityOptions>
protected IOptions<AbpIdentityOptions> AbpIdentityOptions { get; }
.....
await IdentityOptions.SetAsync(); // set option first.
await _identityUserManager.AddPasswordAsync (userdetails,input.Password)).CheckErrors()
Hi,
Although the token has expired, the authorization server login status has not expired, so when you refresh the page it will challenge again and log in directly.
no the IdenttiyUserManager don’t need permission you are using the IdentityUserAppService and it required a permission. That’s why you get the exception
Could you share the full steps to reproduce, thanks.
Hi,
That makes sense; good luck to you.
This is very strange, but I don't know your project details, and there are no reproducing steps.
Can I check it remotely?
Hi,
No, ABP does not provide such functionality.
You can search it on Google: https://www.google.com/search?q=aspnet+core+encrypt+response&oq=aspnet+core+encrypt+response
And I think the main question of the ticket is solved, can we close this? Thanks.
If we then look in the database we can see that exactly 100 BackgroundJob rows are IsAbandoned = true with RetryCount = 1 and these records thus never made it to our AcmeBackgroundWorker. So what has picked up this data? Why were they flagged as unprocesable?
I just think there is another application that is executing background jobs