<<O>>  Difference Topic ShARPE (r1.14 - 12 Oct 2007 - BrucLiong)
META TOPICPARENT WebHome

Shibboleth Attribute Release Policy Editor (ShARPE)

Line: 47 to 47

What to do next

  1. Download page to fetch the software
Deleted:
<
<
  1. Installation of SP Description Editor

  1. Installation of ShARPE
  2. Uninstallation of ShARPE
  3. How to use ShARPE
  4. How to use Autograph
  5. Visual tours of ShARPE
Added:
>
>
  1. Installation of SP Description Editor (optional)

  1. Test-drive at OpenShARPE
  2. Extra (advanced) configuration of ShARPE
  3. ShARPE Mailing List
 <<O>>  Difference Topic ShARPE (r1.13 - 26 Aug 2007 - BrucLiong)
META TOPICPARENT WebHome

Shibboleth Attribute Release Policy Editor (ShARPE)

Line: 54 to 54
  1. How to use Autograph
  2. Visual tours of ShARPE
  3. Test-drive at OpenShARPE
Added:
>
>
  1. Extra (advanced) configuration of ShARPE

  1. ShARPE Mailing List
  2. Identity Provider Management Suite
 <<O>>  Difference Topic ShARPE (r1.12 - 30 May 2006 - BrucLiong)
META TOPICPARENT WebHome

Shibboleth Attribute Release Policy Editor (ShARPE)

Line: 49 to 49
  1. Download page to fetch the software
  2. Installation of SP Description Editor
  3. Installation of ShARPE
Added:
>
>
  1. Uninstallation of ShARPE

  1. How to use ShARPE
  2. How to use Autograph
  3. Visual tours of ShARPE
 <<O>>  Difference Topic ShARPE (r1.11 - 15 May 2006 - BrucLiong)
META TOPICPARENT WebHome

Shibboleth Attribute Release Policy Editor (ShARPE)

Line: 52 to 52
  1. How to use ShARPE
  2. How to use Autograph
  3. Visual tours of ShARPE
Added:
>
>
  1. Test-drive at OpenShARPE

  1. ShARPE Mailing List
  2. Identity Provider Management Suite
 <<O>>  Difference Topic ShARPE (r1.10 - 02 May 2006 - BrucLiong)
META TOPICPARENT WebHome
Changed:
<
<

Shibbolet Attribute Release Policy Editor (ShARPE)

>
>

Shibboleth Attribute Release Policy Editor (ShARPE)


Line: 27 to 27
  • inform admin and users on services they receive in return for their attributes, before they release anything
  • visualization of user's attributes (what user has, what rules in ARP, what released), via WebSharpe
Added:
>
>		 ShARPE and Autograph are part of the National Science Foundation Middleware Initiative (NMI) EDIT software release.NMI Logo

ShARPE and Autograph are licensed under Apache License, Version 2.0


ShARPE is composed of 3 components, SharpeCore, WebSharpe, and Autograph.

WebSharpe is a web interface for Sharpe to allow user and admin to interact with ShARPE. ShARPE can be fully functional without WebSharpe, however its use as user interface to ShARPE is recommended.

Line: 42 to 46

 SharpeCore is the core component of ShARPE. It sits ontop of current Shibboleth IdP and access/manipulate configuration files as used by the IdP. Introduction of SharpeCore would enable any IdP to benefit Sharpe's capabilities.

What to do next

Added:
>
>
  1. Download page to fetch the software

  1. Installation of SP Description Editor
  2. Installation of ShARPE
  3. How to use ShARPE
  4. How to use Autograph
  5. Visual tours of ShARPE
Added:
>
>
  1. ShARPE Mailing List

  1. Identity Provider Management Suite

-- BrucLiong - 24 Apr 2006

 <<O>>  Difference Topic ShARPE (r1.9 - 24 Apr 2006 - BrucLiong)
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

Line: 43 to 43

What to do next

  1. Installation of SP Description Editor
Changed:
<
<
  1. Installation of WebSharpe
  2. How to use WebSharpe
>
>
  1. Installation of ShARPE
  2. How to use ShARPE

  1. How to use Autograph
Changed:
<
<
  1. Visual tours of WebSharpe
>
>
  1. Visual tours of ShARPE
  2. Identity Provider Management Suite

Changed:
<
<		 Identity Provider Management Suite
>
>		 -- BrucLiong - 24 Apr 2006

Changed:
<
<		 -- BrucLiong - 16 Feb 2006

  • Service Description Schema:
    Service Description Schema

META FILEATTACHMENT sd.png attr="" comment="Service Description Schema" date="1140405934" path="sd.png" size="18386" user="NeilWitheridge" version="1.1"
META FILEATTACHMENT Sharpe.jpg attr="" comment="" date="1141956611" path="Sharpe.jpg" size="21699" user="MoritzTheile" version="1.1"
>
>
META FILEATTACHMENT sd.png attr="h" comment="Service Description Schema" date="1140405934" path="sd.png" size="18386" user="NeilWitheridge" version="1.1"
META FILEATTACHMENT Sharpe.jpg attr="h" comment="" date="1141956611" path="Sharpe.jpg" size="21699" user="MoritzTheile" version="1.1"
 <<O>>  Difference Topic ShARPE (r1.8 - 10 Mar 2006 - MoritzTheile)
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

Added:
>
>

ShARPE is developed as part of the collaboration between MAMS and Shibboleth. ShARPE's aim is to manage the creation and maintenance of user's attributes as defined by Attribute Release Policy (ARP) mechanism of Shibboleth.

In particular, ShARPE allows admins and users to easily manage their release attribute policy in a way that conforms to their privacy and satisfaction of users in gaining the services that they want (on service provider end)

Added:
>
>		 To do the crosswalk between different directory schemas mappings have to be defined. This can be achieved using the Crosswalker.

  IdP Management Suite

ShARPE is also an extension of Shibboleth providing other functionalities that are not existence in current Shibboleth, such as:

  • ability for admin to manage ARPs without manual editing of XML files
Line: 43 to 56

 Service Description Schema

META FILEATTACHMENT sd.png attr="" comment="Service Description Schema" date="1140405934" path="sd.png" size="18386" user="NeilWitheridge" version="1.1"
Added:
>
>
META FILEATTACHMENT Sharpe.jpg attr="" comment="" date="1141956611" path="Sharpe.jpg" size="21699" user="MoritzTheile" version="1.1"
 <<O>>  Difference Topic ShARPE (r1.7 - 09 Mar 2006 - MoritzTheile)
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

Line: 35 to 35
  1. How to use Autograph
  2. Visual tours of WebSharpe
Added:
>
>		 Identity Provider Management Suite

-- BrucLiong - 16 Feb 2006

  • Service Description Schema:
 <<O>>  Difference Topic ShARPE (r1.6 - 20 Feb 2006 - NeilWitheridge)
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

Line: 37 to 37

-- BrucLiong - 16 Feb 2006

Added:
>
>
  • Service Description Schema:
    Service Description Schema

META FILEATTACHMENT sd.png attr="" comment="Service Description Schema" date="1140405934" path="sd.png" size="18386" user="NeilWitheridge" version="1.1"
 <<O>>  Difference Topic ShARPE (r1.5 - 19 Feb 2006 - BrucLiong)
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

Line: 28 to 28

SharpeCore is the core component of ShARPE. It sits ontop of current Shibboleth IdP and access/manipulate configuration files as used by the IdP. Introduction of SharpeCore would enable any IdP to benefit Sharpe's capabilities.

Changed:
<
<		 IMAGE HERE illustrating Sharpe - WebSharpe - SharpeCore - Autograph

ONE IMAGE on WebSharpe

ONE IMAGE on Autograph

References

>
>

What to do next

  1. Installation of SP Description Editor
  2. Installation of WebSharpe
  3. How to use WebSharpe
  4. How to use Autograph
  5. Visual tours of WebSharpe

-- BrucLiong - 16 Feb 2006

 <<O>>  Difference Topic ShARPE (r1.4 - 17 Feb 2006 - BrucLiong)
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

Line: 9 to 9

 ShARPE is also an extension of Shibboleth providing other functionalities that are not existence in current Shibboleth, such as:
  • ability for admin to manage ARPs without manual editing of XML files
  • ability for users to manage their ARPs and extending what admin has set for them (institutional and group/community wide policy)
Changed:
<
<
  • ability to process group policy for users, i.e. Physics administrator may allow or disallow certain attributes to be released for all members in the Physics department
>
>
  • ability to process group policy for users, i.e. Physics administrator may allow or disallow certain attributes to be released for all members in the Physics department

  • ability to perform mapping of attributes from different schemas from simple mapping to complex one, i.e. IdP may define the attribute as mail but SP may understand it as email
  • inform admin and users on services they receive in return for their attributes, before they release anything
  • visualization of user's attributes (what user has, what rules in ARP, what released), via WebSharpe
Changed:
<
<		 ShARPE is composed of 3 components, SharpeCore, WebSharpe, and Autograph.
>
>		 ShARPE is composed of 3 components, SharpeCore, WebSharpe, and Autograph.

WebSharpe is a web interface for Sharpe to allow user and admin to interact with ShARPE. ShARPE can be fully functional without WebSharpe, however its use as user interface to ShARPE is recommended.

Line: 28 to 28

SharpeCore is the core component of ShARPE. It sits ontop of current Shibboleth IdP and access/manipulate configuration files as used by the IdP. Introduction of SharpeCore would enable any IdP to benefit Sharpe's capabilities.

Changed:
<
<		 IMAGE HERE illustrating Sharpe - WebSharpe - SharpeCore - Autograph
>
>		 IMAGE HERE illustrating Sharpe - WebSharpe - SharpeCore - Autograph

ONE IMAGE on WebSharpe

 <<O>>  Difference Topic ShARPE (r1.3 - 16 Feb 2006 - BrucLiong)
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

Line: 7 to 7

 In particular, ShARPE allows admins and users to easily manage their release attribute policy in a way that conforms to their privacy and satisfaction of users in gaining the services that they want (on service provider end)

ShARPE is also an extension of Shibboleth providing other functionalities that are not existence in current Shibboleth, such as:

Added:
>
>
  • ability for admin to manage ARPs without manual editing of XML files
  • ability for users to manage their ARPs and extending what admin has set for them (institutional and group/community wide policy)

  • ability to process group policy for users, i.e. Physics administrator may allow or disallow certain attributes to be released for all members in the Physics department
  • ability to perform mapping of attributes from different schemas from simple mapping to complex one, i.e. IdP may define the attribute as mail but SP may understand it as email
Added:
>
>
  • inform admin and users on services they receive in return for their attributes, before they release anything

  • visualization of user's attributes (what user has, what rules in ARP, what released), via WebSharpe

ShARPE is composed of 3 components, SharpeCore, WebSharpe, and Autograph.

Line: 21 to 24
  • overrule the release of particular attribute when it was set by admin
  • visualize what attributes released and how the ARPs affect the attributes
Changed:
<
<		 Autograph is another web interface that interacts with SharpeCore to illustrate the usage of idCard. The idea is that user would have lots of idCard to be use when s/he visits a SP. User can specify at the IdP which idCard to use for certain SP. Each idCard would have certain details containing user's attributes specifically agreed by user to be released for the SP. For example, I am a professor at university A and also a member of IEEE. When I visit an online bookshop (SP), I may choose idCard with some attributes that reveal the fact I am working in university environment only, however when I go to university's affiliated sites, I may use another idCard that specifies my membership in IEEE.
>
>		 Autograph is another web interface that interacts with SharpeCore to illustrate the usage of idCard. The idea is that user would have lots of idCard to be use when s/he visits a SP. User can specify at the IdP which idCard to use for certain SP. Each idCard would have certain details containing user's attributes specifically agreed by user to be released for the SP. For example, I am a professor at university A and also a member of IEEE. When I visit an online bookshop (SP), I may choose idCard with some attributes that reveal the fact I am working in university environment only, however when I go to university's affiliated sites, I may use another idCard that specifies my membership in IEEE.

SharpeCore is the core component of ShARPE. It sits ontop of current Shibboleth IdP and access/manipulate configuration files as used by the IdP. Introduction of SharpeCore would enable any IdP to benefit Sharpe's capabilities.

Line: 32 to 35

 ONE IMAGE on Autograph

References

Changed:
<
<
>
>

-- BrucLiong - 16 Feb 2006

 <<O>>  Difference Topic ShARPE (r1.2 - 16 Feb 2006 - BrucLiong)
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

Line: 8 to 8

ShARPE is also an extension of Shibboleth providing other functionalities that are not existence in current Shibboleth, such as:

  • ability to process group policy for users, i.e. Physics administrator may allow or disallow certain attributes to be released for all members in the Physics department
Changed:
<
<
  • ability to perform mapping of attributes from different schemas from simple mapping to complex one, i.e. IdP may define the attribute as mail but SP may understand it as email
>
>
  • ability to perform mapping of attributes from different schemas from simple mapping to complex one, i.e. IdP may define the attribute as mail but SP may understand it as email

  • visualization of user's attributes (what user has, what rules in ARP, what released), via WebSharpe

ShARPE is composed of 3 components, SharpeCore, WebSharpe, and Autograph.

Line: 31 to 31

ONE IMAGE on Autograph

Added:
>
>

References


-- BrucLiong - 16 Feb 2006
 <<O>>  Difference Topic ShARPE (r1.1 - 16 Feb 2006 - BrucLiong)
Line: 1 to 1
Added:
>
>
META TOPICPARENT WebHome

Shibbolet Attribute Release Policy Editor (ShARPE)

ShARPE is developed as part of the collaboration between MAMS and Shibboleth. ShARPE's aim is to manage the creation and maintenance of user's attributes as defined by Attribute Release Policy (ARP) mechanism of Shibboleth.

In particular, ShARPE allows admins and users to easily manage their release attribute policy in a way that conforms to their privacy and satisfaction of users in gaining the services that they want (on service provider end)

ShARPE is also an extension of Shibboleth providing other functionalities that are not existence in current Shibboleth, such as:

  • ability to process group policy for users, i.e. Physics administrator may allow or disallow certain attributes to be released for all members in the Physics department
  • ability to perform mapping of attributes from different schemas from simple mapping to complex one, i.e. IdP may define the attribute as mail but SP may understand it as email
  • visualization of user's attributes (what user has, what rules in ARP, what released), via WebSharpe

ShARPE is composed of 3 components, SharpeCore, WebSharpe, and Autograph.

WebSharpe is a web interface for Sharpe to allow user and admin to interact with ShARPE. ShARPE can be fully functional without WebSharpe, however its use as user interface to ShARPE is recommended.

WebSharpe allows user and admin to:

  • create/manipulate ARP to govern release of attributes from IdP to a particular service at SP
  • modify the release of a particular attribute
  • overrule the release of particular attribute when it was set by admin
  • visualize what attributes released and how the ARPs affect the attributes

Autograph is another web interface that interacts with SharpeCore to illustrate the usage of idCard. The idea is that user would have lots of idCard to be use when s/he visits a SP. User can specify at the IdP which idCard to use for certain SP. Each idCard would have certain details containing user's attributes specifically agreed by user to be released for the SP. For example, I am a professor at university A and also a member of IEEE. When I visit an online bookshop (SP), I may choose idCard with some attributes that reveal the fact I am working in university environment only, however when I go to university's affiliated sites, I may use another idCard that specifies my membership in IEEE.

SharpeCore is the core component of ShARPE. It sits ontop of current Shibboleth IdP and access/manipulate configuration files as used by the IdP. Introduction of SharpeCore would enable any IdP to benefit Sharpe's capabilities.

IMAGE HERE illustrating Sharpe - WebSharpe - SharpeCore - Autograph

ONE IMAGE on WebSharpe

ONE IMAGE on Autograph

-- BrucLiong - 16 Feb 2006

View topic | Diffs | r1.14 | > | r1.13 | > | r1.12 | More
Revision r1.1 - 16 Feb 2006 - 04:54 - BrucLiong
Revision r1.14 - 12 Oct 2007 - 05:05 - BrucLiong