Skip to content

bug: Browser provider fails saving storageState when ~/.aws/saml2aws does not exist #26

Closed

Description

@aspratt

Intake from triage §2 (upstream PR Versent#1522 ≈ Versent#1527). This is a direct follow-up of #4 (Playwright) and depends on PR #10.

Reproduce: run the Browser provider with HOME set to an empty dir. Fix: MkdirAll before saving, plus the err-check ordering fix from Versent#1522.

Activity

  1. added
    type:bugsaml2aws does something wrong that it is meant to do right
    nature:functionalSomething that exists and should work
    severity:S3Degraded, with an easy workaround
    on Oct 20, 2026
  2. aspratt commented on Oct 20, 2026

    @aspratt
    OwnerAuthor

    Fix in PR #33 (679c9f7): ~/.aws/saml2aws is created with 0700 before storageState is saved. Review (Sonnet) and e2e are in progress.

  3. added a commit that references this issue on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    nature:functionalSomething that exists and should workprovider:browserpkg/provider/browserseverity:S3Degraded, with an easy workaroundstatus:intakeStage 1: record openedtype:bugsaml2aws does something wrong that it is meant to do right

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions