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
Enable Nextcloud as OAuth2 Provider for rocket.chat
Install rocket.chat desktop application (on any platform) and configure to login in nextcloud via OAuth2
Login does not work as the desktop-application tries to open an external window and fails with following error message Access Forbidden State token does not match: image
Expected behaviour
The OAuth2 Login from the rocket.chat desktop-app should work
Actual behaviour
The external browser window opens (out of the rocket.chat app) with an error message.
This is because, the rocket.chat app opens links with absolute URLs in a new window, i.e. the external browser window.
Server configuration
Operating system:
Ubuntu-18.04 Web server:
Nginx Database:
mysql PHP version:
Nextcloud version: (see Nextcloud admin page)
16.0.8 (also in 17.0.3) Updated from an older Nextcloud/ownCloud or fresh install:
from snap Where did you install Nextcloud from:
snap
Proposed Solution
in core/templates/loginflow/authpicker.php change this line
Steps to reproduce
Access Forbidden State token does not match
:image
Expected behaviour
The OAuth2 Login from the rocket.chat desktop-app should work
Actual behaviour
The external browser window opens (out of the rocket.chat app) with an error message.
This is because, the rocket.chat app opens links with absolute URLs in a new window, i.e. the external browser window.
Server configuration
Operating system:
Ubuntu-18.04
Web server:
Nginx
Database:
mysql
PHP version:
Nextcloud version: (see Nextcloud admin page)
16.0.8 (also in 17.0.3)
Updated from an older Nextcloud/ownCloud or fresh install:
from snap
Where did you install Nextcloud from:
snap
Proposed Solution
in
core/templates/loginflow/authpicker.php
change this lineI've tested the solution and it solves the problem. Are there any drawbacks to this, otherwise I'd open a pull-request for it.
The text was updated successfully, but these errors were encountered: