Magento2: Update 2.2.1: One or more integrations have been reset because of a change to their xml configs.

[thomvanderboon]

I have a integration configured (System -> Integration). After update to 2.2.1 it keeps complaining about "Reauthorisation", but when you try to reauthorize this fails without any error message.

Preconditions

1. Ubuntu 16.04 LTS
2. MariaDB 10.2
3. PHP 7.0.22

Steps to reproduce

1. Have integration user configured before update
2. Update to 2.2.1
3. Try to reauthorize integration

Expected result

1. API user should be reautorized

Actual result

1. Nothing happens: API user not reautorized

[bondimedical3]

I reported this in M2.2.0 - they still haven't fixed it

[magento-engcom-team]

Hello @thomvanderboon. Thanks for reporting. Please tell us what was Your previous version You've been upgraded from to 2.2.1.

[thomvanderboon]

Upgrade 2.1.9 -> 2.2.0 without problems
Update 2.2.0 -> 2.2.1 gave this error

I use composer to update magento via the command line

[matin73]

same error for me - fresh installation 2.2.0 yesterday - today update to 2.2.1.
One or more integrations have been reset because of a change to their xml configs.
Magento Social

[magento-engcom-team]

@thomvanderboon, "One or more integrations have been reset because of a change to their xml configs" message is really there after update, but the user created in a previous version has not needed any reauthorizing. Or even if to have reauthorize that user, one is successfully reauthorized. Do You mean Your integration user can't work with Magento after the upgrade? If so, please provide us how You configured it while creating. Thank You.

[leoquijano]

Hello,

I have the same issue, starting when I upgraded 2.1.9 to 2.2.0. We're not using Magento Social at the moment, and would like to keep the integration off for the moment. Is there any way of removing it, or at least the error message?

[matin73]

I could solve it. i do know if it helps, but i changed api key and password with new generated user in marketplace for repro with
composer config http-basic.repo.magento.com xxx yyy
then i rerun
composer require magento/product-community-edition 2.2.1 --no-update
composer update
php bin/magento setup:upgrade

and then i logged in in admin, same error message but then i refreshed api of facebook social store and now message is gone ...

[bondimedical3]

@leoquijano to switch it off you can disable the Magento Social module from your Web Setup Wizard.

[leoquijano]

So php bin/magento module:disable Magento_Social also would work?

[bondimedical3]

Sorry but I did not test it with the cli but let me know how it goes.

[thomvanderboon]

If you have no other integrations running php bin/magento module:disable Shopial_Facebook will solve the problem

[magento-engcom-team]

@thomvanderboon could You be more clear please, the problem is only in that message appearing or Your integration user created in previous versions doesn't work.

[bondimedical3]

@leoquijano the answer provided by @thomvanderboon works

[leoquijano]

Thanks, everybody; it worked for me.

Any ideas why this isn't an opt-in feature? I'm thinking this may confuse some admins.

[thomvanderboon]

@magento-engcom-team I stopped using the oauth from my integration, because communicating via REST using tokens had no drawbacks for me.

I am currently setting up a new testshop to test your question. But have to do that next to my own work

[hostep]

I've seen this message popup for resetting the integration multiple times, I'm not exactly sure, but it might get triggered every time the app/etc/config.php file is changed. Not only after upgrading Magento to a newer version. So I think something is wrong in the logic and the integration shouldn't get reset so often. The config.xml file of the integration certainly wasn't changed the last time I've seen it popup, so it makes no sense that the integration resets itself so often.
It's currently very annoying to keep seeing this message popup all the time and then having to manually reset the integration. Would be great if someone could take a look at the logic about when integrations reset themselves because I suspect there is a bug in there somewhere.

It only seems to happen to the 'Magento Social' integration though, fortunately not to our custom integrations we added.

[magento-engcom-team]

@thomvanderboon, we are closing this issue due to inactivity. If you'd like to update it, please reopen the issue.

[eTonki]

Same problem,
i have updated from 2.1.9 to 2.2.1

[ci2014]

Same on 2.2.2

[suguna-e]

how to integrate the new theme activation for magento?

[matin73]

Same on 2.2.2

[emilshamloo]

I have installed 2.2.2 and I have this problem.
Is there any tutorial for newbies to follow?
Thansk in advane :-)

[harimayco]

Same problem on 2.2.2 developer mode.

[katiakweb]

Same problem!!! (2.2.2 developer mode.)

[treii28]

It will not function at all with a pop-up blocker running. When any pop-up blockers are disabled, it tries to open some link at https://fbapp.ezsocialshop.com/facebook/index.php with a notice saying 'log into or create a third party account to enable...' or something to that effect. But then the url never loads anything and times out in the pop-up window.

[nizzac]

Same problem!

[akosglue]

2.2.3 as well

[adamlavery]

Magento team,

As with some other integrations, this needs to be fully disabled from the start. Then if we want to use it we'll enable it. Anything that requires setting up should be fully disabled on install. We shouldn't have to jump through hoops to turn something off that we don't and probably won't ever want.

As it stands, pretty much anytime we update anything, this message comes back to the dashboard and we must go through the authorisation again, which fails but at least stops the message.

[czettnersandor]

I would also see this disabled as default along with Dotmailer, which is apparently generating huge amount of log entries. I do have a practice now to disable them from config.php for each new installation, but I would rather get rid of this practice and I believe most of us would have a better sleep if these features were disabled by default. Even better, keep it off from Magento codebase and release it on the Marketplace for those few who need it.

[ob7]

still a problem in 2.2.4. Disabling Shopial_Facebook from the command line removes the error.

[Mrunal13]

@thomvanderboon Thank you for your post, it really helped. :) :+1:

[CrumpetSmasher]

Just upgraded to 2.2.5 and experiencing this problem.

Disabled module Shopial_Facebook via CLI as suggested by thomvanderboon but the error still occurs.

The problem is I have an active integration with a WMS and the auth token keeps getting reset breaking the integration 2 or 3 times a day.

[magento-engcom-team]

Hi @thomvanderboon. Thank you for your report.
The issue has been fixed in magento/magento2#14065 by @therool in 2.2-develop branch
Related commit(s):

• 89a0a09f2b843948b1f784d077506dcee834efd9
• 5815a2073d4703eccbb12100e1bbe7dc48bb79bb
• 406935b76fc45ad326e0001d6afa3df9e478dfaf
• 3868e814def1b8886c2c33a191f7e0ff306a2172
• 42eab522219d118918dcb50c154b1f84be42861f

The fix will be available with the upcoming 2.2.8 release.

[slavvka]

Hi @thomvanderboon. Thank you for your report.
The issue has been fixed in magento/magento2#18273 by @mage2pratik in 2.3-develop branch
Related commit(s):

• 6c33d206e999554ff26e45ed3ab6d30e70adf1aa
• 0b3fe71e45d9126c60e00f5333ca208bba01c990
• 31b7f072622fe738ec26cfc5c576ac429e8b6337
• 999d8e56b8aa8a4e943692321acbfb3fbb2b5ed1
• 401b42318d39e1ebf1973051cea15d0ae85ce02e

The fix will be available with the upcoming 2.3.1 release.

[tonycr7]

Is it fixed in Magento 2.2.6?

[slavvka]

Hey @tonycr7,

The fix will be available with the upcoming 2.2.8 release.