Open thebigkhaled opened 1 day ago
I found a workaround solution to use the production certificate running dotnet dev-certs https -v -ep openiddict.pfx -p db1e01bd-e51c-4345-8255-c789e345940a --trust
then change the environment to production in
if (true)
{
PreConfigure<AbpOpenIddictAspNetCoreOptions>(options =>
{
options.AddDevelopmentEncryptionAndSigningCertificate = false;
});
PreConfigure<OpenIddictServerBuilder>(serverBuilder =>
{
serverBuilder.AddProductionEncryptionAndSigningCertificate("openiddict.pfx", "db1e01bd-e51c-4345-8255-c789e345940a");
serverBuilder.SetIssuer(new Uri(configuration["AuthServer:Authority"]!));
});
}
Update to the Latest .NET SDK: Ensure you are using the latest .NET SDK that might have fixes for macOS Sequoia issues. Regularly check the official .NET GitHub repository for updates.
Modify Configuration:
If using the workaround with the production certificate, make sure to set the environment correctly in your configuration:
csharp
Copy code
if (true)
{
PreConfigure
PreConfigure<OpenIddictServerBuilder>(serverBuilder =>
{
serverBuilder.AddProductionEncryptionAndSigningCertificate("openiddict.pfx", "db1e01bd-e51c-4345-8255-c789e345940a");
serverBuilder.SetIssuer(new Uri(configuration["AuthServer:Authority"]!));
});
} File a Detailed Bug Report: If not already done, consider filing a bug report on the .NET repository, including all the details and your findings. This can help improve future updates and potentially address your issue more promptly.
Community Support: Engage with the ABP community or relevant forums for any potential fixes or shared experiences from other developers facing similar issues.
Review Keychain Access: Since the error indicates that the certificate may have been deleted from the keychain, ensure that the certificate exists and is accessible in your macOS Keychain. You may need to re-add it if it's missing.
Is there an existing issue for this?
Description
I’m encountering an issue with a newly generated project after updating to macOS Sequoia (15). After completing the migration successfully, the problem arises when attempting to run the project. Initially, I had trouble with .NET certificate generation, but I was able to resolve that by following the workaround for
CertificateRequest.CreateSelfSigned
on macOS Sequoia.CertificateRequest.CreateSelfSigned fails on macOS Sequoia
Even after successfully generating the development certificate, I’m still encountering an error related to the opendict certificate. I suspect this is due to macOS Sequoia’s updated security policies. While the workaround works fine for .NET APIs, it doesn’t seem to resolve the issue for Abp projects.
.NET is expected to release an emergency update in October to address this problem, but in the meantime, does anyone have suggestions for a fix ?
Reproduction Steps
Generate new application using cli on macOS sequoia.
Run migration and then run the app
Expected behavior
No response
Actual behavior
No response
Regression?
No response
Known Workarounds
Version
8.3.1
User Interface
React Native
Database Provider
EF Core (Default)
Tiered or separate authentication server
Tiered
Operation System
macOS
Other information
No response