The log out process is one that we use with our own authentication provider separate from the Genesys chat.
The app requires users to log in to use the app. Then inside the app the user can tap a button to "Chat to us". At which point we instantiate the Genesys ChatController using the SDK as per the docs.
We are passing in some customAttributes to the messengerAccount when we create the chatController.
This has allowed the chat back end to authenticate the user and get information from the back end about the user.
But after the user logs out and a new user logs in those customAttributes change.
Please check this section in the developer center, this is a generic explanation of Authenticated Messaging.
This will handle the different user logins and this is the next feature we will release this year.
Does it fit into your application?
The Clear Conversation feature will be delivered next year only, I don't have exact timeline yet for that.
Thanks for the link. I think this is what the web team implemented on the web chat for the site.
When the authenticated messaging is implemented in the mobile SDK will this also mean that only the chat history of the authorised user is shown?
i.e. if user A logs in and starts chatting with support.
Then user A logs out.
Then user B logs in and starts chatting with support.
User B won't see user A's history?
Do you have an ETA for the authenticated messaging in the mobile SDK just so I can feedback to the team?