sigcli-auth-proxy

Run sig login followed by the site URL, for example sig login https://jira.example.com. The CLI opens a browser for SSO login, extracts session cookies automatically, and stores them encrypted for later authenticated requests.

Use sig request with the target URL to make direct authenticated calls, or start sig proxy --port 8080 and route HTTP traffic through it. Credentials are injected from encrypted local storage and never appear in environment variables or shell history.

Yes, configure a provider with strategy oauth2, tokenUrl, clientId, and clientSecret in ~/.sig/config.yaml. The CLI obtains access tokens and refreshes them automatically when they expire.

Validation fails when the validateUrl returns HTTP 200 even for logged-out users. Add a validateRule JavaScript expression such as res.body.status_code === 0, or point validateUrl at an endpoint that returns 401 when unauthenticated.

Yes, add an extract entry with from localStorage, the storage key in match, and a jsonPath for nested values. This works for apps like Slack that store tokens such as xoxc in localStorage instead of cookies.

Credentials are encrypted with AES-256-GCM and stored in ~/.sig/credentials/ with file mode 600. An audit log is kept in ~/.sig/logs/, and sig get redacts tokens by default unless --no-redaction is passed.