-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Update IdentityServer4 -> Duende #33590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| <Reference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" /> | ||
| <Reference Include="Microsoft.AspNetCore.Identity.UI" /> | ||
| <Reference Include="Newtonsoft.Json" /> | ||
| <SuppressBaselineReference Include="IdentityServer4.AspNetIdentity" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aspnet-build is this something I should be checking in (SupressBaselineReference?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's alright if the pseudo-breaking change is approved. I'm a bit more concerned about having a shipping package depend on an unsigned assembly. Thoughts @Pilchie❔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would be my only concern as well. I couldn't find other instances of shipping projects doing this in our repo or dotnet/runtime
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blowdart seems to be okay with this, is there anyone else we should ping about this? To clarify its signed, but doesn't have a strong name, poor choice in wording by me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our Nuget package is signed. The assemblies do not have a strong name. What would be the benefit of that for a library targeting .NET Core consumers only?
dougbu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, why are you adding the empty src/Identity/ApiAuthorization.IdentityServer/src/ApiAuthorizationDbContext.cs file❔
| <Reference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" /> | ||
| <Reference Include="Microsoft.AspNetCore.Identity.UI" /> | ||
| <Reference Include="Newtonsoft.Json" /> | ||
| <SuppressBaselineReference Include="IdentityServer4.AspNetIdentity" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's alright if the pseudo-breaking change is approved. I'm a bit more concerned about having a shipping package depend on an unsigned assembly. Thoughts @Pilchie❔
...y/testassets/Wasm.Authentication.Server/Data/Migrations/ApplicationDbContextModelSnapshot.cs
Outdated
Show resolved
Hide resolved
| /// <value> | ||
| /// The keys. | ||
| /// </value> | ||
| public DbSet<Key> Keys { get; set; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see a couple of new DbSet<T> properties in this PR but haven't noticed new references to them. What are they for❔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it comes from a new requirement from the updated version of IPersistedGrantDbContext, which now store Keys, I'm not sure exactly what they are used for, but its part of the contract for IdentityServer Stores
...y/testassets/Wasm.Authentication.Server/Data/Migrations/ApplicationDbContextModelSnapshot.cs
Show resolved
Hide resolved
|
Which one is the unsigned package @dougbu mentions? |
|
@blowdart all of the identity server packages are unsigned, by design it appears: DuendeArchive/IdentityServer4#1653 |
|
Oh strong named rather than signed. Yea not worried then considering it has no security benefits, and it's "only" a dependency rather than shipping as part of the product. |
Fixes #32881