3.0.1 fails to import certificate on Windows shared tier about net-core-push-notifications HOT 10 CLOSED

Please use version 3.0.0. I'll revert the 3.0.1 changes when I release a new version. Thank you!

from net-core-push-notifications.

@Dreamescaper Are you getting it in Azure Function or Azure Web app? I remember setting an env variable WEBSITE_LOAD_USER_PROFILE=1 for those.

from net-core-push-notifications.

@andrei-m-code
It does not not work for the cheapest shared tier - you can't load profile there.

from net-core-push-notifications.

Limitations of the environment... 🤷‍♂️. Sorry buddy, I wish I could help you with it. Do you use windows or linux btw? @Dreamescaper

from net-core-push-notifications.

@andrei-m-code
Windows.

Thing is that is works fine with 3.0.0 and BouncyCastle implementation.
If you don't like the idea of this external dependency, would be great to have ability to inject custom implementation (so in my case I'd inject that removed BouncyCastle implementation).

from net-core-push-notifications.

@Dreamescaper wow really? That's not good. I indeed hate to have that extra dependency, but if it doesn't work otherwise.. maybe injecting is an option. It certainly complicates things for average user though. I'll need to think about it.

from net-core-push-notifications.

Hi Folks

We where facing a similar issue with on an hosted environment first. It turns out, that our hoster had an issue on a shared tier but was not able to fix it, therefore we moved our push notification service to a dedicated server (Windows 2019 with IIS).

Initially it was not working there also, but after some investigations and trying if it is working with kestrel, it turns out - with kestrel it was working fine.

Then we focused again the application pool from the iis and switched the app pool identity from ApplicationPoolIdentity to NetworkService, after that push notification where send also using iis.

Maybe you can give it a try, hopefully it works for you too.

Best regards

cue

from net-core-push-notifications.

Hi, Andrei,

have the same exception on my hosting environment.

Stack trace is

StackTrace: at System.Security.Cryptography.CngKeyLite.ImportKeyBlob(String blobType, ReadOnlySpan1 keyBlob, Boolean encrypted, ReadOnlySpan1 password)
at System.Security.Cryptography.CngPkcs8.ImportPkcs8(ReadOnlySpan1 keyBlob) at System.Security.Cryptography.CngPkcs8.ImportPkcs8PrivateKey(ReadOnlySpan1 source, Int32& bytesRead)
at System.Security.Cryptography.ECDsaImplementation.ECDsaCng.ImportPkcs8PrivateKey(ReadOnlySpan1 source, Int32& bytesRead) at CorePush.Apple.ApnSender.CreateJwtToken() at CorePush.Apple.ApnSender.<GetJwtToken>b__8_0(String _) at System.Collections.Concurrent.ConcurrentDictionary2.GetOrAdd(TKey key, Func`2 valueFactory)
at CorePush.Apple.ApnSender.GetJwtToken()
at CorePush.Apple.ApnSender.SendAsync(Object notification, String deviceToken, String apnsId, Int32 apnsExpiration, Int32 apnsPriority, Boolean isBackground)
at BusinessLogic.Services.MobileNotificationService.SendMessage(String message, Int32 userId) in C:\Users\

from net-core-push-notifications.

Greate, 3.0.0 works as expected. Thank you!

from net-core-push-notifications.

v3.0.2 should now work for shared environments and whatnot

from net-core-push-notifications.