[GH-ISSUE #1] OAuth provider signin fails after redirect #3

New issue

Closed

opened 2026-05-23 08:33:42 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-23 08:33:42 -06:00

Owner

Originally created by @appy-one on GitHub (Feb 26, 2021).
Original GitHub issue: https://github.com/appy-one/acebase-client/issues/1

Originally assigned to: @appy-one on GitHub.

After signing in with an OAuth2 provider, the user is successfully redirected back to the site with ?result=[base64 encoded data]. BUT, the function handling the redirect result fails because it uses Buffer.from to do the base64 decoding, which is not supported in the browser.

Example:

const result = client.auth.getRedirectResult(); // Error

Solution: add browser polyfill for base64 decoding (safely with utf8 characters)

Originally created by @appy-one on GitHub (Feb 26, 2021). Original GitHub issue: https://github.com/appy-one/acebase-client/issues/1 Originally assigned to: @appy-one on GitHub. After signing in with an OAuth2 provider, the user is successfully redirected back to the site with ?result=[base64 encoded data]. BUT, the function handling the redirect result fails because it uses ```Buffer.from``` to do the base64 decoding, which is not supported in the browser. Example: ```js const result = client.auth.getRedirectResult(); // Error ``` Solution: add browser polyfill for base64 decoding (safely with utf8 characters)