Gluu 4.1 QA - Null error after OTP QR code screen times out

[sahilIT2020]

Describe the issue

Null error after OTP QR code screen times out

Steps To Reproduce

Steps to reproduce the behavior:

1. Enable OTP custom script and set in oxTrust acr default authentication
2. Login to oxtrust UI, and wait until QR screen times out, without registering with OTP device

Expected behavior

It should give a friendly error message or allow user to retry registration

Actual behavior

A clear and concise description of what happen. OOPS error

##Environment detail

OS: CentOS 7.4 Gluu version(If applicable):4.1 with hybrid (couchbase and wrends)

[yurem]

I agree that the error message not explains details. it should show that session timeout. I offer to move this to 4.2 because updates can cause other issues in 4.1 now.

Also oxAuth can't cover re-authenticate flow because even AuthZ can be expired. As result after successful authentication RP can refuse issues code/token. For such case in oxAuth there is property: errorHandlingMethod: remote. In this case after login failure (for example session timeout) oxAuth sends user to RP with error response. RP should handle it and re-initiate login flow.

[yurem]

Here is how oxTrust handle it:

[yurem]

You can press return Button to force relogin

[yurem]

It should be fixed in 4.1.1

[maduvena]

When QR code times out, we will refresh (reload) QR code

[jgomer2001]

think this can be closed @maduvena ?

[MohitMaliFtechiz]

hi @yurem , message is still not user friendly on 4.2.2. , current message is "unexpected error has occurred at null "

[MohitMaliFtechiz]

this issue is fixed