[Yanel-commits] rev 30693 - in
public/yanel/trunk/src/realms/yanel-website/content: .
66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep
66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions
66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413
66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822
michi at wyona.com
michi at wyona.com
Thu Jan 24 09:01:17 CET 2008
Author: michi
Date: 2008-01-24 09:01:16 +0100 (Thu, 24 Jan 2008)
New Revision: 30693
Added:
public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/
public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/content
public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/meta
public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/
public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/content
public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/meta
Modified:
public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52
public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/meta
Log:
para about authorization added
Modified: public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52
===================================================================
--- public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52 2008-01-24 07:48:24 UTC (rev 30692)
+++ public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52 2008-01-24 08:01:16 UTC (rev 30693)
@@ -2,5 +2,5 @@
<head> <title>Overview of Yanel Access Control Component</title>
</head>
-<body> <h1>Overview of Yanel Access Control Components</h1>Each Yanel realm can have its own IdentityManager and PolicyManager, whereas the IdentityManager is responsible for authentication and the PolicyManager for Authorization. Additionally a Yanel realm can also have its own WebAuthenticator, which can make sense if custom HTTP headers are being used, such as for instance for Single-Sign-On solutions.<br/><br/><h2>Authentication Usecases</h2>Yanel currently supports the following authentication usecases:<ul><li>HTTP BASIC and DIGEST<br/></li><li>Web Forms (XHTML)</li><li>Neutron</li><li>OpenID</li><li>Single-Sign-On through custom HTTP headers</li></ul>(please get in <a href="../../../mailing-lists.html">touch with the developers</a> if you have a need for another usecase)<br/><br/>Other usecases can be easily implemented by introducing a <a href="custom-identity-manager-custom-policy-manager.html">custom WebAuthenticator</a>. The actual authentication is being deleg!
ated in most cases (an exception is for instance OpenID) to the IdentityManager, whereas one can also introduce a <a href="custom-identity-manager-custom-policy-manager.html">custom IdentityManager</a> (e.g. LDAP authentication is currently done by a dedicated LDAPIdentityManager.</body>
+<body> <h1>Overview of Yanel Access Control Components</h1>Each Yanel realm can have its own IdentityManager and PolicyManager, whereas the IdentityManager is responsible for authentication and the PolicyManager for Authorization. Additionally a Yanel realm can also have its own WebAuthenticator, which can make sense if custom HTTP headers are being used, such as for instance for Single-Sign-On solutions.<br/><br/><h2>Authentication Usecases</h2>Yanel currently supports the following authentication usecases:<ul><li>HTTP BASIC and DIGEST<br/></li><li>Web Forms (XHTML)</li><li>Neutron</li><li>OpenID</li><li>Single-Sign-On through custom HTTP headers</li></ul>(please get in <a href="../../../mailing-lists.html">touch with the developers</a> if you have a need for another usecase)<br/><br/>Other usecases can be easily implemented by introducing a <a href="custom-identity-manager-custom-policy-manager.html">custom WebAuthenticator</a>. The actual authentication is being deleg!
ated in most cases (an exception is for instance OpenID) to the IdentityManager, whereas one can also introduce a <a href="custom-identity-manager-custom-policy-manager.html">custom IdentityManager</a> (e.g. LDAP authentication is currently done by a dedicated LDAPIdentityManager.<br/><br/><h2>Authorization</h2>Yanel supports URL based and content based access control. URL based means that with every URL an access control policy can be associated. Content based means that one can associate an access control policy with an arbitrary piece of content within a webpage (e.g. the phone number of a person is only being displayed if one is signed in and has the corresponding rights to see this phone number).<br/><br/>The access control policies are managed by the PolicyManager, whereas each realm can have its own PolicyManager and one can easily introduce a <a href="custom-identity-manager-custom-policy-manager.html">custom PolicyManager</a> for specific requirements. </body>
</html>
\ No newline at end of file
Modified: public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/meta
===================================================================
--- public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/meta 2008-01-24 07:48:24 UTC (rev 30692)
+++ public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/meta 2008-01-24 08:01:16 UTC (rev 30693)
@@ -1,7 +1,7 @@
yarep_type<string>:resource
yarep_isCheckedOut<boolean>:false
-yarep_size<long>:1424
-yarep_checkoutDate<date>:2008-01-24T10:12:26+0100
+yarep_size<long>:2119
+yarep_checkoutDate<date>:2008-01-24T10:41:03+0100
yarep_checkoutUserID<string>:michi
-yarep_lastModifed<long>:1201166591000
-yarep_checkinDate<date>:2008-01-24T10:23:11+0100
+yarep_lastModifed<long>:1201167792000
+yarep_checkinDate<date>:2008-01-24T10:43:12+0100
Added: public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/content
===================================================================
--- public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/content (rev 0)
+++ public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/content 2008-01-24 08:01:16 UTC (rev 30693)
@@ -0,0 +1,6 @@
+<?xml version="1.0"?><html xmlns="http://www.w3.org/1999/xhtml">
+<head> <title>Overview of Yanel Access Control Component</title>
+</head>
+
+<body> <h1>Overview of Yanel Access Control Components</h1>Each Yanel realm can have its own IdentityManager and PolicyManager, whereas the IdentityManager is responsible for authentication and the PolicyManager for Authorization. Additionally a Yanel realm can also have its own WebAuthenticator, which can make sense if custom HTTP headers are being used, such as for instance for Single-Sign-On solutions.<br/><br/><h2>Authentication Usecases</h2>Yanel currently supports the following authentication usecases:<ul><li>HTTP BASIC and DIGEST<br/></li><li>Web Forms (XHTML)</li><li>Neutron</li><li>OpenID</li><li>Single-Sign-On through custom HTTP headers</li></ul>(please get in <a href="../../../mailing-lists.html">touch with the developers</a> if you have a need for another usecase)<br/><br/>Other usecases can be easily implemented by introducing a <a href="custom-identity-manager-custom-policy-manager.html">custom WebAuthenticator</a>. The actual authentication is being deleg!
ated in most cases (an exception is for instance OpenID) to the IdentityManager, whereas one can also introduce a <a href="custom-identity-manager-custom-policy-manager.html">custom IdentityManager</a> (e.g. LDAP authentication is currently done by a dedicated LDAPIdentityManager.<br/><br/><h2>Authorization</h2>Yanel supports URL based and content based access control. URL based means that with every URL an access control policy can be associated. Content based means that one can associate an access control policy with an arbitrary piece of content within a webpage (e.g. the phone number of a person is only being displayed if one is signed in and has the corresponding rights to see this phone number). </body>
+</html>
\ No newline at end of file
Added: public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/meta
===================================================================
--- public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/meta (rev 0)
+++ public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167632413/meta 2008-01-24 08:01:16 UTC (rev 30693)
@@ -0,0 +1,12 @@
+yarep_revisionComment<string>:updated
+yarep_type<string>:resource
+yarep_isCheckedOut<boolean>:false
+yarep_revisionCreator<string>:michi
+workflow-date<date>:2008-01-24T10:40:32+0100
+yarep_size<long>:1854
+yarep_checkoutDate<date>:2008-01-24T10:32:49+0100
+yarep_checkoutUserID<string>:michi
+yarep_lastModifed<long>:1201167632000
+workflow-state<string>:draft
+yarep_checkinDate<date>:2008-01-24T10:23:11+0100
+yarep_revisionCreationDate<date>:2008-01-24T10:40:32+0100
Added: public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/content
===================================================================
--- public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/content (rev 0)
+++ public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/content 2008-01-24 08:01:16 UTC (rev 30693)
@@ -0,0 +1,6 @@
+<?xml version="1.0"?><html xmlns="http://www.w3.org/1999/xhtml">
+<head> <title>Overview of Yanel Access Control Component</title>
+</head>
+
+<body> <h1>Overview of Yanel Access Control Components</h1>Each Yanel realm can have its own IdentityManager and PolicyManager, whereas the IdentityManager is responsible for authentication and the PolicyManager for Authorization. Additionally a Yanel realm can also have its own WebAuthenticator, which can make sense if custom HTTP headers are being used, such as for instance for Single-Sign-On solutions.<br/><br/><h2>Authentication Usecases</h2>Yanel currently supports the following authentication usecases:<ul><li>HTTP BASIC and DIGEST<br/></li><li>Web Forms (XHTML)</li><li>Neutron</li><li>OpenID</li><li>Single-Sign-On through custom HTTP headers</li></ul>(please get in <a href="../../../mailing-lists.html">touch with the developers</a> if you have a need for another usecase)<br/><br/>Other usecases can be easily implemented by introducing a <a href="custom-identity-manager-custom-policy-manager.html">custom WebAuthenticator</a>. The actual authentication is being deleg!
ated in most cases (an exception is for instance OpenID) to the IdentityManager, whereas one can also introduce a <a href="custom-identity-manager-custom-policy-manager.html">custom IdentityManager</a> (e.g. LDAP authentication is currently done by a dedicated LDAPIdentityManager.<br/><br/><h2>Authorization</h2>Yanel supports URL based and content based access control. URL based means that with every URL an access control policy can be associated. Content based means that one can associate an access control policy with an arbitrary piece of content within a webpage (e.g. the phone number of a person is only being displayed if one is signed in and has the corresponding rights to see this phone number).<br/><br/>The access control policies are managed by the PolicyManager, whereas each realm can have its own PolicyManager and one can easily introduce a <a href="custom-identity-manager-custom-policy-manager.html">custom PolicyManager</a> for specific requirements. </body>
+</html>
\ No newline at end of file
Added: public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/meta
===================================================================
--- public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/meta (rev 0)
+++ public/yanel/trunk/src/realms/yanel-website/content/66e9f4aa-5232-440e-a40f-c6542bbf6d52.yarep/revisions/1201167792822/meta 2008-01-24 08:01:16 UTC (rev 30693)
@@ -0,0 +1,12 @@
+yarep_revisionComment<string>:updated
+yarep_type<string>:resource
+yarep_isCheckedOut<boolean>:false
+yarep_revisionCreator<string>:michi
+workflow-date<date>:2008-01-24T10:43:12+0100
+yarep_checkoutDate<date>:2008-01-24T10:41:03+0100
+yarep_size<long>:2119
+yarep_checkoutUserID<string>:michi
+yarep_lastModifed<long>:1201167792000
+workflow-state<string>:draft
+yarep_checkinDate<date>:2008-01-24T10:40:32+0100
+yarep_revisionCreationDate<date>:2008-01-24T10:43:12+0100
More information about the Yanel-commits
mailing list