@@ -236,7 +236,7 @@ pattern so that it is only accessible by requests from the local server itself:
236
236
access_control :
237
237
#
238
238
# the 'ips' option supports IP addresses and subnet masks
239
- - { path: '^/internal', roles: IS_AUTHENTICATED_ANONYMOUSLY , ips: [127.0.0.1, ::1, 192.168.0.1/24] }
239
+ - { path: '^/internal', roles: PUBLIC_ACCESS , ips: [127.0.0.1, ::1, 192.168.0.1/24] }
240
240
- { path: '^/internal', roles: ROLE_NO_ACCESS }
241
241
242
242
10000
.. code-block :: xml
@@ -255,7 +255,7 @@ pattern so that it is only accessible by requests from the local server itself:
255
255
<!-- ... -->
256
256
257
257
<!-- the 'ips' option supports IP addresses and subnet masks -->
258
- <rule path =" ^/internal" role =" IS_AUTHENTICATED_ANONYMOUSLY " >
258
+ <rule path =" ^/internal" role =" PUBLIC_ACCESS " >
259
259
<ip >127.0.0.1</ip >
260
260
<ip >::1</ip >
261
261
</rule >
@@ -274,7 +274,7 @@ pattern so that it is only accessible by requests from the local server itself:
274
274
275
275
$security->accessControl()
276
276
->path('^/internal')
277
- ->roles(['IS_AUTHENTICATED_ANONYMOUSLY '])
277
+ ->roles(['PUBLIC_ACCESS '])
278
278
// the 'ips' option supports IP addresses and subnet masks
279
279
->ips(['127.0.0.1', '::1'])
280
280
;
@@ -302,7 +302,7 @@ address):
302
302
303
303
* Now, the first access control rule is enabled as both the ``path `` and the
304
304
``ip `` match: access is allowed as the user always has the
305
- ``IS_AUTHENTICATED_ANONYMOUSLY `` role.
305
+ ``PUBLIC_ACCESS `` role.
306
306
307
307
* The second access rule is not examined as the first rule matched.
308
308
@@ -407,7 +407,7 @@ access those URLs via a specific port. This could be useful for example for
407
407
security :
408
408
# ...
409
409
access_control :
410
- - { path: ^/cart/checkout, roles: IS_AUTHENTICATED_ANONYMOUSLY , port: 8080 }
410
+ - { path: ^/cart/checkout, roles: PUBLIC_ACCESS , port: 8080 }
411
411
412
412
.. code-block :: xml
413
413
@@ -424,7 +424,7 @@ access those URLs via a specific port. This could be useful for example for
424
424
<config >
425
425
<!-- ... -->
426
426
<rule path =" ^/cart/checkout"
427
- role =" IS_AUTHENTICATED_ANONYMOUSLY "
427
+ role =" PUBLIC_ACCESS "
428
428
port =" 8080"
429
429
/>
430
430
</config >
@@ -440,7 +440,7 @@ access those URLs via a specific port. This could be useful for example for
440
440
441
441
$security->accessControl()
442
442
->path('^/cart/checkout')
443
- ->roles(['IS_AUTHENTICATED_ANONYMOUSLY '])
443
+ ->roles(['PUBLIC_ACCESS '])
444
444
->port(8080)
445
445
;
446
446
};
@@ -461,7 +461,7 @@ the user will be redirected to ``https``:
461
461
security :
462
462
# ...
463
463
access_control :
464
- - { path: ^/cart/checkout, roles: IS_AUTHENTICATED_ANONYMOUSLY , requires_channel: https }
464
+ - { path: ^/cart/checkout, roles: PUBLIC_ACCESS , requires_channel: https }
465
465
466
466
.. code-block :: xml
467
467
@@ -478,7 +478,7 @@ the user will be redirected to ``https``:
478
478
<config >
479
479
<!-- ... -->
480
480
<rule path =" ^/cart/checkout"
481
- role =" IS_AUTHENTICATED_ANONYMOUSLY "
481
+ role =" PUBLIC_ACCESS "
482
482
requires-channel =" https"
483
483
/>
484
484
</config >
@@ -494,7 +494,7 @@ the user will be redirected to ``https``:
494
494
495
495
$security->accessControl()
496
496
->path('^/cart/checkout')
497
- ->roles(['IS_AUTHENTICATED_ANONYMOUSLY '])
497
+ ->roles(['PUBLIC_ACCESS '])
498
498
->requiresChannel('https')
499
499
;
500
500
};
0 commit comments