Skip to content

Commit 4958a29

Browse files
committed
Merge pull request #501 from stof/jms_repo
Updated the url for JMSSecurityExtraBundle
2 parents 6bbf459 + 7d0703b commit 4958a29

File tree

3 files changed

+24
-24
lines changed

3 files changed

+24
-24
lines changed

book/security.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -743,7 +743,7 @@ authorization from inside a controller:
743743
744744
.. _book-security-securing-controller-annotations:
745745

746-
You can also choose to install and use the optional ``SecurityExtraBundle``,
746+
You can also choose to install and use the optional ``JMSSecurityExtraBundle``,
747747
which can secure your controller using annotations:
748748

749749
.. code-block:: php
@@ -758,7 +758,7 @@ which can secure your controller using annotations:
758758
// ...
759759
}
760760
761-
For more information, see the `SecurityExtraBundle`_ documentation. If you're
761+
For more information, see the `JMSSecurityExtraBundle`_ documentation. If you're
762762
using Symfony's Standard Distribution, this bundle is available by default.
763763
If not, you can easily download and install it.
764764

@@ -1658,7 +1658,7 @@ Learn more from the Cookbook
16581658
* :doc:`/cookbook/security/remember_me`
16591659

16601660
.. _`security component`: https://github.com/symfony/Security
1661-
.. _`SecurityExtraBundle`: https://github.com/schmittjoh/SecurityExtraBundle
1661+
.. _`JMSSecurityExtraBundle`: https://github.com/schmittjoh/JMSSecurityExtraBundle
16621662
.. _`FOSUserBundle`: https://github.com/FriendsOfSymfony/FOSUserBundle
16631663
.. _`implement the \Serializable interface`: http://php.net/manual/en/class.serializable.php
16641664
.. _`functions-online.com`: http://www.functions-online.com/sha1.html

cookbook/security/acl_advanced.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ before it is returned.
162162

163163
Due to current limitations of the PHP language, there are no
164164
post-authorization capabilities build into the core Security component.
165-
However, there is an experimental SecurityExtraBundle_ which adds these
165+
However, there is an experimental JMSSecurityExtraBundle_ which adds these
166166
capabilities. See its documentation for further information on how this is
167167
accomplished.
168168

@@ -181,4 +181,4 @@ is applicable, the class-scope ACEs will be checked, if none is applicable,
181181
then the process will be repeated with the ACEs of the parent ACL. If no
182182
parent ACL exists, an exception will be thrown.
183183

184-
.. _SecurityExtraBundle: https://github.com/schmittjoh/SecurityExtraBundle
184+
.. _JMSSecurityExtraBundle: https://github.com/schmittjoh/JMSSecurityExtraBundle

cookbook/security/securing_services.rst

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -39,15 +39,15 @@ role. Before you add security, the class looks something like this:
3939
// ...
4040
}
4141
42-
Your goal is to check the user's role when the ``sendNewsletter()`` method is
43-
called. The first step towards this is to inject the ``security.context``
42+
Your goal is to check the user's role when the ``sendNewsletter()`` method is
43+
called. The first step towards this is to inject the ``security.context``
4444
service into the object. Since it won't make sense *not* to perform the security
4545
check, this is an ideal candidate for constructor injection, which guarantees
4646
that the security context object will be available inside the ``NewsletterManager``
4747
class::
4848

4949
namespace Acme\HelloBundle\Newsletter;
50-
50+
5151
use Symfony\Component\Security\Core\SecurityContextInterface;
5252

5353
class NewsletterManager
@@ -126,7 +126,7 @@ The injected service can then be used to perform the security check when the
126126
if (false === $this->securityContext->isGranted('ROLE_NEWSLETTER_ADMIN')) {
127127
throw new AccessDeniedException();
128128
}
129-
129+
130130
//--
131131
}
132132

@@ -139,9 +139,9 @@ be prompted to log in.
139139
Securing Methods Using Annotations
140140
----------------------------------
141141

142-
You can also secure method calls in any service with annotations by using the
143-
optional `SecurityExtraBundle`_ bundle. This bundle is included in the Symfony2
144-
Standard Distribution.
142+
You can also secure method calls in any service with annotations by using the
143+
optional `JMSSecurityExtraBundle`_ bundle. This bundle is included in the
144+
Symfony2 Standard Distribution.
145145

146146
To enable the annotations functionality, :ref:`tag<book-service-container-tags>`
147147
the service you want to secure with the ``security.secure_service`` tag
@@ -184,7 +184,7 @@ the :ref:`sidebar<securing-services-annotations-sidebar>` below):
184184
array(new Reference('security.context'))
185185
));
186186
$definition->addTag('security.secure_service');
187-
$container->setDefinition('newsletter_manager', $definition);
187+
$container->setDefinition('newsletter_manager', $definition);
188188
189189
You can then achieve the same results as above using an annotation::
190190

@@ -195,12 +195,12 @@ You can then achieve the same results as above using an annotation::
195195

196196
class NewsletterManager
197197
{
198-
198+
199199
/**
200200
* @Secure(roles="ROLE_NEWSLETTER_ADMIN")
201201
*/
202202
public function sendNewsletter()
203-
{
203+
{
204204
//--
205205
}
206206

@@ -210,12 +210,12 @@ You can then achieve the same results as above using an annotation::
210210
.. note::
211211

212212
The annotations work because a proxy class is created for your class
213-
which performs the security checks. This means that, whilst you can use
213+
which performs the security checks. This means that, whilst you can use
214214
annotations on public and protected methods, you cannot use them with
215215
private methods or methods marked final.
216216

217-
The ``SecurityExtraBundle`` also allows you to secure the parameters and return
218-
values of methods. For more information, see the `SecurityExtraBundle`_
217+
The ``JMSSecurityExtraBundle`` also allows you to secure the parameters and return
218+
values of methods. For more information, see the `JMSSecurityExtraBundle`_
219219
documentation.
220220

221221
.. _securing-services-annotations-sidebar:
@@ -235,7 +235,7 @@ documentation.
235235
jms_security_extra:
236236
# ...
237237
secure_all_services: true
238-
238+
239239
.. code-block:: xml
240240
241241
<!-- app/config/config.xml -->
@@ -245,18 +245,18 @@ documentation.
245245
xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
246246
247247
<jms_security_extra secure_controllers="true" secure_all_services="true" />
248-
249-
</srv:container>
248+
249+
</srv:container>
250250
251251
.. code-block:: php
252-
252+
253253
// app/config/config.php
254-
$container->loadFromExtension('jms_security_extra', array(
254+
$container->loadFromExtension('jms_security_extra', array(
255255
// ...
256256
'secure_all_services' => true,
257257
));
258258
259259
The disadvantage of this method is that, if activated, the initial page
260260
load may be very slow depending on how many services you have defined.
261261

262-
.. _`SecurityExtraBundle`: https://github.com/schmittjoh/SecurityExtraBundle
262+
.. _`JMSSecurityExtraBundle`: https://github.com/schmittjoh/JMSSecurityExtraBundle

0 commit comments

Comments
 (0)