feat(auth): normalize static credentials through auth context - #150
Draft
djwhitt wants to merge 4 commits into
Draft
feat(auth): normalize static credentials through auth context#150djwhitt wants to merge 4 commits into
djwhitt wants to merge 4 commits into
Conversation
Normalize the existing API Bearer key and web Basic credential into stable, non-secret principals and single-tenant auth contexts. Attach those contexts to authenticated Plug connections and LiveView sockets while preserving constant-time checks, pre-parser denial, session rotation, and the current capability surface. Require an explicit SMOLQUERY_AUTH_MODE=static for API and web roles, reject unsupported OIDC mode without fallback, and update deployment configuration and documentation for the fail-closed boot contract. Tests: ../bin/x mix ci Tests: ../bin/test Tests: ../bin/x mix dialyzer T-230
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 36071841 | Triggered | Generic Password | 6b434d3 | config/test.exs | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
djwhitt
changed the title
djwhitt
marked this pull request as draft
August 16, 2026 00:09
Carry the updated contract base and current origin/main into the published static-auth layer without rewriting existing commits.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SMOLQUERY_AUTH_MODE=staticfor API and web roles and reject unsupported OIDC mode without fallbackValidation
../bin/x mix ci../bin/test— 1,013 passed, 175 excluded../bin/x mix dialyzerT-230
Stacked on #144 with GitHub Stacks CLI.