You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing the OAuth connection flow, I noticed that the flow does not continue correctly when the user is not already logged in to their beehiiv account in the same browser session.
If the user is already logged in to beehiiv, clicking Connect to beehiiv from the WordPress plugin settings page takes the user to the OAuth authorization screen as expected.
However, if the user is not logged in to beehiiv, they are first asked to log in. After completing login, the user is redirected to the beehiiv dashboard instead of being taken to the OAuth authorization screen.
Steps to reproduce
Open a browser/incognito session where the beehiiv account is not already logged in.
Go to WordPress admin >beehiiv settings.
Click Connect to beehiiv.
Complete the beehiiv login flow.
Actual result
After successful login, the user is redirected to the beehiiv dashboard.
To continue the OAuth flow, the user needs to use browser back navigation, return to the WordPress plugin flow, and click Connect to beehiiv again. After doing this, the OAuth authorization screen appears.
Expected result
After successful beehiiv login, the user should continue to the OAuth authorization screen for the WordPress plugin, or otherwise continue the OAuth connection flow without needing to manually go back and click Connect to beehiiv again.
Expected flow:
Connect to beehiiv > beehiiv login > OAuth authorization screen > Grant access >redirected back to WordPress connected state
Description
While testing the OAuth connection flow, I noticed that the flow does not continue correctly when the user is not already logged in to their beehiiv account in the same browser session.
If the user is already logged in to beehiiv, clicking Connect to beehiiv from the WordPress plugin settings page takes the user to the OAuth authorization screen as expected.
However, if the user is not logged in to beehiiv, they are first asked to log in. After completing login, the user is redirected to the beehiiv dashboard instead of being taken to the OAuth authorization screen.
Steps to reproduce
Actual result
After successful login, the user is redirected to the beehiiv dashboard.
To continue the OAuth flow, the user needs to use browser back navigation, return to the WordPress plugin flow, and click Connect to beehiiv again. After doing this, the OAuth authorization screen appears.
Expected result
After successful beehiiv login, the user should continue to the OAuth authorization screen for the WordPress plugin, or otherwise continue the OAuth connection flow without needing to manually go back and click Connect to beehiiv again.
Expected flow:
Connect to beehiiv > beehiiv login > OAuth authorization screen > Grant access >redirected back to WordPress connected state
Screen recording
Details
Recording.3109.mp4