onesignal-php-api icon indicating copy to clipboard operation
onesignal-php-api copied to clipboard
verified publisher icon OneSignal

What changes required after deprication of user auth keys.

Open AdilSoomro opened this issue 1 year ago • 5 comments

How can we help?

Since we no longer can acquire the user auth keys, what needs to be changed in the sdk code to allow sending push for new accounts?

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

AdilSoomro avatar Nov 21 '24 06:11 AdilSoomro

https://documentation.onesignal.com/docs/keys-and-ids#migrating-from-legacy-api-keys please check it

BlackStar-95 avatar Nov 27 '24 15:11 BlackStar-95

@BlackStar-95 thanks, we already received these instructions. We've added this plugin as a dependency in one of our own plugin via composer. We distribute our plugin to other developers. The instructions to manually migrate from legacy api is cumbersome for our customer base.

AdilSoomro avatar Nov 27 '24 17:11 AdilSoomro

Hi @AdilSoomro,

Our team is working on an API for generating new rich auth tokens and should be available early next year.

sherwinski avatar Dec 10 '24 22:12 sherwinski

@sherwinski Has this been addressed in 2.1.0?

AdilSoomro avatar Feb 18 '25 13:02 AdilSoomro

Hi @AdilSoomro,

Unfortunately no, but I will follow up on this issue with any updates once I have them. Thanks for your patience.

sherwinski avatar Feb 19 '25 00:02 sherwinski

Hey @AdilSoomro,

Thanks for your patience here, we've just added support for the Authentication endpoints (e.g. creating, deleting, rotating keys, etc) in https://github.com/OneSignal/onesignal-php-api/releases/tag/v5.3.0-beta1. Hope that this helps in your situation.

sherwinski avatar Oct 02 '25 21:10 sherwinski