+xWe never heard back and it's not something we've been able to reproduce. What SAML for ASP.NET Core version are you using? Is this an intermittent issue? How easy is it to reproduce? To help with the debugging, could you create a small test app that simply loads the certificate and uses the private key in an attempt to reproduce the issue more consistently? Thanks for your reply. Our app targets "netstandard2.0" and is deployed on Azure App Service. Cert is created like this: new X509Certificate2( Convert.FromBase64String(certContentSecret.Value), string.Empty); Certificate is cached for 60minutes using C# ObjectCache. This cert is then used to acquireToken like this: await context.AcquireTokenAsync(audience, certCred, sendX5c: true); The issue is: acquireTokenAsync throws the exception "Keyset does not exist". This issue happens every few months and is not easy to replicate. Sometimes it would go away by itself and sometimes we'd need to change the app service plan and that will fix it. Any pointers/suggestions would be extremely helpful!
|