You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
PostgreSQL Revocation Statements doesn't allow multiline queries as opposed to creation statements which take into consideration multline queries by searching for END keywords. Revocation statement lacks this logic.
To Reproduce
Steps to reproduce the behavior:
Create any PostgreSQL backend
For revocation statement use "DO $$ BEGIN CREATE ROLE \"reassign\"; EXCEPTION WHEN duplicate_object THEN RAISE NOTICE '%, moving to next statement', SQLERRM USING ERRCODE = SQLSTATE; END $$;"
See error in vault logs about PostgreSQL syntax error.
Expected behavior
Revocation statements should consider multiline queries.
Environment:
Vault Server Version (retrieve with vault status): 1.10.3
Vault CLI Version (retrieve with vault version): 1.10.3
Server Operating System/Architecture: Linux amd64
The text was updated successfully, but these errors were encountered:
Describe the bug
PostgreSQL Revocation Statements doesn't allow multiline queries as opposed to creation statements which take into consideration multline queries by searching for
END
keywords. Revocation statement lacks this logic.To Reproduce
Steps to reproduce the behavior:
"DO $$ BEGIN CREATE ROLE \"reassign\"; EXCEPTION WHEN duplicate_object THEN RAISE NOTICE '%, moving to next statement', SQLERRM USING ERRCODE = SQLSTATE; END $$;"
Expected behavior
Revocation statements should consider multiline queries.
Environment:
vault status
): 1.10.3vault version
): 1.10.3The text was updated successfully, but these errors were encountered: