Author: keith
Date: Mon Jul 21 02:03:56 2008
New Revision: 19766
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=19766

Log:
Adding a page for securing Mashups


Added:
   trunk/mashup/java/xdocs/images/assign_users_and_roles.png   (contents, props 
changed)
   trunk/mashup/java/xdocs/images/configure_security.png   (contents, props 
changed)
   trunk/mashup/java/xdocs/images/security_scenarios.png   (contents, props 
changed)
   trunk/mashup/java/xdocs/securingmashups.html
Modified:
   trunk/mashup/java/xdocs/toc.html

Added: trunk/mashup/java/xdocs/images/assign_users_and_roles.png
URL: 
http://wso2.org/svn/browse/wso2/trunk/mashup/java/xdocs/images/assign_users_and_roles.png?pathrev=19766
==============================================================================
Binary file. No diff available.

Added: trunk/mashup/java/xdocs/images/configure_security.png
URL: 
http://wso2.org/svn/browse/wso2/trunk/mashup/java/xdocs/images/configure_security.png?pathrev=19766
==============================================================================
Binary file. No diff available.

Added: trunk/mashup/java/xdocs/images/security_scenarios.png
URL: 
http://wso2.org/svn/browse/wso2/trunk/mashup/java/xdocs/images/security_scenarios.png?pathrev=19766
==============================================================================
Binary file. No diff available.

Added: trunk/mashup/java/xdocs/securingmashups.html
URL: 
http://wso2.org/svn/browse/wso2/trunk/mashup/java/xdocs/securingmashups.html?pathrev=19766
==============================================================================
--- (empty file)
+++ trunk/mashup/java/xdocs/securingmashups.html        Mon Jul 21 02:03:56 2008
@@ -0,0 +1,52 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html xmlns="http://www.w3.org/1999/xhtml";><head><!--
+~ Copyright 2005-2008 WSO2, Inc. (http://wso2.com)
+~
+~ Licensed under the Apache License, Version 2.0 (the "License");
+~ you may not use this file except in compliance with the License.
+~ You may obtain a copy of the License at
+~
+~ http://www.apache.org/licenses/LICENSE-2.0
+~
+~ Unless required by applicable law or agreed to in writing, software
+~ distributed under the License is distributed on an "AS IS" BASIS,
+~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+~ See the License for the specific language governing permissions and
+~ limitations under the License.
+-->
+
+<meta http-equiv="content-type" content=""><title>Securing Mashups</title>
+
+<link href="css/mashup-docs.css" rel="stylesheet" type="text/css" 
media="all"></head>
+<body lang="EN-US">
+<div id="main-content">
+<h1>Securing Mashups</h1>
+<p>The Mashup Server allows users to secure their mashups using
+WS-Security. All the complexities of WS-Security are hidden under the
+covers so that users can apply security scenarios of their mashups with
+ease. Once a security scenario is applied the coresponding WSDL of that
+mashup will display the WS-Security policy been engaged on that mashup.
+Hence consumers of this mashup will be able to consume your secured
+mashup by processing the information available in the WSDL.</p><p>Securing
+mashups deployed on the Mashup Server can be done by visiting the
+corresponding mashup page. If the user has already signed in he will
+see a link called "Configure Security Scenarios" in the configuration
+section on the mashup page (See image below). If the user has not set
+up his private key he will be redirected to the certificate manager page. 
Please refer the <a href="keystoremanagement.html">Keystore Management</a> 
section for setting up private keys.</p><img 
src="images/configure_security.png" style="width: 994px; height: 813px;" 
alt="Configure Security"><p></p>
+<h2 id="managing">Applying Security Scenarios</h2>
+<p>The Security Scenarios page list the security scenario that has been
+applied to a mashup. The Mashup Server ships with 15 most commonly used
+security scenarios and these scenarios can be applied onto a mashup by
+the click of a button. The default scenario engaged is 
unsecured.&nbsp;</p><p><img src="images/security_scenarios.png" style="width: 
1003px; height: 774px;" alt="Security Scenarios"></p><p></p>Some
+of the security scenarios listed above will require the user to specify
+the users and roles that the service will be opened to. These are the
+security scenarios that involve Username Token Authentication. When
+such a scenario is been applied you will be prompt with a list of
+available users and roles as follows,&nbsp;<br><br><img 
src="images/assign_users_and_roles.png" style="width: 1003px; height: 777px;" 
alt="Assign Users and Roles"><br><br>Providing
+access to the "mashup_user" role would mean that any registered user in
+the Mashup Server will be able to access this service. <br><br>NOTE:
+The generated stub provides facilities to access mashups secured using
+"UsernameToken with Timestamp over HTTPS" while the <a 
href="wsrequesthostobject.html">WSRequest host object</a> provides facilities 
to access any secured mashup.
+</div>
+<p>� 2007-2008 WSO2 Inc.</p>
+</body></html>
\ No newline at end of file

Modified: trunk/mashup/java/xdocs/toc.html
URL: 
http://wso2.org/svn/browse/wso2/trunk/mashup/java/xdocs/toc.html?rev=19766&r1=19765&r2=19766&view=diff
==============================================================================
--- trunk/mashup/java/xdocs/toc.html    (original)
+++ trunk/mashup/java/xdocs/toc.html    Mon Jul 21 02:03:56 2008
@@ -27,7 +27,7 @@
 Mashup Server Community</a></p>
 <p><a target="mainFrame" href="installationguide.html">Installation</a></p>
 <p><a href="adminguide.html" target="mainFrame">Managing
-Services</a></p>
+Services</a></p><ul><li><a href="securingmashups.html" 
target="mainFrame">Securing Mashups</a></li></ul>
 <p><a href="usermanagement.html" target="mainFrame">Managing
 Users</a></p>
 <ul>

_______________________________________________
Mashup-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/mashup-dev

Reply via email to