What changes required after deprication of user auth keys.

[AdilSoomro]

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

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

[BlackStar-95]

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

[AdilSoomro]

@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.

[sherwinski]

Hi @AdilSoomro,

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

[AdilSoomro]

@sherwinski Has this been addressed in 2.1.0?

[sherwinski]

Hi @AdilSoomro,

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

[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.