Skip to content

Conversation

aniket-okta
Copy link
Contributor

This pull request fixes #244 introduces strong name signing to the Okta.AspNetCore assembly. This resolves issues encountered when referencing Okta.AspNetCore from other strongly named assemblies, particularly in .NET 6.0+ projects.

The changes include:

Adding a public key file (okta.aspnet.snk).
Enabling assembly signing and specifying the key file in the Okta.AspNetCore.csproj.
Implementing delayed signing for development builds.
(If applicable) Updating InternalsVisibleTo attributes in AssemblyInfo.cs to include the public key of related test assemblies.
(If applicable) Outlining necessary build server configurations for full strong name signing using a private key.
(If applicable) Providing instructions for developers to enable local debugging of partially signed assemblies.
This change aligns with the approach taken in the okta-aspnet repository (as seen in the linked issue and related pull request) to ensure better compatibility and integration with strongly named .NET ecosystems.

@aniket-okta aniket-okta merged commit c5cf2f8 into master May 2, 2025
2 checks passed
@aniket-okta aniket-okta deleted the OKTA-920831 branch May 2, 2025 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Okta.AspNetCore assembly not strongly-named assembly
2 participants