Open
Conversation
Author
|
Confirming that this passed on my end:
docker build -f Dockerfile-15 -t supabase-postgres:15 .
docker run --rm -d --name pg_rsa_test -e POSTGRES_PASSWORD=postgres supabase-postgres:15
docker exec -it pg_rsa_test psql -U supabase_admin -d postgres -c "CREATE EXTENSION pg_rsa;"
docker exec -it pg_rsa_test psql -U supabase_admin -d postgres -c "SELECT pg_rsa_test();" # built-in test suite |
Author
|
(note to self: after pr approved, need to add to: https://github.com/supabase/supabase/blob/master/packages/shared-data/extensions.json) |
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
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.
What kind of change does this PR introduce?
Adds small
pg_rsaextension that I made (designed to implementrsasigning and verifying in postgres function).What is the current behavior?
Currently, there is no way to sign in RSA directly in a postgres function.
What is the new behavior?
Adds RSA-functions: see https://github.com/barrownicholas/pg_rsa#functions
Additional context
Currently, I am trying to connect to Google APIs using a service account and a self-signed JWT, using a PEM private key. Google only supports RSA256. Unfortunately for me, there are no out-of-the-box solutions for RSA-signing in Postgres... until now! See https://github.com/barrownicholas/pg_rsa#functions.