Storage: Non OIDC users have to reload storage
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication
Research direction
Start by tracing the storage connection form action and how it creates a local-user session when OIDC is off. Follow the activation request to see why it uses the original headers without the newly issued session cookie. Done means a non-OIDC user can save and activate a storage connection in one submission without reloading.
Written by the indexing model from the issue text.
Description
When a user in a non OIDC environment sets up a storage connection he gets the following error message:
The connection was saved but could not be activated. Reload the page and select it from the saved connections.
With OIDC off, if a browser submitted the connect form without a valid session cookie, the server created a new local-user session during that same request, but its cookie only went out with the response. The action then tried to activate the saved connection using the original request headers, which had no session cookie, so better-auth returned 401 and the user got "saved but could not be activated".
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 39
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/cockpit
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stackabletech/cockpit#444 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
stackabletech/cockpit#385 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
stackabletech/cockpit#465 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
stackabletech/cockpit#462 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
stackabletech/cockpit#460 ·
Maintainers usually reply within 2 days
All issues in stackabletech/cockpit
Similar issues
-
bug parity
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
WenyuChiou/agent-board#1489 ·
Maintainers usually reply within 1 day
-
area: bazaar bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
accensa/x402-facilitator-stellar#779 ·
Maintainers usually reply within 1 day
-
bug good first issue P4 size:S web-ui
Difficulty 2/5 Half a day Newbie friendliness 85/100
josephfung/curia#2600 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cloudflare/partykit#444 ·