This is not acceptable solution because then user in Apple ID settings - Sign-In with Apple has each app separately what is not desired. From user's view it looks like he is creating new registration when apple native dialog offers adding name, choosing private/relay email etc. We have more than 5 app targets/variants but we can not achieve user

great

@ernestDev You will never get name prop (and any other except email) in id_token because of Apple's world. In google and facebook oauth 2.0 it works as you expect but not in Apple's world. You will get name only as GET['user'] after redirecting when user authorizes request/permissions. Note that there is a another problem - Apple adds GET['user'] only after first sign in. GET['user'] is json stringified string like: {"name":{"firstName":"...","lastName":"..."},"email":"..."}

It seems that automatic verification does not work at all. Just manual. Problem is when using short lived certs such as Lets Encrypt. It is really bothering to always verify manually.

Not working.