You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue does not cover chat_message.write (傳送訊息至聊天室). Removing this scope requires siginificant rewrite of the chatbot workflows, which are outlined here.
The text was updated successfully, but these errors were encountered:
As-is
Currently Cofacts LIFF requests for
openid
andchat_message.write
scope.This triggers the following consent window when the user first opens Cofacts LIFF:
Currently the "用戶識別資訊 (必要資訊)" has caused confusion and intimidated users from proceeding.
To-be
We should use
profile
instead. If we do so, the consent window will become something similar to:The wording of "Profile" scope (個人檔案) is more welcoming to the users.
To achieve this, we should replace current ID token mechanism with access token + get profile API from chatbot server.
Furthermore, we can access
liff.getFriendship()
after we have access toprofile
scope, allowing us to display links to add Cofacts chatbot to those who did not.Implementation detail
/v2/profile
for theuserId
./oauth2/v2.1/verify
,/v2/profile
should be enough just for retrieving trustworthyuserId
from LINE.Other notes
urlToken
param mechanism.chat_message.write
(傳送訊息至聊天室). Removing this scope requires siginificant rewrite of the chatbot workflows, which are outlined here.The text was updated successfully, but these errors were encountered: