Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secure Integration on Pantheon Doc Update #9089

Open
titomarifrancis-pantheon opened this issue Jul 11, 2024 · 2 comments
Open

Secure Integration on Pantheon Doc Update #9089

titomarifrancis-pantheon opened this issue Jul 11, 2024 · 2 comments
Assignees
Labels
Topic: Security Type: Fix Content Issue or PR to resolve incorrect information in the docs

Comments

@titomarifrancis-pantheon
Copy link
Contributor

Re: Secure Development on Pantheon

Priority: Medium

Issue Description:

Clients think we're just using 127.0.0.1 or loopback so some would argue that it's wrong

Suggested Resolution

Provide explanation for the reader that the IP 127.0.0.1 perceived as loopback is actually necessary for the Secure Integration tunnel to function alongside with the PHP constant defined by the client

Copy link

👋 @titomarifrancis-pantheon
Thanks for opening your first issue here! @pantheon-systems/docs-admins is excited to review this!

If you like this project, please ⭐star⭐ our repo.

@titomarifrancis-pantheon titomarifrancis-pantheon changed the title Secure Development on Pantheon Doc Update Secure Integration on Pantheon Doc Update Jul 11, 2024
@stevector stevector added Topic: Security Type: Fix Content Issue or PR to resolve incorrect information in the docs labels Jul 17, 2024
@rachelwhitton
Copy link
Member

Is the copy here enough or is it lacking? https://docs.pantheon.io/guides/secure-development/secure-integration#why-does-secure-integration-use-127001-or-loopback-ip-address

we could reposition this information as an Alert further up the page, is that the request here? Any additional info you can provide on the issue and recommended solution would be helpful. Thank you for opening this issue!

@rachelwhitton rachelwhitton self-assigned this Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Topic: Security Type: Fix Content Issue or PR to resolve incorrect information in the docs
Projects
None yet
Development

No branches or pull requests

3 participants