Hi Team,
ADVANCED AUTHENTICATION 9.0 on Windows, try to integrate with push authentication using Google FCM.
Have follow the the documentation, setup & configured AA with Push configuration.
I was able to registered my mobile device and i able to obtain a Device ID and Device Token.
Note: I able to connect FCM using my server key.
But when i test with
Push Authentication login, it failed. When check AFM log, it show the error
2021-04-21 13:14:15,781 [http-nio-8080-exec-6] INFO
pns.fcm.SSLUtils(53) -> connection got successful2021-04-21 13:14:15,875 [http-nio-8080-exec-6] INFO aa.pns.PushNotificationService(84) -> RESPONSE :
{"multicast_id":1335814113183043666,"success":0,"failure":1,"canonical_ids":0,"results":[{"error":"MismatchSenderId"}]}
2021-04-21 13:14:15,875 [http-nio-8080-exec-6] INFO aa.pns.PushNotificationService(122) ->
FCM response is: {"multicast_id":1335814113183043666,"success":0,"failure":1,"canonical_ids":0,"results":[{"error":"MismatchSenderId"}]}2021-04-21 13:14:15,875 [http-nio-8080-exec-6] ERROR aa.pns.PushResultSet(57) -> This is error scenario...
2021-04-21 13:14:15,875 [http-nio-8080-exec-6] INFO aa.pns.PushResultSet(61) -> Error msg is : MismatchSenderId
2021-04-21 13:14:15,875 [http-nio-8080-exec-6] INFO aa.pns.PushResultSet(77) -> errorMsg: MismatchSenderId status: fail deviceToken: eFh1z80xneU:APA91bHRBr4RwRjRinaIwNlHSqZl0zT1WJHqbvxivy1fteXGyg7AZmkJ8_Xfx8ZZhywZoizCO0qMwQlPhg6HhtLjmKAPHnTgnaf7QzOzjUWaEMBfMAmc-P5m_yxgf87VRGg3QI7QgMvX msgID: null
Q1. When Register a mobile device with Push, which firebase instance ID is used ?
Q2. We are using Playstore CA Mobile Authenticator app, will it does it work with FCM based on OOTB configuration ?
Q3. Do we need to custom build a CA Mobile Authenticator app in order to work with FCM for Push notification ?
regards,
William