Suddenly locked out from iTunes Connect. What could be the problem?

Thanks for that hint, Markus.

In my case however, I did not change the ADC login, nor did I any other change to my profile, neither in iTunes Connect, nor in ADC.

But your experience seems to show that iTunes Connect keeps the relation to the ADC login by name. So my guess is that for some reason the iTunes connect user name was changed, and now does not fit my ADC name any more. One indication I have for this is the suggestion I got from Apple that my apple ID should be entered as one word without spaces, but my Apple ID consists of my name as two words. Maybe they have run some normalisation procedure over the iTunes Connect logins that has cleaned out the space from my ID and therefore it does not match the actual ADC login any more (which still has a space).

I'll do some experiments along that line, and let you know if I succeed.

Thanks to your hint, Markus, I found the solution!

In fact, Apple apparently did some cleanup in the iTunes Connect login ID database. My original ID which was my name in two words, with a space in between, and both with uppercase first characters apparently got "cleaned" to a single all lowercase word with no space between first and last name.

What I did was to change my Apple ID in the ADC member profile to match the cleaned iTunes Connect version, and voila, I can login again.

In my case I had an indication what my "cleaned" version of my Apple ID probably is, because of one support answer suggesting to login with the all lowercase, no space version of my Apple ID. But I guess once you know that some cleaning process was ran over iTunes connect login IDs, you might be able to guess yours (no spaces, all lowercase, and probably no other special characters).

I'll report that back to Apple. I find it a bit strange that they seem not aware of what they did to their iTunes Connect login database and need external try and error research from us to solve the problem... In addition, I think this set up holds a massive security risk.

It seems that the iTunes connect is a two step process: First your credentials are verified using the centralized Apple ID authentication database. If you pass here, in the next step your Apple ID string will be used to find the iTunes connect account (one iTunes connect account can have more than one authorized user). If no account is found, you get the "Apple ID does not have permission to access iTunes Connect." error.

For this second step, iTunes connect apparently maintains a list of Apple ID strings literally, and somehow these got cleaned, normalized, mangled (ymmv) between July 16th and July 18th so they don't match the Apple ID (in some cases) any more from which they were once derived.

For those that never could login since they registered, I guess the automatic transfer of the Apple ID to iTunes was done with an unexpected name mangling in the first place. So I still think it might be worth trying to reverse engineer that mangling algorithm. In case of email addresses, maybe they filtered out less common characters like "-" or "_", so creating an Apple ID variant without these (if your email address does contains them) could help.

Sorry Alex, my suggestion was probably misleading.

It certainly does not help to change the Apple ID to some arbitrary new text with no special chars and spaces. Only if you can guess what the normalisation/cleanup process in iTunes Connect did to the copy of your Apple ID stored in iTunes connect, that might help.

In my case, removing the space and using all lowercase did the trick because that was in fact the modification that had happened in iTunes connect. With email addresses, I see no obvious normalisation/cleanup that could have happened, except maybe eliminating uppercase and eventually "-" and "_". But if your email address already was all lowercase, I'm out of ideas..

But I'd try the hint from johnnylundy (see above) to click the activation link again, maybe this can re-establish the broken link between Apple ID and iTunes Connect (I haven't tried, but would make sense).