Out of the blue, I’ve been unable to 2FA-validate logins via Push token - the client system (where the user tries access) receives an HTTP error when contacting the PI server, although the PI app actually receives the request to authenticate.
In PI’s log, I found the following error, twice per authentication request:
[2021-05-21 11:34:27,663][14536][139832521623296][WARNING][privacyidea.lib.smsprovider.FirebaseProvider:169] Failed to send message to firebase service: {
“error”: {
“code”: 404,
“message”: “Requested entity was not found.”,
“status”: “NOT_FOUND”,
“details”: [
{
“@type”: “type.googleapis.com/google.firebase.fcm.v1.FcmError”,
“errorCode”: “UNREGISTERED”
}
]
}
}
This happens also with the latest code, as updated today (v3.5.2), and of course after restarting PI.
Searching the net, I found references to expiring Firebase credentials, “for good measure” I created a new key in Firebase and provided the according new JSON file (with the updated private key) to PI, restarted httpd but still have the errors and same behavior.
Any insight into what PI / Firebase is missing, that may have changed in the last few days?