mirror of https://github.com/docusealco/docuseal
master
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.0.8
1.1.0
1.1.1
1.1.10
1.1.11
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.1.9
1.2.0
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
1.3.0
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.4.0
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.5.6
1.5.7
1.5.8
1.5.9
1.6.0
1.6.1
1.6.2
1.6.3
1.6.4
1.6.5
1.6.6
1.6.7
1.6.8
1.6.9
1.7.0
1.7.1
1.7.2
1.7.3
1.7.4
1.7.5
1.7.6
1.7.7
1.7.8
1.7.9
1.8.0
1.8.1
1.8.2
1.8.3
1.8.4
1.8.5
1.8.6
1.8.7
1.8.8
1.8.9
1.9.0
1.9.1
1.9.10
1.9.2
1.9.3
1.9.4
1.9.5
1.9.6
1.9.7
1.9.8
1.9.9
2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
2.0.6
2.0.7
2.0.8
2.0.9
2.1.0
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.2.0
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
${ noResults }
2 Commits (7ddafe0b130c7582206fe4d76cfce25864a9d1d3)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Bernardo Anderson
|
7ddafe0b13 |
CP-11289 - Migrate CloudFront config to environment variables
Remove hardcoded CloudFront domains and key pair IDs from repository. All CloudFront configuration now loaded from ENV variables for security: - CF_URL: CloudFront distribution URL - CF_KEY_PAIR_ID: CloudFront key pair identifier - CF_KEY_SECRET: AWS Secrets Manager path for private key - SECURED_STORAGE_BUCKET: S3 bucket name - SECURED_STORAGE_REGION: AWS region This prevents exposure of infrastructure identifiers in public repository. Configuration should be set via cpdocuseal deployment module. |
2 months ago |
|
Bernardo Anderson
|
bfcc59d70f |
CP-11289 - Add CloudFront signed URLs for secured document storage
Implement compliance storage configuration using AWS CloudFront signed URLs for completed documents. This reuses the existing ATS infrastructure to provide secure, time-limited access to document storage while maintaining backward compatibility with legacy storage. - Add aws-sdk-cloudfront dependency for URL signing - Create DocumentSecurityService for CloudFront signed URL generation - Add secured storage service configuration in storage.yml - Update completed_documents model with storage_location tracking - Modify download controllers to use signed URLs for secured storage - Add compliance_storage.yml configuration for different environments - Update submitter completion job to track storage location BREAKING CHANGE: Requires SECURED_STORAGE_BUCKET and SECURED_STORAGE_REGION environment variables for staging/production environments |
2 months ago |