sst: 3.10 Breaks OpenAuth DNS

Upgrading to 3.10 with the new router breaks OpenAuth when using custom DNS. The tokens will get issued with the iss field as the underlying lambda url instead of the provided DNS.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 19 (7 by maintainers)

Most upvoted comments

Upgraded to 3.10.11 and it works with both google and github login, thanks

Upgraded to 3.10.11 and it resolved everything for me! Using the SST auth component. Thanks!

I have the same problem with adding domain to the Auth component, the redirect it gives to the oauth provider is the generated url instead of the custom domain, had to rollback to 3.9.44

Not fixed. Adding a domain to sst.aws.Auth still has OpenAuthProviders use the lambda url instead of the cloudfront one in the redirect_uri

Taking a look.