search

SwisscomTrustServices / itext7-ais-client

Apache License 2.0
1 stars 3 forks source link

Enhance the SignResponse when falling back to "ConsentURL" with a reason string #2

Open ralfhauser opened 3 years ago

ralfhauser commented 3 years ago

Today, again, we got a response with URL instead of the MobileID authorization being triggered on the user's SmartPhone like it nicely did for months.

DEBUG ...- 200 sign resp of 911 b received 20210720_114941_376 DEBUG ...- <?xml version="1.0" encoding="UTF-8" standalone="yes"?>urn:oasis:names:tc:dss:1.0:profiles:asynchronousprocessing:resultmajor:Pending24a528d9-02cc-42b4-b781-fccaa6yyyyyy</async:ResponseID>https://ais-sas.swisscom.com/sas/web/tk4a97fc11804xxxxxx/pass?lang=de</sc:ConsentURL></sc:Result></sc:StepUpAuthorisationInfo>

The user still perfectly validated on level 4:

SUCCESSFUL {"evidenceId" : "RAS5db2aa0c9cfee30007XXXX","serialNumber" : "MIDCHENXHCS0XXX"}

So, we don't have a clue why ?

And especially during holiday season, users forget about the events that could cause this.

So, please amend the SignResponse with a reason field that says something like

"NewSIMwithNewTelco" "latestTandCsNotApproved" "IdDocumentExpired" "5yrsSinceLastCheckExceeded" ...

This would make it so much easier for our support to help them and avoid so many frustrations.

Many thanks in advance!

paulmuntean commented 3 years ago

@ralfhauser that happens when the Mobile ID is not active or cannot be reached.

Please open an NIC and call the following tel. nr. too see exactly what is the issue in your particular case.

Please call here: Tel. On 0800 724 724 and have your Pro number ready (is on the contract) or email ENT.Incident-Data@swisscom.com

The second option is not preferred as it can take up to 3 days to open.

ralfhauser commented 3 years ago

@paulmuntean Thanks for the hint. Our history with your support organizations shows more cases than the 2 causes you mention.

We have used the full spectrum of your support channels/organizations with mixed results (the end-users were often not happy).

Therefore we suggest to extend the response with a reason such that we can avoid unnecessary cost on your and our side and increase end-user satisfaction.

ralfhauser commented 3 years ago

similarly, also give a reason when the verify returns "No confirmed evidences found for mobile number"

Incident #: 92886965 is another example where open a NIC and calling 0800 724 724 so far hasn't lead to an solution for the end-user

casparflintstone commented 2 years ago

Today we hat the following problem:

41792772010 "RAS61855c2d0392c5061f5e87a2","serialNumber" : "SAS011lzurwbjy2"

Answer od AIS service: "MobileID busy"

The client was AIS identified - but the MobileID was 'not activated' - we checked it on the MobileID portal. After reactivating the MobileID with the recovery code a new AIS identification is needed .... (serial number missmatch ...)

->how can a user be 'identified' with inactive MobileID?