github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 23:52:05 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #6973] [Signin with Apple] New requirement to provide server-to-server notification endpoint #28011

New Issue
Closed
opened 2026-04-17 19:21:01 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-17 19:21:01 -05:00
Owner
Copy Link

Originally created by @JeongJuhyeon on GitHub (Dec 24, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6973

Apple is starting to require developers to provide a server-to-server notification endpoint to use Sign in with Apple, including for the handling of Apple Account deletions as well as email forwarding changes.

For better-auth users who have integrated Apple as a provider, what's the suggested way forward here to satisfy this requirement?

Originally created by @JeongJuhyeon on GitHub (Dec 24, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6973 Apple is starting to require developers to provide a [server-to-server notification endpoint](https://developer.apple.com/news/?id=j9zukcr6) to use Sign in with Apple, including for the handling of Apple Account deletions as well as email forwarding changes. For better-auth users who have integrated Apple as a provider, what's the suggested way forward here to satisfy this requirement?
GiteaMirror added the oauth label 2026-04-17 19:21:01 -05:00
GiteaMirror commented 2026-04-17 19:21:04 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Dec 24, 2025):

To meet Apple's new requirement for a server-to-server notification endpoint when using Sign in with Apple, you'll need to implement a notification endpoint in your backend. This endpoint will handle notifications related to account deletions and email forwarding changes from Apple.

Here are the next steps for Better Auth users who have integrated Apple as a provider:

  1. Create the Notification Endpoint: Develop a server endpoint that can receive and process notifications sent by Apple. Ensure your endpoint validates incoming requests to confirm they are from Apple.

  2. Update Better Auth Configuration: In your Better Auth configuration, specify the new notification endpoint within the appropriate options where you're defining your social providers.

  3. Testing: Test the endpoint to ensure it correctly processes the notifications from Apple and handle any necessary actions, such as deleting user accounts or updating user email information.

  4. Monitoring: After deployment, monitor the endpoint to ensure it is receiving notifications properly and handling them as expected.

Feel free to ask if you need more detailed guidance on implementing any of these steps! Tag @better-auth-agent if you would like additional help!

If you need more help, tag @better-auth-agent in a comment so I can respond.

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3688772081 --> @better-auth-agent[bot] commented on GitHub (Dec 24, 2025): To meet Apple's new requirement for a server-to-server notification endpoint when using Sign in with Apple, you'll need to implement a notification endpoint in your backend. This endpoint will handle notifications related to account deletions and email forwarding changes from Apple. Here are the next steps for Better Auth users who have integrated Apple as a provider: 1. **Create the Notification Endpoint**: Develop a server endpoint that can receive and process notifications sent by Apple. Ensure your endpoint validates incoming requests to confirm they are from Apple. 2. **Update Better Auth Configuration**: In your Better Auth configuration, specify the new notification endpoint within the appropriate options where you're defining your social providers. 3. **Testing**: Test the endpoint to ensure it correctly processes the notifications from Apple and handle any necessary actions, such as deleting user accounts or updating user email information. 4. **Monitoring**: After deployment, monitor the endpoint to ensure it is receiving notifications properly and handling them as expected. Feel free to ask if you need more detailed guidance on implementing any of these steps! Tag @better-auth-agent if you would like additional help! _If you need more help, tag @better-auth-agent in a comment so I can respond._ <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/skyvern_ultra_detailed_interactive.html) • [Discord](https://discord.gg/fG2XXEuQX3) • [GitHub](https://github.com/Skyvern-AI/Skyvern) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/skyvern_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/fG2XXEuQX3) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/Skyvern-AI/Skyvern)
GiteaMirror commented 2026-04-17 19:21:04 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Mar 25, 2026):

Hi, @JeongJuhyeon. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary

  • You raised a concern about Apple's new requirement for a server-to-server notification endpoint for account deletions and email forwarding changes.
  • The Better Auth team responded with detailed guidance on how to create, configure, validate, test, and monitor this endpoint.
  • This guidance enables Better Auth users to comply with Apple's updated requirements.
  • The issue has been resolved with the provided instructions and support offer.

Next Steps

  • Please let me know if this issue is still relevant to the latest version of better-auth by commenting here.
  • Otherwise, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

<!-- gh-comment-id:4127832995 --> @dosubot[bot] commented on GitHub (Mar 25, 2026): Hi, @JeongJuhyeon. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary** - You raised a concern about Apple's new requirement for a server-to-server notification endpoint for account deletions and email forwarding changes. - The Better Auth team responded with detailed guidance on how to create, configure, validate, test, and monitor this endpoint. - This guidance enables Better Auth users to comply with Apple's updated requirements. - The issue has been resolved with the provided instructions and support offer. **Next Steps** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here. - Otherwise, this issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label oauth
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#28011
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?