From version 7 it is not compatible.
opened 01:08PM - 11 Jun 20 UTC
closed 03:24PM - 16 Mar 21 UTC
enhancement
blocker
verified
integration
prioritised by payment
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 3.3
* Installation method (source, package, ..): any
* Operating system: any
* Database + version: any
* Elasticsearch version: any
* Browser + version: Google Chrome latest
* Ticket-ID: 1076705, 1076758 , 1076759
### Expected behavior:
Authentication against facebook, no matter if using the "add account" functionality for adding a new facebook channel or authentication itself for logging in to Zammad, the process will function successfully.
### Actual behavior:
If enabling API version 7, facebook complains about invalid scopes which are requested by Zammad during autorisation against facebook.
Old scopes are:
* publish_pages
* manage_pages
These scopes are, as far as I can tell, replaced by:
* pages_manage_engagement
* pages_manage_metadata
* pages_manage_posts
If provided with above mentioned permissions, Zammad will function with API version 6.
### Currently working solution:
Don't upgrade facebook Apps to API version 7 (neither for endusers nor developers).
facebook Apps up to API version 6 seems to be working without issues.
*Note: Downgrading developers API version from 7 to 6 is not possible - however, it is for endusers.*
### Steps to reproduce the behavior:
* have a app with required permissions ( `pages_manage_engagement, pages_manage_metadata, pages_manage_posts, email, default` )
* try to authenticate against facebook for either logging in to Zammad or adding a facebook page to the facebook channel
* to double tab you can test this with API version 6 and less and API version 7
* keep in mind that, as soon you upgrade API version to v7 for the developer, there's no way back
Yes I'm sure this is a bug and no feature request or a general question.
Thanks. So this means Zammad cannot be used with Facebook until this ticket is resolved or unless you have an app previous created with a lower version of the API.
Unfortunately, it is not possible to downgrade version
system
March 3, 2021, 3:40pm
5
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.