Task #5440

Security should have its own configuration file

Added by Robert Lemke about 10 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Should have
Category:
Configuration
Start date:
2009-11-19
Due date:
% Done:

100%

Sprint:
PHP Version:
Has patch:
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

Revision 35190454 (diff)
Added by Andreas Förthner almost 10 years ago

[+TASK] FLOW3: Moved the security policy configuration to its own Policy.yaml file. Resolves #5440

History

#1 Updated by Robert Lemke about 10 years ago

  • Status changed from New to Accepted
  • Assignee set to Robert Lemke
  • Target version set to 1.0 alpha 7

#2 Updated by Robert Lemke about 10 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 almost 10 years ago

  • Target version changed from 1.0 alpha 7 to 1.0 alpha 8

#4 Updated by Robert Lemke almost 10 years ago

  • Assignee changed from Robert Lemke to Andreas Förthner

#5 Updated by Andreas Förthner almost 10 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r3824.

Also available in: Atom PDF