hi
I checked, the problem should DataProtectorTokenProvider.
You can inject the UserManager
in your identity server project, then call GenerateEmailConfirmationTokenAsync
and ConfirmEmailAsync
to check if the function is works.
public IdentityUserManager UserManager { get; set; }
public virtual Task<string> GenerateEmailConfirmationTokenAsync(TUser user);
public virtual async Task<IdentityResult> ConfirmEmailAsync(TUser user, string token)
hi
Can i check it remotely? https://zoom.us/j/92883778530?pwd=SHRCbEd0UndjYzc5R2szVlJiLzJzQT09
Will it work if identity server and api are run on one instance?
Sorriy, but I could not find what you wrote about on page provided by link. Can you please send link to source of project you talking about?
If you create an app project, you will find a HttpApi.Client.ConsoleTestApp
project, which will call the application service that requires authorization. It is done automatically in the ConsoleTestApp
project. You can think of it as event handler or background job/work.
In a monolithic application, it will directly use application services, and in tiered or microservices, it will automatically call web api.
In short - I want CurrentUser and CurrentTenant will be provided before event handler execution
I don't fully understand, can you share some code?
hi vijay.nallala
We can discuss here. Please reply if you have any questions.
I think everything is ok locally, right?
Can you add below code to identity server and api?
public void ConfigureServices(IServiceCollection services)
{
var redis = ConnectionMultiplexer.Connect(configuration["Redis:Configuration"]);
context.Services.AddDataProtection()
.PersistKeysToStackExchangeRedis(redis, "Your-DataProtection-Keys")
.SetApplicationName("YourAppName");
}
hi
The tenant switch component show logic:
MultiTenancyOptions.Value.IsEnabled &&
(TenantResolveResultAccessor.Result?.AppliedResolvers?.Contains(CookieTenantResolveContributor.ContributorName) == true))
hi @broctune
Can you share the project with me? liming.ma@volosoft.com
hi
You can try this method in Angular.
this.authService.navigateToLogin();
hi christophe
Since Angular can customize Accept-Language
, you don't need to remove AcceptLanguageHeaderRequestCultureProvider
in backend.
https://github.com/abpframework/abp/pull/9162