We have Campaign Classic v7 9123, hosted by Adobe on their AWS infrastructure. We're trying to switch from the standard Adobe authentication to Federated ID using Azure AD.
Adobe have configured our Dev instance, setting up the External Account for "Adobe Experience Cloud", and we've enabled Federation in the Admin Console using the Azure AD connector. We've verified the External Account configuration against the docs:
We've been going backwards and forwards for weeks now, and no closer to figuring out why this isn't work nor what we need to do to resolve. The exact same behaviour occurs when we use Adobe IDs and Federated IDs, so we're pretty sure it's not related to Federation / Azure AD. It does seem to be something to do with the callback trying to invoke "localhost" somewhere along the line, though that may be an Adobe Campaign error, not a local error.
I'd like to hear from any customers who have successfully enabled Adobe ID or Federated ID in Adobe Campaign Classic v7, and especially if you had and resolved this behavior.