JP Joom2Static - Security Recommendations
Article Index
- JP Joom2Static
- Why use JP Joom2Static?
- What's New in JP Joom2Static
- Installation
- General Configuration
- Menu and Asset Configuration
- Image Optimization
- .htaccess Settings
- Manual Files and Protected Sites
- Webhooks and REST API
- Deployment
- FTP Deployment
- Netlify Deployment
- AWS S3 Deployment
- GitHub Pages Deployment
- Generate Static HTML
- Configuration Parameter Reference
- Security Recommendations
- Conclusion
- All Pages
Page 18 of 19
Security Recommendations
JP Joom2Static can use credentials for external hosting and automation services. Keep all authentication details private.
Pay particular attention to the following values:
- Webhook Secret Token
- FTP Password
- Netlify Personal Access Token
- S3 Access Key
- S3 Secret Key
- GitHub Personal Access Token
- .htaccess Username and Password
Do not include these credentials in public screenshots, documentation, support posts, frontend HTML, or public Git repositories.
If any credential is accidentally exposed, revoke or rotate it immediately through the corresponding service.
