You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by fc...@apache.org on 2013/01/03 11:03:05 UTC
svn commit: r1428255 -
/stanbol/site/trunk/content/development/security.mdtext
Author: fchrist
Date: Thu Jan 3 10:03:05 2013
New Revision: 1428255
URL: http://svn.apache.org/viewvc?rev=1428255&view=rev
Log:
Fixed title
Modified:
stanbol/site/trunk/content/development/security.mdtext
Modified: stanbol/site/trunk/content/development/security.mdtext
URL: http://svn.apache.org/viewvc/stanbol/site/trunk/content/development/security.mdtext?rev=1428255&r1=1428254&r2=1428255&view=diff
==============================================================================
--- stanbol/site/trunk/content/development/security.mdtext (original)
+++ stanbol/site/trunk/content/development/security.mdtext Thu Jan 3 10:03:05 2013
@@ -1,4 +1,4 @@
-Title:
+Title: Security Aware Coding
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -16,11 +16,8 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-Title: Security in Stanbol
-### General
-
-Stanbol uses standard [Java Security][1] for authorization. The permission can be set
+Apache Stanbol uses standard [Java Security][1] for authorization. The permission can be set
on a per user and per role basis using the user managers HTTP Api or UI. For the
documentation of the HTTP API see the [README][2] oth the usermanager. The UI is available
as a tab on the Webconsole. If stanbol is used within an application server the menchanisms
@@ -28,7 +25,7 @@ provided by this application servers mus
as well as to the code-base. Stanbol launchers have no code-based permission limitations
the code of all bundles is executed with full priviledges.
-### Writing security aware code
+## Writing security aware code
As for any Java libraries Stanbol modules should make sure they require a reasonable set of
permissions. This includes doing checks for permssions with the [AccessController][3] as well as