PULP-2347: forward encoded VPN secret from Vault - #1474
Merged
Merged
Conversation
Contributor
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThe nginx VPN proxy now treats the Vault secret as the complete base64-encoded wire value and forwards it unchanged to Akamai, eliminating runtime encoding; the changelog records the change, and deployments must supply the updated newline-free Vault value. Sequence diagram for forwarding the Vault-encoded VPN secretsequenceDiagram
participant Vault
participant NginxInit as NginxInit
participant Nginx
participant Akamai
Vault->>NginxInit: VPN_ACCESS_SECRET
NginxInit->>NginxInit: sed(..., VPN_ACCESS_SECRET, ...)
NginxInit->>Nginx: exec nginx -c /opt/nginx-rendered/nginx.conf
Nginx->>Akamai: X-Pulp-VPN-Access: VPN_ACCESS_SECRET
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
There was a problem hiding this comment.
Hey - I've reviewed your changes and they look great!
Sourcery assessment
Needs a human reviewer. This changes the credential material passed into nginx for VPN authentication; if the Vault value is not already in the expected encoding, VPN access could fail or the wrong credential could be accepted. Reverting restores the previous behavior, but an authentication mistake can affect access immediately and requires human verification.
Treat the Vault value as the base64-encoded wire secret and stop re-encoding it in nginx. Assisted-by: GPT-5.6 Luna
decko
force-pushed
the
pulp-2347-vpn-wire-secret
branch
from
September 14, 2026 15:37
449f182 to
0fa5ca6
Compare
Member
Author
|
/retest |
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.
Summary
Treat the Vault VPN secret as the base64-encoded wire value and forward it unchanged from nginx to Akamai.
Changes
X-Pulp-VPN-Access.Validation
git diff --checkpassed.Jira
PULP-2347
Labels: ai-assisted
Assisted-by: Claude
Summary by Sourcery
Forward the Vault-provided encoded VPN secret directly through nginx to Akamai.
Bug Fixes:
Deployment:
Chores: