failure openid_connect_sub_mismatch #2

AtProtocol Discourse Community sign up gives failure?message=openid_connect_sub_mismatch&origin=%2Fc%2Fprivatedatawg%2F16&strategy=oidc

Steps to reproduce:

1. Navigate to https://discourse.atprotocol.community/c/privatedatawg/16
2. Click Sign Up
3. I am redirected to https://auth.smokesignal.events/oauth/authorize?client_id=6824288b-0c2f-4cb1-befb-50d1fc9e7472&code_challenge=lJ0rFEWCSiAb31Xc1JGzH2CZ6s21Gn1jzexrsCYww3o&code_challenge_method=S256&nonce=e0c2792b5b8cddb44206d305304cdef3d1bcbf5935f93f250b4142fb3c55277d&redirect_uri=https%3A%2F%2Fdiscourse.atprotocol.community%2Fauth%2Foidc%2Fcallback&response_type=code&scope=openid+profile+email+account%3Aemail+atproto&state=6819956b0e97ae62c39f9f4bcaf8305270115ea110fb51fa
4. Enter my bluesky handle
5. I am redirected to Bluesky's OAuth login
6. Enter my password
7. Accept permissions
8. Get redirected to page that shows shows: "Sorry, there was an error while trying to authorize your account with oidc. Please try again." Url on that page is: https://discourse.atprotocol.community/auth/failure?message=openid_connect_sub_mismatch&origin=%2Fc%2Fprivatedatawg%2F16&strategy=oidc

Additional info: I tried with a different account before in which I unchecked the email permission. Tried deleting all cookies on all sites and a differnet browser and revoking smokesignal permissions and still didn't work. Tried with a different account, and allowed email permission and got the same error.

I am able to log into other services with bluesky that don't use AIP. For example, I did the same flow afterwards to create a tangled account here.

Could be a problem with the atproto discourse integration itself, wasn't sure.