Identityserver4: Breaking change in IdentityServer4.EntityFramework?

Created on 7 Dec 2018  路  12Comments  路  Source: IdentityServer/IdentityServer4

I've just updated

<PackageReference Include="IdentityServer4.AspNetIdentity" Version="2.1.0" />
<PackageReference Include="IdentityServer4.EntityFramework" Version="2.1.1" />

to

<PackageReference Include="IdentityServer4.AspNetIdentity" Version="2.3.0" />
<PackageReference Include="IdentityServer4.EntityFramework" Version="2.3.2" />

and I now get an error accessing .well-known/openid-configuration. Is a db change needed for this update?

capture

question

All 12 comments

You have to run EF migrations. Check the release notes.

Like this? It says my db is up to date

image

You need to create the migrations first, e.g. dotnet ef migrations add 23Update -c ConfigurationDbContext

That just creates CreateTable methods then errors as I already have those tables.

Is there a sql script somewhere that I can just run to update my db to the 2.3 version?

capture

I also need a SQL script, because the project I'm working in is DB first and I have to send the script to the DBA.

Is there a sql script somewhere that I can just run to update my db to the 2.3 version?

We don't have that because we don't know what version you're coming from and we don't maintain a matrix of upgrade scripts for all databases.

Do we have instructions somewhere - preferably in our docs that show how to create sql scripts and diff scripts?

I generated the db using the add-migration and then generated the scripts for creating the db using SQL tools. But because this project I'm working in is a project where the database is created and maintained by a DBA I think I'll define my clients using the custom client store or import them from a json file.

Is there a sql script somewhere that I can just run to update my db to the 2.3 version?

We don't have that because we don't know what version you're coming from and we don't maintain a matrix of upgrade scripts for all databases.

How are we supposed to upgrade then if EF Migrations does not work and you don't provide upgrade scripts. Surely you've documented the changes somewhere so we can manually add them?

EF can generate diff scripts for your specific database back-end.

EF doesn't work for us

I've managed to get the db up to date. I created a new 2.3 db and used sql compare to copy the change over to my idserver db.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings