Try the beta version of the new SilverStripe documentation

For the next 2 weeks you can use the new documentation website and give us your feedback.

close

This document contains information for an outdated version (3.0) and may not be maintained any more.

If some of your projects still use this version, consider upgrading as soon as possible.

Access Control and Page Security

There is a fairly comprehensive security mechanism in place for SilverStripe. If you want to add premium content to your site you have to figure this stuff out, and it's not entirely obvious.

Ways to restrict access

There are a number of ways to restrict access in SilverStripe. In the security tab in the CMS you can create groups that have access to certain parts. The options can be found on the permissions documentation.

Once you have groups, you can set access for each page for a particular groups. This can be:

  • anyone
  • any person who is logged in
  • a specific group

It is unclear how this works for data-objects that are not pages.

The Security Groups in SilverStripe

In the security tab you can make groups for security. The way this was intended was as follows (this may be a counter intuitive):

  • employees
  • marketing
    • marketing executive

Thus, the further up the hierarchy you go the MORE privileges you can get. Similarly, you could have:

  • members
  • coordinators
    • admins

Where members have some privileges, coordinators slightly more and administrators the most; having each group inheriting privileges from its parent group.

Permission checking is at class level

SilverStripe provides a security mechanism via the Permission::check method (see LeftAndMain for examples on how the admin screens work)

(next step -- go from Permission::checkMember...)

Nuts and bolts -- figuring it out

Here are my notes trying to figure this stuff out. Not really useful unless you're VERY interested in how exactly SS works.

Loading the admin page: looking at security

If you go to [your site]/admin Director.php maps the 'admin' URL request through a Director rule to the CMSMain controller (see CMSMain, with no arguments).

CMSMain.init() calls its parent which, of all things is called LeftAndMain. It's in LeftAndMain that the important security checks are made by calling Permission::check.

Security::permissionFailure is the next utility function you can use to redirect to the login form.

Customizing Access Checks in CMS Classes

see LeftAndMain

Comments

Comment policy: Please use comments for tips and corrections about the described functionality.
Comments are moderated, we reserve the right to remove comments that are inappropriate or are no longer relevant. Use the Silverstripe Forum to ask questions.

blog comments powered by Disqus