Constant email codes no matter the fact that this option is turned off in control panel

Report · Aug 31, 2018

We have multiple Adobe accounts, which are used at different locations, but come from single ip address.

And our users almost terrorized with CONSTANT CAPTHA and email authentication code-requests.

Adobe support claims that Captcha comes from Google.

But email codes from Adobe keep coming even if this feature is disabled in control panel.

First query ADB-3338912-Q8Z5 was closed as resolved without doing anything.

Second query was dropped because i was visiting bathroom waaaay too long.

Third query ADB-3463640-M9B3 was closed with incoming call via phone saying "we resolved the situation", but guess what, nothing was resolved. Issue still there.

I don't have hopes for official atrocious "support", but would like to ask real users. Do any of you run into such situation with irksome email codes from adobe?

Is there any workaround to fix this modern mess?

Report · Aug 31, 2018

[moved from Adobe Creative Cloud to Deployment for Creative Cloud for Team, Enterprise, & CS]

Report · Sep 03, 2018

Hi,

I am not clear exactly what context these CAPTCHA requests appear in.

Are your users trying to sign in using their Adobe ID? Are they using social sign-in via facebook/google ?

If so please refer to the following articles

.

Resolve errors that can occur when signing in with your social account (Facebook or Google)

How to Disable Social sign in for Acrobat

Sign in to your Adobe ID account with your Facebook or Google account. Create a new Adobe ID account...

Report · Sep 03, 2018

Users are trying to sign in via standard Adobe ID, not via social stuff.

Report · Sep 03, 2018

Multiple logins from one IP address could be seen as suspicious hence triggering this mechanism.

To verify you would need to share logs with our engineering team - Contact Customer Care

Log Collector Tool

Report · Sep 03, 2018

I already reported our IP address. Thanks for log-collector link!

Weird that such tool was not mentioned by support in previous discussions via chat.

Report · Sep 06, 2018

Problem is finally resolved, somehow we get blacklisted via automated protection on Adobe side.