X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2Fgetting-started-guide%2Fsecurity_considerations.rst;fp=docs%2Fgetting-started-guide%2Fsecurity_considerations.rst;h=fe06b33087fa82f8d327450b753f4d222be1c110;hb=e974986d3f5569db50b64e93bcf66803674af29c;hp=75ffc4711e1877e6da66ebf5426f008bed77c782;hpb=10340768b5a7e858711405f4957a65cbced4473c;p=docs.git diff --git a/docs/getting-started-guide/security_considerations.rst b/docs/getting-started-guide/security_considerations.rst index 75ffc4711..fe06b3308 100644 --- a/docs/getting-started-guide/security_considerations.rst +++ b/docs/getting-started-guide/security_considerations.rst @@ -182,7 +182,7 @@ Disabling the remote shutdown port ---------------------------------- You can lock down your deployment post installation. Set -``karaf.shutdown.port=-1`` in ``etc/custom.properties`` or ``etc/config.properties`` to +``karaf.shutdown.port=-1`` in ``etc/custom.properties`` to disable the remote shutdown port. Securing Southbound Plugins @@ -218,7 +218,7 @@ Securing RESTCONF using HTTPS To secure Jetty RESTful services, including RESTCONF, you must configure the Jetty server to utilize SSL by performing the following steps. -#. Issue the following command sequence to create a self-signed certificate for +#. Issue the following command sequence to create a self-signed certificate in the ``etc`` folder for use by the ODL deployment. :: @@ -243,7 +243,7 @@ Jetty server to utilize SSL by performing the following steps. #. After the key has been obtained, make the following changes to - the ``etc/custom.properties`` file to set a few default properties. + the ``etc/org.ops4j.pax.web.cfg`` file to set a few default properties. :: @@ -255,129 +255,17 @@ Jetty server to utilize SSL by performing the following steps. org.ops4j.pax.web.ssl.key.password=123456 org.ops4j.pax.web.ssl.key.alias=jetty -#. Then edit the ``etc/jetty.xml`` file with the appropriate HTTP connectors. - For example: - - :: - - - - - - - - - - https - - - - 32768 - 8192 - 8192 - - - false - - false - 512 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - jetty-default - - - - - - - - - - - - - - - karaf - karaf - - - org.apache.karaf.jaas.boot.principal.RolePrincipal - - - - - - - - - default - karaf - - - org.apache.karaf.jaas.boot.principal.RolePrincipal - - - - - - - - -The configuration snippet above adds a connector that is protected by SSL on -port 8443. You can test that the changes have succeeded by restarting Karaf, +You can test that the changes have succeeded by restarting Karaf, issuing the following ``curl`` command, and ensuring that the 2XX HTTP status code appears in the returned message. :: - curl -u admin:admin -v -k https://localhost:8443/restconf/modules + curl -u admin:admin -v -k https://localhost:8443/rests/operations + +A more advanced example of Jetty security configuration can be found in this article: +https://access.redhat.com/documentation/en-us/red_hat_jboss_fuse/6.3/html/security_guide/webconsole#idm139646384633952 Security Considerations for Clustering ======================================