Unable to add Apple as identity provider per the sample

[mtanml]

I'm following the instructions at https://github.com/azure-ad-b2c/samples/tree/master/policies/sign-in-with-apple to add "Sign in with Apple" as a B2C identity provider.

I got to the very last step, and when I click Save I get the error "The issuer 'https://appleid.apple.com' found at the metadata endpoint {my endpoint} is already in use by an identity provider.

Are those instructions still valid?

[otsomkalov]

Facing the same issue. Any updates?

[JasSuri]

Looking into it for you.

[1iveowl]

Any update here? I'm facing the same issue as outlined above.

[1iveowl]

Added a StackOverflow question on this:

• Sign in with Apple guide - the metadata endpoint is already in use by an identity provider

[agrabhi]

Answered in SO.

[alanwoolley]

I'm also getting the same error despite not having a custom identity provider with the same issuer. If I change the issuer in my .well-known/openid-configuration file in any way, keeping the rest of the configuration the same, I can create a new provider.

[JasSuri]

There appears to be an issue here in regards to the conflict with the metadata endpoint, we are working on it.

[abastias]

I am having the same problem...
The issuer 'https://appleid.apple.com' found at the metadata endpoint '{My azure function}/.well-known/openid-configuration' is already in use by an identity provider.

Apple rejected my app because they want me to include "Sign in with Apple"

Any help will be very welcome.

[agrabhi]

The issue is resolved now. @JasSuri issue can be closed now.

[WhippsP]

Closing as per @agrabhi request.

[wojtekdo]

This fixed the problem for a single Apple ID provider. I need more of them and adding any consecutive gives me the same error.
I have many apps in different Apple developer accounts, with different services configured (different client Ids) and need users in a single AAD B2C tenant. IEF seems to enable this approach but not standard policies and I need them in a few places where exchanging policy to a custom one would be very difficult.

[agrabhi]

That's by design in basic policies

Azure AD B2C enforces the distinct issuer. The reason being that unique id of the user depends on the client Id in that system. If you have two apps in Facebook, Facebook will give you separate unique user Id for same user using different apps. So AADB2C wants that connection to one issuer is established through only one identity provider.

Any reason why you would want to use the same tenant?