Use in existing IdentityServer setup

[ruant]

For people having identity server running already, any plans on making a guide on how to get this awesome Admin UI to work?

Maybe there has to be some work done with exposing setup options like naming, using existing dbcontexts etc.

[ruant]

Especially if it's planned to release this UI as a simple injectable middleware as issue #28 is about.

[skoruba]

@ruant Sure, I will add this use case to the upcoming video tutorial. It's a great idea. 👍

We are currently working on a project template for dotnet cli. It will be possible to use like this:
dotnet new skoruba.is4admin. #51
I think - it might be useful for the better customization. You can define your administration name, default admin role name etc.

After that I want to create the nuget packages with UI and BL & EF layers, but I think that takes more time to complete. :)

Thank you for your feedback.

[Brice-xCIT]

Hi! This issue to me should be priority number one. After spending several hours in the code I still don't see how to use this with an existing installation. Somehow the code forces consumers to use its own EF migration and database schema, which bundles ASP.NET Core Identity and IdentityServer4.EntityFramework models into one single DB and DbContext. I tried to decouple both of these things to bind them to two different EF connections, without any success. Similarly, using this single DB as operational store, config store and identity store in vanilla IS4 fails because (from what I understand) migrations are not compatible.

I would really love some doc about how to use this nice admin UI with the plain old IS4 quickstart at http://docs.identityserver.io/en/release/quickstarts/8_entity_framework.html.
At least, is it even possible?

[skoruba]

Hi,
I absolutely understand your requirements, I will create a documentation for that.
Please for now - take a look at this branch - feature/extensible-aspnet-identity -
https://github.com/skoruba/IdentityServer4.Admin/tree/feature/extensible-aspnet-identity
Currently, I am working on better using of this administration with the existing instance of the IS4.
Do you want to use the administration only for IS4 or with Asp.Net Core Identity?
Thanks!

[Brice-xCIT]

Thanks for your message and responsiveness, @skoruba!
I found out about the branch right after writing the message, and although it definitely goes into the right direction, as far as I can see AdminDbContext still wraps the three stores.
IS4+Asp.Net Core Identity is what I'm after, and truthfully I could even consider using AdminDbContext's integrated DB migration instead of the IS4 quickstart's suggested design, if only I could figure out how IS4 is supposed to connect to this integrated DB at all, either through Core Identity as an identity store, or through EF as operational or config store. I guess, that's what Skoruba.IdentityServer4.AspNetCoreIdentity is doing?

[skoruba]

It’s absolutely possible to split the AdminDbContext into more DbContexts like you mentioned with IS4 quickstart sample.
The repositories/services are designed for generic DbContext and you can choose an approach of one or more dbcontexts.
Please take a look at Startup class for extension method that added into DI the repositories and services - AddAdminServices - there you can specify one or more dbcontexts.
BTW: I know that it might be probable unclear, therefore I will prepare a doc.
I am very happy for your points!
Thanks!

[patrick-heuer]

I have the same requirement: I want to enhance my existing SSO service (C#/Core 2.1, Identity Server 4, ASP.NET Identity, Sqlite, Kestrel webserver) with your great Admin UI.

But I don´t know how to do!

I have seen in the "official" IdentityServer4 - AdminUI tool from Rock Solid, that you can add "UseAdminUI" in the startup.cs and then an additional admin-url is available... that is very easy integration, but I am not sure if I like their tool and also not their licences - so my hope is on your solution :)

[skoruba]

@PKrause79 I will update the README with getting started guide - probable this week :)
Thanks!

[patrick-heuer]

I am thinking, why you have separated (standalone) services for IDS4, ASP.NET Identity and your Admin-service? What are the reasons for that? Maybe your appraoch is better and its not a good design to integrate all the 3 artefacts as a "SSO-application" in only one service - what do you think?

[skoruba]

I have created two separated web apps - one for IS4 with Asp.Net Core Identity and AdminUI - I think it is up to you - how you will design this project structure - I prefer this approach. :)

[skoruba]

@PKrause79 - I have updated the master branch with some information how to use current solution with existing IdentityServer4 instance.
Please take a look, thanks!

[OculiViridi]

@skoruba Hi! I'm also trying to add your AdminUI on my existing IS4 instance, but by following the readme I'm not really sure about how to make them works together...

This is my actual IS4 configuration.

DbContext

public class AuthDbContext : IdentityDbContext<User>
{
	public AuthDbContext(DbContextOptions<AuthDbContext> options)
		: base(options)
	{ }

	protected override void OnModelCreating(ModelBuilder builder)
	{
		base.OnModelCreating(builder);
	}
}

Startup class

public class Startup
{
	public void ConfigureServices(IServiceCollection services)
	{
		services.AddDbContext<AuthDbContext>(options =>
			options.UseSqlServer(connectionString,
				sqlServerOptions => sqlServerOptions
					.MigrationsAssembly(assemblyName)));

		services.AddIdentity<User, IdentityRole>(options =>
			{
				options.Password.RequireDigit = true;
				options.Password.RequiredLength = 10;
				options.Password.RequireLowercase = true;
				options.Password.RequireUppercase = true;
			})
			.AddEntityFrameworkStores<AuthDbContext>()
			.AddDefaultTokenProviders();

		services.AddMvc(config =>
			{
				// HTTP 406 when not supported format is requested by client
				config.ReturnHttpNotAcceptable = true;
			})
			.SetCompatibilityVersion(CompatibilityVersion.Version_2_1);

		services.Configure<IISOptions>(iis =>
			{
				iis.AuthenticationDisplayName = "Windows";
				iis.AutomaticAuthentication = false;
			});

		var builder = services.AddIdentityServer(options =>
			{
				options.Events.RaiseErrorEvents = true;
				options.Events.RaiseInformationEvents = true;
				options.Events.RaiseFailureEvents = true;
				options.Events.RaiseSuccessEvents = true;
			})

			// Configuration data store
			.AddConfigurationStore(configurationDb =>
				{
					configurationDb.ConfigureDbContext = db => db.UseSqlServer(connectionString, sql => sql.MigrationsAssembly(assemblyName));
				})

			// Operational data store
			.AddOperationalStore(operationalDb =>
				{
					operationalDb.ConfigureDbContext = db => db.UseSqlServer(connectionString, sql => sql.MigrationsAssembly(assemblyName));
				})

			.AddAspNetIdentity<User>();
		}
	}
}

What am I supposed to do on MyProject.AuthAdminUI.STS.Identity and MyProject.AuthAdminUI.Admin projects?

Also, do I need to create a separate database for the Admin UI or can I add the required tables to the current one used by IS4? Actually, all my IS4 DbContexts uses the same database, so .NET IdentityUser, Persisted and Configuration are different DbContexts but all tables are on the same database.
Is there any possible conflict adding the Admin UI ones?