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.

Sign up for GitHub

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

Jump to bottom

Strapi transfer does not work with aws waf standard rules #20183

Closed
imfrostii8 opened this issue Apr 23, 2024 · 2 comments
Closed

Strapi transfer does not work with aws waf standard rules #20183

imfrostii8 opened this issue Apr 23, 2024 · 2 comments
Labels
flag: question Automation Flag to handle community questions

Comments

@imfrostii8
Copy link

Bug report

Required System information

  • Node.js version: v21.5.0
  • NPM version: 10.2.4
  • Strapi version: 4.15.5
  • Database: postgresql

Describe the bug

When running strapi transfer from or to a remote hosted on aws with a standard waf it shows: error: [FATAL] Failed to initialize the connection: Authorization Error
Transfer process failed.

The waf runs the core rule set based on vulnerabilities published by OWASP.

Steps to reproduce the behavior

  1. Start a new strapi project.
  2. Deploy it to aws with a waf in front of it.
  3. Run the strapi transfer command from or to the remote instance.

Expected behavior

It should transfer data normally to and from the remote instance.

Additional context

Disabling the wof solves the issue
@derrickmehaffy derrickmehaffy added the flag: question Automation Flag to handle community questions label Apr 23, 2024
@github-actions GitHub Actions
Copy link
Contributor

This is a templated message

Hello @imfrostii8,

I see you are wanting to ask a question that is not really a bug report,

Please see the following contributing guidelines for asking a question here.

Thank you.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 23, 2024
@derrickmehaffy
Copy link
Member

DTS auth is no different than normal user auth since it uses a bearer token in an authorization header.

Closing as a question since this really isn't related to us and is more so about properly configuring the WAF for authorization header usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flag: question Automation Flag to handle community questions
Projects
Support team
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@derrickmehaffy @imfrostii8