Skip to content

Conversation

@kwsantiago
Copy link
Contributor

Closes #138

@kwsantiago kwsantiago force-pushed the 138-grpc-auth branch 2 times, most recently from d730480 to ac1678e Compare November 26, 2025 20:15
@bennyhodl
Copy link
Owner

We should probably have authentication that doesn't just check a string but verifies a signature.

Or an API secret that the server can generate as an API key to verify in request

kormir-server has a HMAC authentication https://github.com/bennyhodl/kormir/pull/25/changes

@kwsantiago kwsantiago changed the title feat(security): add API key authentication for gRPC server feat(security): add HMAC authentication for gRPC server Jan 8, 2026
@kwsantiago
Copy link
Contributor Author

@bennyhodl good point, thank you for pointing out. Reflected in 709162e

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.

gRPC API exposed without authentication

2 participants