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
Or you can respond with native account token using loginToken:
{
"loginToken":"your-auth-token"
}
The workaround is simple - the response needs to include both properties, but it takes time to figure out what's the problem. Either the code or documentation needs to be fixed.
Server Setup Information:
Version of Rocket.Chat Server: 0.58.2
Operating System: Ubuntu 16.04 LTS
Deployment Method(snap/docker/tar/etc): snap
Number of Running Instances: 1
DB Replicaset Oplog:
Node Version:
Steps to Reproduce:
Enable and configure iframe integration as described in documentation, using "loginToken" only in the response
Open Rocket.Chat in browser and monitor network data in dev tools
Note the network requests in browser dev tools
Expected behavior:
Apart from Rocket.Chat resources, one request to login API URL
Actual behavior:
One request to API URL. Then another request to iframe URL.
Relevant logs:
The text was updated successfully, but these errors were encountered:
astax-t
pushed a commit
to astax-t/Rocket.Chat
that referenced
this issue
Sep 14, 2017
Description:
When using iframe login, the client code checks for presence of "token" value in the response ( https://github.com/RocketChat/Rocket.Chat/blob/develop/packages/rocketchat-iframe-login/iframe_client.js#L69 ). But the documentation at https://rocket.chat/docs/developer-guides/iframe-integration/authentication/ says :
The workaround is simple - the response needs to include both properties, but it takes time to figure out what's the problem. Either the code or documentation needs to be fixed.
Server Setup Information:
Steps to Reproduce:
Expected behavior:
Apart from Rocket.Chat resources, one request to login API URL
Actual behavior:
One request to API URL. Then another request to iframe URL.
Relevant logs:
The text was updated successfully, but these errors were encountered: