@@ -240,7 +240,7 @@ pattern so that it is only accessible by requests from the local server itself:
240
240
access_control :
241
241
#
242
242
# the 'ips' option supports IP addresses and subnet masks
243
- - { path: '^/internal', roles: IS_AUTHENTICATED_ANONYMOUSLY , ips: [127.0.0.1, ::1, 192.168.0.1/24] }
243
+ - { path: '^/internal', roles: PUBLIC_ACCESS , ips: [127.0.0.1, ::1, 192.168.0.1/24] }
244
244
- { path: '^/internal', roles: ROLE_NO_ACCESS }
245
245
246
246
.. code-block :: xml
@@ -259,7 +259,7 @@ pattern so that it is only accessible by requests from the local server itself:
259
259
<!-- ... -->
260
260
261
261
<!-- the 'ips' option supports IP addresses and subnet masks -->
262
- <rule path =" ^/internal" role =" IS_AUTHENTICATED_ANONYMOUSLY " >
262
+ <rule path =" ^/internal" role =" PUBLIC_ACCESS " >
263
263
<ip >127.0.0.1</ip >
264
264
<ip >::1</ip >
265
265
</rule >
@@ -278,7 +278,7 @@ pattern so that it is only accessible by requests from the local server itself:
278
278
279
279
$security->accessControl()
280
280
->path('^/internal')
281
- ->roles(['IS_AUTHENTICATED_ANONYMOUSLY '])
281
+ ->roles(['PUBLIC_ACCESS '])
282
282
// the 'ips' option supports IP addresses and subnet masks
283
283
->ips(['127.0.0.1', '::1'])
284
284
;
@@ -306,7 +306,7 @@ address):
306
306
307
307
* Now, the first access control rule is enabled as both the ``path `` and the
308
308
``ip `` match: access is allowed as the user always has the
309
- ``IS_AUTHENTICATED_ANONYMOUSLY `` role.
309
+ ``PUBLIC_ACCESS `` role.
310
310
311
311
* The second access rule is not examined as the first rule matched.
312
312
@@ -411,7 +411,7 @@ access those URLs via a specific port. This could be useful for example for
411
411
security :
412
412
# ...
413
413
access_control :
414
- - { path: ^/cart/checkout, roles: IS_AUTHENTICATED_ANONYMOUSLY , port: 8080 }
414
+ - { path: ^/cart/checkout, roles: PUBLIC_ACCESS , port: 8080 }
415
415
416
416
.. code-block :: xml
417
417
@@ -428,7 +428,7 @@ access those URLs via a specific port. This could be useful for example for
428
428
<config >
429
429
<!-- ... -->
430
430
<rule path =" ^/cart/checkout"
431
- role =" IS_AUTHENTICATED_ANONYMOUSLY "
431
+ role =" PUBLIC_ACCESS "
432
432
port =" 8080"
433
433
/>
434
434
</config >
@@ -444,7 +444,7 @@ access those URLs via a specific port. This could be useful for example for
444
444
445
445
$security->accessControl()
446
446
->path('^/cart/checkout')
447
- ->roles(['IS_AUTHENTICATED_ANONYMOUSLY '])
447
+ ->roles(['PUBLIC_ACCESS '])
448
448
->port(8080)
449
449
;
450
450
};
@@ -465,7 +465,7 @@ the user will be redirected to ``https``:
465
465
security :
466
466
# ...
467
467
access_control :
468
- - { path: ^/cart/checkout, roles: IS_AUTHENTICATED_ANONYMOUSLY , requires_channel: https }
468
+ - { path: ^/cart/checkout, roles: PUBLIC_ACCESS , requires_channel: https }
469
469
470
470
.. code-block :: xml
471
471
@@ -482,7 +482,7 @@ the user will be redirected to ``https``:
482
482
<config >
483
483
<!-- ... -->
484
484
<rule path =" ^/cart/checkout"
485
- role =" IS_AUTHENTICATED_ANONYMOUSLY "
485
+ role =" PUBLIC_ACCESS "
486
486
requires-channel =" https"
487
487
/>
488
488
</config >
@@ -498,7 +498,7 @@ the user will be redirected to ``https``:
498
498
499
499
$security->accessControl()
500
500
->path('^/cart/checkout')
501
- ->roles(['IS_AUTHENTICATED_ANONYMOUSLY '])
501
+ ->roles(['PUBLIC_ACCESS '])
502
502
->requiresChannel('https')
503
503
;
504
504
};
0 commit comments