Task #5440
Security should have its own configuration file
| Status: | Resolved | Start date: | 2009-11-19 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Andreas Förthner | % Done: | 100% |
|
| Category: | Configuration | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 8 | |||
| Sprint: | Has patch: | |||
| PHP Version: | Complexity: |
Description
Currently all security related options are configured in the FLOW3.yaml configuration file. As this configuration will become more extensive in the future and justifies its own class, we should introduce setting files called "Security.yaml" and move all security related options to them.
Associated revisions
[+TASK] FLOW3: Moved the security policy configuration to its own Policy.yaml file. Resolves #5440
History
#1 Updated by Robert Lemke over 5 years ago
- Status changed from New to Accepted
- Assigned To set to Robert Lemke
- Target version set to 1.0 alpha 7
#2 Updated by Robert Lemke over 5 years ago
Instead of moving all security related options to a Security.yaml file we should only externalize the policy section to a file called SecurityPolicies.yaml. The other options are comprehensive settings covering the whole security framework and therefore still belong to the FLOW3 Settings.yaml file.
#3 Updated by Robert Lemke over 5 years ago
- Target version changed from 1.0 alpha 7 to 1.0 alpha 8
#4 Updated by Robert Lemke over 5 years ago
- Assigned To changed from Robert Lemke to Andreas Förthner
#5 Updated by Andreas Förthner over 5 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r3824.