Hello all,

I am configuring IBM Verify App with ISAM 9.0.7 by following the ISAM MMFA Cookbook, but unfortunately I am not able to make it work. At the time of registration, just after scanning the QRCode, I get an error on IBM Verify which says IOError. Currently, I have performed the following troubleshooting steps as per my understanding:

1) Checked that the details URL is reachable by the phone. Yes it is reachable.
2) Checked that the SCIM configuration is working. Yes it is working and I am able to view the user details on SCIM demo application using the mobile reverse proxy
3) Captured the logcat by recreating the issue, but unable to find any valuable information in the logcat.
My logcat command: adb logcat | findstr com.ibm.security.verifyapp > logcat-verify-new.log
My logcat output: logcat-verify-new.log

I have two questions:

1) Why is logcat not capturing valuable information? Am I not capturing it in the right way or is it that IBM Verify is not writing such errors to the logcat?
2) What are the other ways in which we can troubleshoot IBM Verify app related issues?

Hope to hear..

​Best regards,

------------------------------
Jahanzaib Sarwar
------------------------------

Hi Jahanzaib,

to answer your questions:

1) Both. The output to logcat is quite limited for security reasons. However, your command restricts that even further. Please try "adb logcat | findstr com.ibm.security" to capture output from the SDK (com.ibm.security.verifysdk) as well. The error most likely occurs there. I would also recommend not to filter the logcat output at all if you can share that file privately. Output from Firebase or push notification services could also provide valuable information to debug a problem.

2) I understand that it is difficult to debug a setup with IBM Verify. In the next version of the app (2.3.0 - coming soon) we will expose the exception message in the error screen if something went wrong.

To your actual problem: "IO Error" indicates a network problem. Could you please check that the server uses HTTPS and has a valid _not_-self-signed certificate! Self-signed certs don't pass the SSL checks and the app will fail to connect. For testing purposes, you can use the "ignoreSslCerts" flag, set in the QR code (see the Cookbook for configuration details).

------------------------------
Carsten Hagemann
------------------------------

Original Message:
Sent: Sat October 12, 2019 12:28 PM
From: Jahanzaib Sarwar
Subject: IBM Verify Troubleshooting

Hello all,

I am configuring IBM Verify App with ISAM 9.0.7 by following the ISAM MMFA Cookbook, but unfortunately I am not able to make it work. At the time of registration, just after scanning the QRCode, I get an error on IBM Verify which says IOError. Currently, I have performed the following troubleshooting steps as per my understanding:

1) Checked that the details URL is reachable by the phone. Yes it is reachable.
2) Checked that the SCIM configuration is working. Yes it is working and I am able to view the user details on SCIM demo application using the mobile reverse proxy
3) Captured the logcat by recreating the issue, but unable to find any valuable information in the logcat.
My logcat command: adb logcat | findstr com.ibm.security.verifyapp > logcat-verify-new.log
My logcat output: logcat-verify-new.log

I have two questions:

1) Why is logcat not capturing valuable information? Am I not capturing it in the right way or is it that IBM Verify is not writing such errors to the logcat?
2) What are the other ways in which we can troubleshoot IBM Verify app related issues?

Hope to hear..

​Best regards,

------------------------------
Jahanzaib Sarwar
------------------------------

Hi Carsten,

Thank you for your reply.

1) ​ Right, I will re-generate the logcat with the filter you suggested and check if I can find any errors, will share it here as well. Also, I will generate it without any filter as you recommended and send it to you privately.

2) That's a good news, it would really help in getting closer to the root cause.

Yes I have already set the ignoreSslCerts flag to true as per the cook book, but still it gives me IOError. I have cross-checked the QRCode for this flag by scanning it with another QRCode scanner app, and found the flag there in the QRCode, which confirmed that the flag is there. This brings me the need to dig down to what could be causing the issue at the network side other than the certificate thing..

Will get back with the logcat.

Regards,

------------------------------
Jahanzaib Sarwar
------------------------------

Original Message:
Sent: Sun October 13, 2019 06:41 AM
From: Carsten Hagemann
Subject: IBM Verify Troubleshooting

Hi Jahanzaib,

to answer your questions:

1) Both. The output to logcat is quite limited for security reasons. However, your command restricts that even further. Please try "adb logcat | findstr com.ibm.security" to capture output from the SDK (com.ibm.security.verifysdk) as well. The error most likely occurs there. I would also recommend not to filter the logcat output at all if you can share that file privately. Output from Firebase or push notification services could also provide valuable information to debug a problem.

2) I understand that it is difficult to debug a setup with IBM Verify. In the next version of the app (2.3.0 - coming soon) we will expose the exception message in the error screen if something went wrong.

To your actual problem: "IO Error" indicates a network problem. Could you please check that the server uses HTTPS and has a valid _not_-self-signed certificate! Self-signed certs don't pass the SSL checks and the app will fail to connect. For testing purposes, you can use the "ignoreSslCerts" flag, set in the QR code (see the Cookbook for configuration details).

------------------------------
Carsten Hagemann

Original Message:
Sent: Sat October 12, 2019 12:28 PM
From: Jahanzaib Sarwar
Subject: IBM Verify Troubleshooting

Hello all,

I am configuring IBM Verify App with ISAM 9.0.7 by following the ISAM MMFA Cookbook, but unfortunately I am not able to make it work. At the time of registration, just after scanning the QRCode, I get an error on IBM Verify which says IOError. Currently, I have performed the following troubleshooting steps as per my understanding:

1) Checked that the details URL is reachable by the phone. Yes it is reachable.
2) Checked that the SCIM configuration is working. Yes it is working and I am able to view the user details on SCIM demo application using the mobile reverse proxy
3) Captured the logcat by recreating the issue, but unable to find any valuable information in the logcat.
My logcat command: adb logcat | findstr com.ibm.security.verifyapp > logcat-verify-new.log
My logcat output: logcat-verify-new.log

I have two questions:

1) Why is logcat not capturing valuable information? Am I not capturing it in the right way or is it that IBM Verify is not writing such errors to the logcat?
2) What are the other ways in which we can troubleshoot IBM Verify app related issues?

Hope to hear..

​Best regards,

------------------------------
Jahanzaib Sarwar
------------------------------

Hello Jahanzaib,

Facing similar issue. Did you manage to find a fix ?

Thanks,
Mitesh 

------------------------------
Mitesh Parekh
------------------------------

Original Message:
Sent: Sun October 13, 2019 07:06 AM
From: Jahanzaib Sarwar
Subject: IBM Verify Troubleshooting

Hi Carsten,

Thank you for your reply.

1) ​ Right, I will re-generate the logcat with the filter you suggested and check if I can find any errors, will share it here as well. Also, I will generate it without any filter as you recommended and send it to you privately.

2) That's a good news, it would really help in getting closer to the root cause.

Yes I have already set the ignoreSslCerts flag to true as per the cook book, but still it gives me IOError. I have cross-checked the QRCode for this flag by scanning it with another QRCode scanner app, and found the flag there in the QRCode, which confirmed that the flag is there. This brings me the need to dig down to what could be causing the issue at the network side other than the certificate thing..

Will get back with the logcat.

Regards,

------------------------------
Jahanzaib Sarwar

Original Message:
Sent: Sun October 13, 2019 06:41 AM
From: Carsten Hagemann
Subject: IBM Verify Troubleshooting

Hi Jahanzaib,

to answer your questions:

1) Both. The output to logcat is quite limited for security reasons. However, your command restricts that even further. Please try "adb logcat | findstr com.ibm.security" to capture output from the SDK (com.ibm.security.verifysdk) as well. The error most likely occurs there. I would also recommend not to filter the logcat output at all if you can share that file privately. Output from Firebase or push notification services could also provide valuable information to debug a problem.

2) I understand that it is difficult to debug a setup with IBM Verify. In the next version of the app (2.3.0 - coming soon) we will expose the exception message in the error screen if something went wrong.

To your actual problem: "IO Error" indicates a network problem. Could you please check that the server uses HTTPS and has a valid _not_-self-signed certificate! Self-signed certs don't pass the SSL checks and the app will fail to connect. For testing purposes, you can use the "ignoreSslCerts" flag, set in the QR code (see the Cookbook for configuration details).

------------------------------
Carsten Hagemann

Original Message:
Sent: Sat October 12, 2019 12:28 PM
From: Jahanzaib Sarwar
Subject: IBM Verify Troubleshooting

Hello all,

I am configuring IBM Verify App with ISAM 9.0.7 by following the ISAM MMFA Cookbook, but unfortunately I am not able to make it work. At the time of registration, just after scanning the QRCode, I get an error on IBM Verify which says IOError. Currently, I have performed the following troubleshooting steps as per my understanding:

1) Checked that the details URL is reachable by the phone. Yes it is reachable.
2) Checked that the SCIM configuration is working. Yes it is working and I am able to view the user details on SCIM demo application using the mobile reverse proxy
3) Captured the logcat by recreating the issue, but unable to find any valuable information in the logcat.
My logcat command: adb logcat | findstr com.ibm.security.verifyapp > logcat-verify-new.log
My logcat output: logcat-verify-new.log

I have two questions:

1) Why is logcat not capturing valuable information? Am I not capturing it in the right way or is it that IBM Verify is not writing such errors to the logcat?
2) What are the other ways in which we can troubleshoot IBM Verify app related issues?

Hope to hear..

​Best regards,

------------------------------
Jahanzaib Sarwar
------------------------------