Openiddict-core: Cannot move OpenIddict entities to custom schema after new version

Created on 3 Jul 2018 · 13Comments · Source: openiddict/openiddict-core

Hi, I have been putting the OpenIddict entities in their own "OpenIddict" schema in my database. It has worked fine until the latest version.

Right now, it is creating the tables in the "OpenIddict" schema like I want it to, but it is also creating the default schema (public as I'm using PGSQL) as well.

Any suggestions? I'm sure I'm just missing something in my Startup.cs.

Thanks!

In my Startup.cs

        public void ConfigureServices(IServiceCollection services)
        {
            ....
            services.AddEntityFrameworkNpgsql().AddDbContextPool<AppDbContext>(options =>
            {
                options.UseNpgsql(Configuration["pgsql:housestay"], b => b.MigrationsAssembly("HouseStayEF"));
                options.UseOpenIddict();
            });
            ....
            services.AddOpenIddict()
                .AddCore(options =>
                {
                    options.UseEntityFrameworkCore().UseDbContext<AppDbContext>();
                })
                .AddServer(options =>
                {
                    options.UseMvc();
                    options.EnableTokenEndpoint("/auth/token");

                    options.AllowPasswordFlow();
                    //options.AllowCustomFlow(GrantTypes.Facebook);
                    //options.AllowCustomFlow(GrantTypes.Google);
                    options.AllowRefreshTokenFlow();

                    //options.AcceptAnonymousClients();

                    options.RegisterScopes(
                        OpenIdConnectConstants.Scopes.Email,
                        OpenIdConnectConstants.Scopes.Profile,
                        OpenIddictConstants.Scopes.Roles
                        );

                    options.SetAccessTokenLifetime(TimeSpan.FromHours(1));
                    options.SetRefreshTokenLifetime(TimeSpan.FromDays(180));

                    if (!_isProduction)
                    {
                        options.DisableHttpsRequirement();
                    }
                });
            ....
        }

In my AppDbContext.OnModelCreating:

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

        .....
        builder.Entity<OpenIddictApplication>(e => { e.ToTable("Applications", "OpenIddict"); });

        builder.Entity<OpenIddictAuthorization>(e => { e.ToTable("Authorizations", "OpenIddict"); });

        builder.Entity<OpenIddictScope>(e => { e.ToTable("Scopes", "OpenIddict"); });

        builder.Entity<OpenIddictToken>(e => { e.ToTable("Tokens", "OpenIddict"); });
        .....
    }

Source

ArcadeRenegade

Most helpful comment

You can use the ASP.NET Core authorization policy builder: policy.RequireClaim(OAuthValidationConstants.Claims.Scope, "marketing_api").

kevinchalet on 4 Jul 2018

🎉2

All 13 comments

Hey Ryan,

Any chance you could share the usings you have in AppDbContext? I want to make sure you're using the good models there.

kevinchalet on 3 Jul 2018

Hi @PinpointTownes ! It is using using the models from OpenIddict.Models.

using OpenIddict.Models;