We have so far had a relatively stable PrivacyIDEA environment running version 3.6.2 (mobile 3.1.5) with PUSH tokens working.
On the new version of the mobile application PrivacyIDEA Authenticator 4.0 we get in the logs error:
“message”: “SenderId mismatch”,
But if someone is using older version of mobile application , for example 3.1.5 communication with PUSH works correctly
Can someone help?
You are right - this was obviously not quite clear.
With the privacyIDEA Authenticator the own-firebase-concept was dropped for stability reasons. You can find in this forum several comments about this. The Authenticator 4.0 as it comes compiled from the stores now uses a central firebase project. You would need an API/auth key, to communicate to this project.
we have encountered the same problem. In my opinion, it is bad style to distribute such a change as an app update without a clear indication of the consequences and to say afterwards that it can only be used by contract customers. First of all, all users who have installed the update are locked out. For Apple users, I think there is no way back to the old app and as I understand it, all existing tokens have to be rolled out again so that it works again.
Thank you (Cornelinux)
We have done the configuration with Poll (without Firebase) for now. Tokens Push started to work.
A few more questions came up in the new environment that I would appreciate clarification on:
Does Push token protection work in the Poll configuration? - I set the policy on the server (push_firebase_app_pin), but the newly made token is not protected. For OTP it works without any problem
Is it possible to force server-side protection for existing tokens in PrivacyIdea Authenticator 4.0
In PrivacyIdea Authenticator 4.0, when Decline (not Accept) is pressed, is anything sent to PrivacyIdea 3.7.1 server, obviously in Poll configuration?
I’m from Poland and by default after installing PrivacyIdea Authenticator 4.0 the Czech language is enabled - a bit inconvenient for regular users. Is it possible to :