@maliming : thank you for you answer but this is not my question. I already have searched for IS4 UI's on the web and already know IS4 documentation.
My question is : is it possible to integrate MVC UI in my project ? As I am using angular UI, I never had to add MVC in the past.
Can you please give me a clue ? There should be a reason why abp zero team has not implemented it on angular... and I want to know if there is a blocking point to do it.
I can see on MVC project template that identyserver UI is implemented (views and controllers) https://github.com/aspnetzero/aspnet-zero-core/blob/dev/aspnet-core/src/MyCompanyName.AbpZeroTemplate.Web.Mvc/Controllers/ConsentController.cs.
Would it be possible to integrate it to my zero angular project ?
I need your help on this.
Yes, but what is your advice ? Doing it in MVC or angular ?
I'm thinking of using MVC with UI provided by IdentityServer4 team In that case, can you provide the basic steps to configure it with abp ?
For example :
As we are using abp to activate identityserver, I need to know what differs from "standard" identityserver integration.
Thank you
You are right ! I removed appsettings.json and appsettings.production.json and it is working now.
Do you know why I had this behavior ? It's like a mix is being done between appsettings files !?
Unfortunately, it is not allowed by our company rules.
Has I said, IdentityServer activation works on my dev machine but not on Azure server...
Have you tried to enable identityserver over your cloud servers ?
Yes,
I'm running my tests on Staging slot so the file used is appsettings.staging.json. As far as I deactivate IdentityServer property, the app runs again. It is not an issue with this file.
Tks @maliming
Here is the error log :
Application startup exception: System.InvalidOperationException: Grant types list contains duplicate values at IdentityServer4.Models.Client.ValidateGrantTypes(IEnumerable`1 grantTypes) at Web.IdentityServer.IdentityServerConfig.GetClients(IConfigurationRoot configuration) in \IdentityServer\IdentityServerConfig.cs:line 39 at Web.IdentityServer.IdentityServerRegistrar.Register(IServiceCollection services, IConfigurationRoot configuration) in Core\IdentityServer\IdentityServerRegistrar.cs:line 13 at Web.Startup.Startup.ConfigureServices(IServiceCollection services) in Web.Host\Startup\Startup.cs:line 106 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.ConfigureServices(IServiceCollection services) at Microsoft.AspNetCore.Hosting.Internal.WebHost.EnsureApplicationServices() at Microsoft.AspNetCore.Hosting.Internal.WebHost.Initialize() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication()
It is strange has I just defined "password" as grant type. I tried to change it by
"AllowedGrantTypes": [ "hybrid", "client_credentials" ],
But same error.
Now we can say : "Starting from zero" :D :D
Joke aside, I also contracted a third party to work on Metronic migration starting from my current project (zero v5). We came to a point where we have both Metronic assets v5 and v6... The project is very slow and I'm not confident for the final result !
On an other hand, I would like to merge my project with current zero version but let's be honnest, the current anglular UI is not qualitative enougth for a production delivery : colors are not consistent, font sizes are different, some themes are not well integrated, UI buggs, angular component limitation (due to JQuery cancellation)... This is far from original Metronic v6 demo that is beautiful.
For my company it is a huge issue ! We are not talking about a one shot product but a SAAS product with a lot of users... The risk is to loose users by doing such updates and even loose opportunities due to customer complain.
I really like developing with abp framework but this non updatable UI came to a blocking point from my side.
This doesn't help. I just enabled IdentityServer on appsettings file :
"IdentityServer": {
"IsEnabled": "true",
"Authority": "https://------app-service-stagging.azurewebsites.net/",
"ApiName": "default-api",
"ApiSecret": "secret",
"Clients": [
{
"ClientId": "client",
"AllowedGrantTypes": [ "password" ],
"ClientSecrets": [
{
"Value": "def2edf7-5d42-4edc-a84a"
}
],
"AllowedScopes": [ "default-api" ]
}
]
},
The only difference between a running project on azure and the error described previously is just changing "IsEnabled" property to "true".