Coder plugin: Fallback authentication button still appears after user has already authenticated

Open
#146 0 comments 0 reactions 1 assignee View on GitHub

@buenos-nachos is already working on this.

Since Jan 6, 2025.

Assessment

This issue has not been assessed yet.

Description

bug

Issue comes from a customer – moving an anonymized version here for more visibility.

Problem

When the Coder plugin is integrated into a Backstage deployment, authentication doesn't always work as expected. The authentication elements don't appear/disappear consistently, and interacting with an element that does not exist sometimes causes the deployment to blow up.

Steps to reproduce

  1. Add the CoderProvider and CoderWorkspacesCard components to a deployment
  2. Navigate to whichever page has the card and authenticate via its built-in UI
  3. Navigate to a different page.
  4. See that the fallback "Authenticate with Coder" button is present at the bottom of the screen, even though the user should already be authenticated
  5. Click the button – the application blows up
Dominant language
TypeScript
Stars
67
Forks
9
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/backstage-plugins

All issues in coder/backstage-plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.