User: alborini
Date: 01/04/25 05:39:29
Modified: src/docs howtojaas.xml
Log:
- added section id for xref
- corrected a few typos
Revision Changes Path
1.5 +22 -20 manual/src/docs/howtojaas.xml
Index: howtojaas.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/howtojaas.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- howtojaas.xml 2001/03/22 19:58:56 1.4
+++ howtojaas.xml 2001/04/25 12:39:29 1.5
@@ -1,5 +1,5 @@
<?xml version = "1.0" encoding = "UTF-8"?>
-<section>
+<section id="howtojaas">
<title>JAAS Based Security in JBoss</title>
<subtitle>Custom Security in JBoss Using the JBossSX Framework</subtitle>
<para>Author:<author>
@@ -21,7 +21,7 @@
for both the standard declarative J2EE security model as well as custom
JAAS Subject based security. It should be sufficient to allow you to configure
a simple security setup for testing and also give you a good start to being
-able to inegrate your own custom security implementation into JBoss. For
+able to integrate your own custom security implementation into JBoss. For
a more detailed description of the JBossSX framework see the JBossSX
chapter.</para>
@@ -62,13 +62,13 @@
<title>Security Model Overview</title>
<para>The security model in JBoss is based on the server container
architecture's
pluggable method interceptors and the fact that the container factory always
-inserts security interceptor(org.jboss.ejb.plugins.SecurityInterceptor).
+inserts the security interceptor (org.jboss.ejb.plugins.SecurityInterceptor).
The SecurityInterceptor delegates the tasks of principal authentication
-and and principal role mapping to two different security interfaces;
+and principal role mapping to two different security interfaces:
org.jboss.security.EJBSecurityManager and org.jboss.security.RealmMapping.
JBoss includes a number of sample implementations of both interfaces which
can be found in the org.jboss.security.plugins.samples package.</para>
- <para>The default security implementation that comes pre-configured is
JMX service
+ <para>The default security implementation that comes pre-configured
consists of a JMX service
bean and a JAAS based implementation of both interfaces. The JMX bean is
org.jboss.security.plugins.JaasSecurityManagerService and the security
interfaces implementation is org.jboss.security.plugins.JaasSecurityManager.
@@ -116,7 +116,7 @@
</itemizedlist>
<section>
<title>security-domain</title>
- <para>The security-domain element specifies the an
implementation of both the
+ <para>The security-domain element specifies an
implementation of both the
org.jboss.security.RealmMapping and org.jboss.security.EJBSecurityManager
interfaces to use for all J2EE deployment units in the ear or ejb-jar.
The value is specified as the JNDI name where the object is located.
@@ -173,7 +173,7 @@
</calloutlist>
<para>Here we are assigning a global security manager
for all beans to the
the object located at java:/jaas/other and we are setting a different
-role mapping manager for the <quote>Standard Stateless
SessionBean</quote>container. This means that any stateless session beans bundled in
the
+role mapping manager for the <quote>Standard Stateless SessionBean</quote>
container. This means that any stateless session beans bundled in the
ear or jar will use the RealmMapper located at java:/jaas/session-roles rather
the the security-domain element setting.
We will see the reason for choosing JNDI names of the form java:/jaas/XXX
@@ -224,7 +224,7 @@
</section>
<section id = "jaas3">
<title>Using JaasSecurityManager</title>
- <para>As you would expect, the JaasSecurityManager uses JAAS(Java
Authentication and
+ <para>As you would expect, the JaasSecurityManager uses JAAS (Java
Authentication and
Authorization Service) to implement both the user authentication and role mapping
function of the RealmMapping and EJBSecurityManager interfaces. It does this by
creating
a JAAS Subject using the javax.security.auth.login.LoginContext mechanism. When
@@ -264,18 +264,18 @@
configured LoginModules for the security domain.</para>
</callout>
</calloutlist>
- <para>If your familiar JAAS, you'll see that the name that was used in
the creation of
+ <para>If you are familiar JAAS, you'll see that the name that was used
in the creation of
the JaasSecurityManager correlates with the LoginContext Configuration
name. The JAAS LoginContext object looks to a configuration object that is made up
of named sections that describe the LoginModules that need to be
executed in order to perform authentication. This abstraction allows the
-authentication api to be independent of a particular implementation. The
+authentication API to be independent of a particular implementation. The
authentication of users and the assignment of user roles comes down to
implementing a javax.security.auth.spi.LoginModule and creating login
configuration entry that correlates with the JaasSecurityManager name.
There exist a number of sample LoginModule implementation in the
org.jboss.security.plugins.samples package. We are going to use the
-JaasServerLoginModule to demonstrate the how to configure a LoginModule to
+JaasServerLoginModule to demonstrate how to configure a LoginModule to
work with the JaasSecurityManager. For your particular application you would
likely need different authentication and role mapping. You can choose another
LoginModule that integrates with your security environment, or implement you own
@@ -311,7 +311,7 @@
;
};</synopsis>See the JAAS documentation for the complete syntax description. In the
JBoss server
auth.conf file there should be an entry like 'other' in <xref linkend =
"server.auth.conf"/> below.
-Also shown is a 'session-roles' entry that we have added that specfies two
+Also shown is a 'session-roles' entry that we have added that specifies two
login modules.</para>
<figure id = "server.auth.conf">
<title>The JBoss Server JAAS Login Config File
@@ -375,7 +375,7 @@
};</programlisting>
</figure>
<note>
- <para>The configuration named 'other'
is used JAAS whenever it can't find
+ <para>The configuration named 'other'
is used by JAAS whenever it can't find
an entry matching the name passed to the LoginContext constructor. So
if we had used a JNDI name like java:/jaas/global as the security-domain
configuration element, we would still be using the 'other' login configuration
@@ -580,7 +580,7 @@
where ${jboss_home} is the location of your JBoss distribution.
@author [EMAIL PROTECTED]
-@version $Revision: 1.4 $
+@version $Revision: 1.5 $
*/
public class SessionClient
{
@@ -666,7 +666,7 @@
<para>The session beans are trivial and both the stateless and
stateful bean use the
same home and remote interfaces. The client is also trivial except for the use
of a JAAS LoginContext and CallbackHandler implementation. This is how a client
-establishes the username and password that is sent to jboss.
+establishes the username and password that is sent to JBoss.
Now, finally let's put everything together and deploy the session bean.</para>
</section>
<section id = "jaas5">
@@ -753,7 +753,7 @@
</step>
<step>
<para> Next, setup the classpath as
follows by substituting the value for jboss_home
- appropriate for your system. For example, I'm using jboss_home is a
+ appropriate for your system. For example, I'm using a
fresh build from cvs and jboss_home=/tmp/cvs/jboss/dist.
</para>
<literallayout>
@@ -846,7 +846,7 @@
<step>
<para>Start the JBoss server.
Go to the $jboss_home/bin directory and use the run.sh or run.bat script as
-appropriate for you system to start the JBoss server. You will see a good
+appropriate for your system to start the JBoss server. You will see a good
deal of ouput on your console. Below is some console output and I have
emphasized the session bean deployment output.</para>
<literallayout>
@@ -857,7 +857,9 @@
[Info] System: Windows 2000 5.0,x86
[Shutdown] Shutdown hook added
[Service Control] Registered with server
-[Service Control] Initializing 24 MBeans</computeroutput>...<emphasis>[Auto deploy]
Starting
+[Service Control] Initializing 24 MBeans
+...</computeroutput>
+<emphasis>[Auto deploy] Starting
[Auto deploy] Watching D:\tmp\cvs\jboss\dist\deploy
[Auto deploy] Auto deploy of file:/D:/tmp/cvs/jboss/dist/deploy/ssbean.jar
[J2EE Deployer Default] Deploy J2EE application:
file:/D:/tmp/cvs/jboss/dist/deploy/ssbean.jar
@@ -889,7 +891,7 @@
users with a role of 'Echo', and we have one user with a username 'scott'
and a password 'echoman' that has this role. We have another user with a
username 'stark' and a password 'javaman' that should not be able to
- acccess the session bean because he does not have the required role. We
+ access the session bean because he does not have the required role. We
need to setup the client env and run the client to test this.</para>
<substeps>
<step>
@@ -940,7 +942,7 @@
</literallayout>
</step>
<step>
- <para>Ok, so that succeed as desired.
Now we need to make sure that unauthorized
+ <para>Ok, so that succeeded as
desired. Now we need to make sure that unauthorized
users are actually denied access. This time run as user stark:</para>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development