Skip to content

fix: store permify credentials in ~/.permify/credentials#38

Open
tanayv77 wants to merge 3 commits into
Permify:mainfrom
tanayv77:feat/issue-2-client-credential-storage
Open

fix: store permify credentials in ~/.permify/credentials#38
tanayv77 wants to merge 3 commits into
Permify:mainfrom
tanayv77:feat/issue-2-client-credential-storage

Conversation

@tanayv77
Copy link
Copy Markdown

@tanayv77 tanayv77 commented May 31, 2026

/claim #2

Summary

  • store endpoint, token, cert path, and cert key in a dedicated per-profile ~/.permify/credentials file
  • keep the existing tenant/profile config focused on non-secret state
  • prompt for optional credential fields during permctl configure and load them when building the gRPC client
  • add regression tests proving the main config excludes credentials while load/write still reconstructs the full client config

Testing

@tanayv77 tanayv77 changed the title feat: store client credentials for secured permify connections fix: store permify credentials in ~/.permify/credentials May 31, 2026
@tanayv77
Copy link
Copy Markdown
Author

Follow-up update: PR #38 now also masks the access token during permctl configure, while keeping the maintainer-requested dedicated ~/.permify/credentials storage model. Validation still passes with go test ./....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Endpoint, Token, Cert Path, and Cert Key Storage for CLI Tool

1 participant