New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
token_auth authentication should only work in the API and Widgetize #5655
Comments
I do not think so – I think that would be a nice feature. For example: Also this is advertising for the open source software. I would propose following: |
in 576 |
What about Widgetize? That process calls the API indirectly. We are experiencing problems because we are unable to use the Widgets in our drupal app because of this problem. We have to log in and the cookie allows the charts to work. It would be better if we could use the token_auth feature with Widgetize too. |
chuckdeal97 please see your feature request in #283 ; feel free to submit any ideas or patches |
reopening as I am now convinced that Widgetize is another special case where token_auth should work, at least until #283 is implemented. |
I dont know how to submit a patch but this is what I added in plugins/Login/Login.php
|
I am a bit confused; I generated the widget and manually added the token_auth in the widget URL, eg.```
|
(In [1935]) Fixes #5655 clarifying documentation regarding widget authentication |
Currently authenticating with token_auth works in all modules. We would want to restrict to API module, because there is no need for users to use this mechanism to login.
The text was updated successfully, but these errors were encountered: