Buy Access to Course
34.

Whitelisting: Securing all Pages, except a few

Share this awesome video!

|

Keep on Learning!

Whitelisting: Securing all Pages, except a few

Next look again at access_control. Right now, our entire site is open to the public, except for the specific pages that we’re locking down in our controller.

But what if almost every page on our site required login? Is there a nice way to enforce this?

Add a new access control that matches all requests and requires ROLE_USER:

# app/config/security.yml
security:
    # ...
    access_control:
        - { path: ^/, roles: ROLE_USER }

Now, every page is locked down. Logout and try it. Mmm a redirect loop!

We’ve got too much security. When we go to any page, we don’t have access and are redirected to /login. Of course, we don’t have access to /login either, so we’re redirected to /login. Do you see the problem?

To fix this, add a new access_control entry above this for any page starting with /login. For the role, type IS_AUTHENTICATED_ANONYMOUSLY:

# app/config/security.yml
security:
    # ...
    access_control:
        - { path: ^/login, roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/, roles: ROLE_USER }

Refresh again. It works! We’re missing our styles, but we’ll fix that next. The access_control entries match from top to bottom and stop after the first match. When we go to /login, the first control is matched and executed. By saying IS_AUTHENTICATED_ANONYMOUSLY, we’re “whitelisting” this URL pattern because every user, even anonymous users, have this role.

Run the router:debug task to see a few other URLs that we should whitelist. These include some URLs that load our CSS files as well as the web debug toolbar and profiler during development. We also need to let anonymous users get to the registration page:

_assetic_01e9169 ANY /css/01e9169.css ... _wdt ANY /_wdt/{token} _profiler_home ANY /_profiler/ user_register ANY /register ...

We haven’t talked about assetic much yet, but by blocking it’s URLs, we’re blocking our stylesheets. With these entries in place, we’re in good shape:

# app/config/security.yml
security:
    # ...
    access_control:
        - { path: ^/login, roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/register, roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/(css|js), roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/(_wdt|_profiler), roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/, roles: ROLE_USER }