sso-server | Then install this SSO server | Authentication library

I got a good and simple SSO sample project from here

Currently the sample works as below.

• Start app1, app2, sso-server.

• Load http://localhost:8082/app1 It will redirect to login page of http://localhost:8080/sso-server

  username: user, password: password

• On successful login, it will redirect back to http://localhost:8082/app1 The page will show "Welcome to app1, user"
• Now on loading http://localhost:8083/app2 The page will show "Welcome to app2, user" since we have already logged in.

Now my issue is the sample uses spring-boot-starter-parent version 1.5.9.RELEASE

The sample uses spring-cloud dependency also. I read like spring-cloud will not support spring-boot-starter-parent version 2 or above.

So I tried to remove spring cloud dependency from app1 and I could start the application after a tough try. My new pom is as below.

I am following this tutorial and it works perfectly, it is single sign on application, then I tried to build a docker image for each service and expose ports they are using but when I login the app1 service this response:

I have been trying to follow a tutorial found HERE for setting up a demo to help me understand SSO on my local machine before implementing in another project. I have run into a problem that has left me stuck. I receive and error telling me to add a bean. Please let me know what code I am missing. I cannot get the program to run.

Tree of file system

AuthApplication.java

We develop a bigger SaaS application based on ASP.NET Core and EFCore. We separate tenants by database, means that we have one database for each tenant.

The database is migrated on any incoming request by a client by a custom middleware. This required, because the application should be immediately available after a tenant signed up on our SSO-Server.

So the pipeline looks like this:

1. Authentication Middleware (ASP.NET Core Standard)
2. UserResolverMiddleware (extracts TenantID from the JWT token and adds it to HttpContext.Items)
3. TenantDatabaseInitializerMiddleware (constructs a TenantDbContext object by passing the tenantid in the ConnectionString and starts migration)

Unfortunately this has some downsides, as I recognized later:

1. The TenantDatabaseInitializer sometimes uses an TenantDbContext of a different tenant. Therefore no database is migrated and the whole request fails.
2. If there are a lot of incoming requests for the same tenant, the migrations often overlap and fail. (The Middleware is catching the InvalidOperationExceptions that are thrown, but this does not seem as good solution).
3. It creates a lot of databases.
4. The requests take potentially long to complete (check for migration).

Long introduction, short question: Can anyone judge whether this migration workflow is a good practise? If not: Do you have a better idea how I can achieve multi tenancy?

I read about Global Query Filters in EFCore 2.0, but I'm not sure how safe this approach is regarding data isolation.

Thanks!