Bynder app Authentication issue

[vitalbone]

Describe the bug
There's an issue with the Contentful Bynder app. The correct Bynder environment is not persisted across Contentful environments in the same Contentful space. Looks like it’s not respecting the env configurations.

The issue occurs when logging into Bynder via the modal—by clicking on the “Select a file on Bynder” button—the user session is persisted across environments if a user changes Contentful environments. This results in the Bynder app potentially looking for assets in the Bynder production asset dam when in the Contentful development environment and vice-versa. I’ve logged a ticket with Bynder.

To Reproduce
Steps to reproduce the behavior:

1. Contentful space A + env A: Go to the Bynder app config, add your production Bynder URL
2. Contentful space A + env B: Go to the Bynder app config, add your development Bynder URL
3. Contentful space A + env A: Open a content entry and scroll to the Bynder app field
4. Contentful space A + env A: Click the "Select a file on Bynder" button
5. Contentful space A + env A: Log into the production Bynder env
6. Contentful space A + env A: See the assets from the production Bynder env
7. Contentful space A + env B: Swap to Contentful env B (in the same space)
8. Contentful space A + env B: Open a content entry and scroll to the Bynder app field
9. Contentful space A + env B: Click the "Select a file on Bynder" button
10. Contentful space A + env B: Notice the assets are still coming from the production Bynder app. Even though the app config should says it should come from the development Bynder env

Expected behavior
A user should be able to see the assets in the Bynder environment that corresponds to the Contentful environment.

Screenshots

Desktop (please complete the following information):

• OS: macOS 12.15.1
• Browser: Firefox
• Version: 103.0.2 (64-bit)

Additional context
Add any other context about the problem here.

[kdamball]

Hi @vitalbone, thanks for a great issue report. We included this issue in our team's backlog but I cannot promise about fix dates. We will add a comment when we have fixed it.

[vitalbone]

Thanks @kdamball - feel free to reach out if you have any questions when you (eventually/hopefully 🤞) get to it :)