You can use HTTPS redirection at OnApplicationInitialization:
...
app.UseHsts();
app.UseHttpsRedirection();
...
that should redirect incoming HTTP to HTTPS. However, I am not sure if this will work if you have a proxy (or web-server configuration) that redirects incoming HTTPS to HTTP.
Do you have any proxy or web-server configuration between your application and azure that can be redirecting HTTPS to HTTP? If not, can you also contact to Azure support about why OpenId Connect configuration doesn't respect to Azure application configuration?
Do you have redirectURI configured as HTTPS on Azure App registry? Can you share information about your azure app registration?
In OnApplicationInitialization:
app.UseCorrelationId();
app.UseStaticFiles(); //Add this line
app.UseCors();
I have refunded your question, we'll fix it in the first patch.
In OnApplicationInitialization:
app.UseCorrelationId();
app.UseStaticFiles(); //Add this line
app.UseCors();
I have refunded your question, we'll fix it in the first patch.
Hello,
You can check the updated article about adding custom properties to the user entity.
See also Object Extensions docs
What is your abp suite version?
The concept of Authentication Server is the web server where the IdentityServer is hosted.
Although, you can use different logout pages for your applications;
These applications will still authenticate against the same AuthServer. They will just see different login pages.
Also, what do you mean by separating the work load of customer portal and admin portal? The point of AuthServer is authenticating your users from a single point. You can always build 2 different applications using 2 different user stores (user tables).
There is no login sample project for Xamarin forms but there are some community articles about Xamarin that might help.
It is not released yet.
This seems pretty much related to web server (IIS in this case) instead of ABP.
You can try IIS Request filtering. Also, there is an SO answer related to this.