Open janinakimtrohlev opened 1 year ago
For now, this needs full tara authentication to complete, Done the chat UI part
waiting TARA to start testing this function.
BUG - Right now I tested. As CSA I can ask authentication and as End User the question comes to me, but if I push "Tuvastama" it shows "This page isn´t working".
Should be after as End User I push button "Tuvastama" it will allow to authenticate by myself with TARA.
Needs additional grooming and sub-issue. @1AhmedYasser will provide input.
Needs to be Modified/Added
BUG - I tried as End User authenticate, but "Tuvasta" (authenticate") button is not working. Nothing happens when I push on it. @varmoh tested it also, got the error screen as shown in screenshot, logs did not show anything.
The problem still exist.
BUG - CSA can initiate authentication and it goes to End User. But after End User authenticate himself, the information is not coming to CSA and conversation begins again from 0. So it close automatically the conversation.
Should be when CSA initiate authentication, the question should go to End User. Then when end user authenticate himself, conversation should continue and in conversation to End User should show that he is authenticated, also the information of authentication should go to CSA:
BUG - As CSA I tried to ask authentication. But this question comes for 1 second and disappears from CSA view and doesn't come to End User. Also as we have right now this problem, I can´t check the previous bug.
@baha-a https://github.com/buerokratt/Buerokratt-Chatbot/issues/46#issuecomment-1923715950 will also need to be addressed in here, they are both related
Can't test right now. Put to blocked status now.
BUG - I tested and as CSA I can initiate an authentication. But as End User I authenticate and it asks me again to authenticate. So the system don´t see that I did it already.
Should be as an End User I authenticate and it will show that I´m authenticated. Also this information about authentication should go to CSA.
BUG - After End User is authenticated ,in the dev " Küsi autentimist" button should be disabled.
Tested and done
AS A CSA, I WANT TO be able to have End User authenticate themselves via “authenticate” button from chat SO THAT it gives me detailed view whenever an End User’s personal data or proof of authentication is required to handle personalized information.
Acceptance criteria
[x] After CSA has sent authentication request, chat widget window displays authentication message with respective button;
[x] After end-user is authenticated, name and ID of end-user is displayed in message details (without authentication only vestleja: anonymous is shown).
[x] After authentication, name is also displayed in message header in name area instead of "anonymous" (anonüümne).
[x] Must be an event type message so there is a mark in chat history about requested authentication. Once authenticated, the authentication button is disabled;