delegate
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 61
DeleGate 9.9.3 / 9.9.4 Pre11
universal application level gateway, or proxy server which can relay most of fundamental application protocols used in the Internet more>> <<less
Added: 2009-07-21 License: Freely Distributable Price: FREE
13 downloads
DeleGate 9.5.6 / 9.6.3 Alpha
DeleGate is a multi-purpose application level gateway and proxy. more>>
DeleGate is a multi-purpose application level gateway, or a proxy server which runs on multiple platforms (Unix, Windows, MacOS X and OS/2). DeleGate mediates communication of various protocols (HTTP, FTP, NNTP, SMTP, POP, Telnet, SOCKS, etc.), applying cache and conversion for mediated data, controlling access from clients and routing toward servers.
DeleGate translates protocols between clients and servers, applying SSL(TLS) to arbitrary protocols, merging several servers into a single server view with aliasing and filtering.
Born as a tiny proxy for Gopher in March 1994, it has steadily grown into a general purpose proxy server. Besides beeing a proxy, DeleGate can be used as a simple origin server for some protocols (HTTP, FTP and NNTP).
Main features:
- UNBOUND PROXY: A user can select target servers arbitrarily in ad hoc way showing destination in user level data specific to the protocol of the client.
- BOUND PROXY: An administrator of DeleGate can specify which destination server is used depending on accessing client.
- CACHE: A message data transferred on a protocol is cached in its inherent format and shared among DeleGate as gateway servers of different protocols.
- CONNECTION SHARING: An established connection to a server in anonymous user can be reused and shared among multiple clients.
- DATA CONVERSION: DeleGate has several built-in data conversion filters which can be applied to a specific part of data in a message on each protocol.
- PROTOCOL CONVERSION: A client of a protocol can talk with servers of other protocols via DeleGate.
- AUTHENTICATION / SECURE PROTOCOL CONVERSION: DeleGate can relay between a non-SSL client and a SSL server, or between a SSL-client and a non-SSL server.
- ACCESS CONTROL: Accesses to be permitted to pass DeleGate are described by a set of triples of destination protocol, destination server and source client.
- LOGGING: Detailed logging of DeleGate actions and protocol dependent logging in standard formats.
- AUTOMATIC INVOCATION: DeleGate can be invoked automatically on demand or at the startup time of the host system.
- RESOLVER CONTROL: You can control the combination and sequence of multiple resolution mechanisms, independently of platforms.
- ROUTING CONTROL: A route toward the server can be selected from alternatives depending on protocol, server and client (host and user).
- MOUNTING SERVERS: Multiple target servers of multiple protocols can be merged into a single server of a protocol, with resource name filtering and aliasing.
- PROXY ON DEMAND: Automatically invoked proxy just for the current session.
- ORIGIN SERVER: You can use DeleGate as simple origin servers for several protocols.
- EXTENSION BY USERS: You can attach your own graphic images, messages, and programs to DeleGate without modifiying the DeleGate program.
- TCP WRAPPER: You can use DeleGate like inetd + TCPwrapper which make your own filter program work as a server with access control.
- SCHEDULER: You can use DeleGate like crond which invokes specified commands at specified timing.
- MULTI-PLATFORM: DeleGate runs on multiple platforms and can be compiled from a common source program without any platform dependent configuration.
Whats New in 9.6.3 Alpha Development Release:
- This release fixes frozen threads or broken data which could be caused with thread based implementations of SSL and gzip filters.
<<lessDeleGate translates protocols between clients and servers, applying SSL(TLS) to arbitrary protocols, merging several servers into a single server view with aliasing and filtering.
Born as a tiny proxy for Gopher in March 1994, it has steadily grown into a general purpose proxy server. Besides beeing a proxy, DeleGate can be used as a simple origin server for some protocols (HTTP, FTP and NNTP).
Main features:
- UNBOUND PROXY: A user can select target servers arbitrarily in ad hoc way showing destination in user level data specific to the protocol of the client.
- BOUND PROXY: An administrator of DeleGate can specify which destination server is used depending on accessing client.
- CACHE: A message data transferred on a protocol is cached in its inherent format and shared among DeleGate as gateway servers of different protocols.
- CONNECTION SHARING: An established connection to a server in anonymous user can be reused and shared among multiple clients.
- DATA CONVERSION: DeleGate has several built-in data conversion filters which can be applied to a specific part of data in a message on each protocol.
- PROTOCOL CONVERSION: A client of a protocol can talk with servers of other protocols via DeleGate.
- AUTHENTICATION / SECURE PROTOCOL CONVERSION: DeleGate can relay between a non-SSL client and a SSL server, or between a SSL-client and a non-SSL server.
- ACCESS CONTROL: Accesses to be permitted to pass DeleGate are described by a set of triples of destination protocol, destination server and source client.
- LOGGING: Detailed logging of DeleGate actions and protocol dependent logging in standard formats.
- AUTOMATIC INVOCATION: DeleGate can be invoked automatically on demand or at the startup time of the host system.
- RESOLVER CONTROL: You can control the combination and sequence of multiple resolution mechanisms, independently of platforms.
- ROUTING CONTROL: A route toward the server can be selected from alternatives depending on protocol, server and client (host and user).
- MOUNTING SERVERS: Multiple target servers of multiple protocols can be merged into a single server of a protocol, with resource name filtering and aliasing.
- PROXY ON DEMAND: Automatically invoked proxy just for the current session.
- ORIGIN SERVER: You can use DeleGate as simple origin servers for several protocols.
- EXTENSION BY USERS: You can attach your own graphic images, messages, and programs to DeleGate without modifiying the DeleGate program.
- TCP WRAPPER: You can use DeleGate like inetd + TCPwrapper which make your own filter program work as a server with access control.
- SCHEDULER: You can use DeleGate like crond which invokes specified commands at specified timing.
- MULTI-PLATFORM: DeleGate runs on multiple platforms and can be compiled from a common source program without any platform dependent configuration.
Whats New in 9.6.3 Alpha Development Release:
- This release fixes frozen threads or broken data which could be caused with thread based implementations of SSL and gzip filters.
Download (1.5MB)
Added: 2007-08-10 License: Freely Distributable Price:
812 downloads
JGame 3.0
JGame is a small high-level 2D game engine for producing games on Java platforms. more>>
JGame is a small high-level 2D game engine for producing games on Java platforms. It does a lot of the stuff you need for a game automatically, and "classic" type arcade games can be developed with a minimum of effort.
It is based on sprites with automatic collision detection, and a tile-based background with easy sprite-tile interaction facilities. JGame games can easily be run as stand-alone applications or as applets, and can be scaled to any resolution.
Main features:
- Tested on various platforms; can easily be run as applet as well.
- Ensures optimised and accelerated graphics for a variety of displays; even works well on remote X11 displays.
- The game is programmed at one resolution, but can be scaled to any desired resolution when run.
- Built-in animated "sprite" engine, with easy animation definition.
- Tile-based background handling, with decorative backdrop.
- Automatic collision detection with sprites and background tiles, and easy background tile interaction.
- Load sprites, tiles, and colour fonts directly from sprite sheets.
- Define images and animations in a text file.
Enhancements:
- New platform-independent versions of Point, Rectangle, Color, Font.
- Changes in package structure. Base classes are now in jgame, platform independent implementation details in jgame.impl, platform dependent classes in jgame.platform.
- Major changes in JGEngine/JGCanvas. A platform independent interface JGEngineInterface has been defined. The platform-independent code has been moved to jgame.impl.*, and for each platform there is a platform-dependent version of JGEngine, delegating functionality to jgame.impl.EngineLogic where possible.
- ImageUtil has been split into a platform-independent interface JGImage, and platform implementations JREImage and MIDPImage.
- StdGame now has two versions, the original for JRE and a somewhat simplified version for MIDP.
- The package tree has been changed. The sources are now in src-*, classes are compiled into classes-*. Compilation of the JGame classes and the examples and applications has been split.
- The code has been optimised: object creations in the most important tight loops have been reduced to near zero, repaintBG has been optimised by a factor 2, isOnPF/isInView were optimised.
- a small bug in background copying where the area bounds would exceed the size of the source image was fixed.
- A few methods were added specifically for use the Midlet platform, such as isMidlet(), displayWidth/Height(), setScalingPreferences().
- setCursor has been renamed to SetMouseCursor.
- there is a new engine getTiles method that copies the data into an existing object. Semantics of the getTiles methods in JGObject have been changed to return a local variable with the information copied into it, rather than create an object every time. Semantics of some other methods such as getImage is changed so as not to create a new object every time.
- fixed bug in exitEngine which did not set the JGObject default_engine to null
- fixed access exception occurring in unsigned webstart.
- improved frame skip logic so that game runs smoothly even if the machine is way too slow
<<lessIt is based on sprites with automatic collision detection, and a tile-based background with easy sprite-tile interaction facilities. JGame games can easily be run as stand-alone applications or as applets, and can be scaled to any resolution.
Main features:
- Tested on various platforms; can easily be run as applet as well.
- Ensures optimised and accelerated graphics for a variety of displays; even works well on remote X11 displays.
- The game is programmed at one resolution, but can be scaled to any desired resolution when run.
- Built-in animated "sprite" engine, with easy animation definition.
- Tile-based background handling, with decorative backdrop.
- Automatic collision detection with sprites and background tiles, and easy background tile interaction.
- Load sprites, tiles, and colour fonts directly from sprite sheets.
- Define images and animations in a text file.
Enhancements:
- New platform-independent versions of Point, Rectangle, Color, Font.
- Changes in package structure. Base classes are now in jgame, platform independent implementation details in jgame.impl, platform dependent classes in jgame.platform.
- Major changes in JGEngine/JGCanvas. A platform independent interface JGEngineInterface has been defined. The platform-independent code has been moved to jgame.impl.*, and for each platform there is a platform-dependent version of JGEngine, delegating functionality to jgame.impl.EngineLogic where possible.
- ImageUtil has been split into a platform-independent interface JGImage, and platform implementations JREImage and MIDPImage.
- StdGame now has two versions, the original for JRE and a somewhat simplified version for MIDP.
- The package tree has been changed. The sources are now in src-*, classes are compiled into classes-*. Compilation of the JGame classes and the examples and applications has been split.
- The code has been optimised: object creations in the most important tight loops have been reduced to near zero, repaintBG has been optimised by a factor 2, isOnPF/isInView were optimised.
- a small bug in background copying where the area bounds would exceed the size of the source image was fixed.
- A few methods were added specifically for use the Midlet platform, such as isMidlet(), displayWidth/Height(), setScalingPreferences().
- setCursor has been renamed to SetMouseCursor.
- there is a new engine getTiles method that copies the data into an existing object. Semantics of the getTiles methods in JGObject have been changed to return a local variable with the information copied into it, rather than create an object every time. Semantics of some other methods such as getImage is changed so as not to create a new object every time.
- fixed bug in exitEngine which did not set the JGObject default_engine to null
- fixed access exception occurring in unsigned webstart.
- improved frame skip logic so that game runs smoothly even if the machine is way too slow
Download (5.3MB)
Added: 2007-08-09 License: BSD License Price:
494 downloads
beware 0.1
beware project is a distributed global server load balancing system. more>>
beware project is a distributed global server load balancing system.
beware is a small DNS server that can have nameserver responsibility delegated to it and that can return a set of authoritative "IN A" records to a client.
Given a list of hosts for a certain domain name, it also tests for services specified and will only return IP addresses for currently reachable services.
<<lessbeware is a small DNS server that can have nameserver responsibility delegated to it and that can return a set of authoritative "IN A" records to a client.
Given a list of hosts for a certain domain name, it also tests for services specified and will only return IP addresses for currently reachable services.
Download (0.12MB)
Added: 2007-04-14 License: GPL (GNU General Public License) Price:
923 downloads
fuselagefs 0.0.1
fuselagefs is a project which consists of a C++ wrapper class for FUSE called Fuselagefs. more>>
fuselagefs is a project which consists of a C++ wrapper class for FUSE called Fuselagefs.
fuselagefs consists of a C++ wrapper class for FUSE called Fuselagefs, as well as Delegatefs which is a Fuselagefs subclass that delegates all operations to an underlying base filesystem.
With Delegatefs you can expose dir1 at mountpoint dir2 very easily as a FUSE filesystem. Subclasses of Delegatefs can then be created which add a little extra functionality to the delegation operation but rely on the parent class to perform the work and return errors to FUSE in an appropriate manner. An example subclass is petardfs.
<<lessfuselagefs consists of a C++ wrapper class for FUSE called Fuselagefs, as well as Delegatefs which is a Fuselagefs subclass that delegates all operations to an underlying base filesystem.
With Delegatefs you can expose dir1 at mountpoint dir2 very easily as a FUSE filesystem. Subclasses of Delegatefs can then be created which add a little extra functionality to the delegation operation but rely on the parent class to perform the work and return errors to FUSE in an appropriate manner. An example subclass is petardfs.
Download (0.27MB)
Added: 2007-04-03 License: GPL (GNU General Public License) Price:
934 downloads
Gentle.NET 1.2.9
Gentle.NET is an object persistence framework for .NET written in C#. more>>
Gentle.NET is an RDBMS independent object persistence framework. Gentle.NET features automatic SQL generation and object construction, an SQL factory for creating custom queries, DataView construction helpers, excellent performance and reasonably complete docs.
The framework defines a few attributes with which you have to decorate the objects you wish to persist. Decorate classes with the TableName attribute, and members (properties and fields as you see fit) with the TableColumn attribute.
There are additional attributes available which need only be used when no Analyzer class exists for the database you are using (see Database Provider - Implementation Status). The Analyzer classes are used to obtain metadata on the current schema directly from the database, thus bypassing the need for replicating this information in your code.
If no Analyzer exists, primary key columns must be decorated with the PrimaryKey attribute, and foreign keys and their mappings must be declared using the ForeignKey attribute. The TableColumn attribute provides properties allowing you to provide details on type, size and null-handling. If an Analyzer does exist, the information obtained automatically overrides any such setting.
Business objects may optionally inherit from the Persistent class, which provides a set of standard methods for persisting and retrieving objects. You can replicate these on a different base class if needed, or on a manager class if you prefer a more SOA-oriented design. Gentle provides support for identity columns (where the database assigns a primary key value to the row being inserted) to implementors of IPersistent (which includes the Persistent class).
The main access point into the framework functionality is provided by the PersistenceBroker class, which is responsible for orchestrating all access to a given database provider.
The PersistenceBroker is responsible for basic query construction and caching, as well as interaction with the database backends. You can create as many PersistenceBroker instances as needed, such as one for every database to which you need to connect. Various classes permit or require you to pass a PersistenceBroker instance, which will be used subsequently for all database operations performed by the class.
If you need to connect to a single database only, you can use the static Broker class, which delegates all calls to a default PersistenceBroker instance (using the DefaultProvider configured in the configuration file).
Persistent objects are identified by a Key, which is really just a Hashtable with some convenient methods for gathering property values from objects. The Key class knows how to populate itself when given an object instance and a set of property names, and also provides a means of obtaining a key holding just the primary key fields.
This is useful when constructing custom queries as constraints can be passed as Key instances to methods on both the (Persistence)Broker and SqlBuilder classes. This encapsulation also enables Gentle to work with multi-column primary keys.
To execute custom SQL statements use the SqlStatement class. Use the SqlBuilder class to construct instances of this class whenever the statement is for a supported type (i.e. a class decorated with the proper attributes as outlined above).
The SqlBuilder provides a database independent way of constructing queries and has many methods for adding constraints and otherwise customizing the query. It is used internally by the PersistenceBroker whenever it needs to generate statements.
You can declare a DataView layout using the CustomView attribute on the properties to include in the DataView. The actual DataView can be obtained using the ObjectView class by supplying an array of business objects.
Multiple statements can be transacted (grouped) using the Transaction class.
Enhancements:
- This release features a complete rewrite of the cache subsystem, with significant performance improvements as a result.
- There have also been several minor improvements and bugfixes throughout the code base.
<<lessThe framework defines a few attributes with which you have to decorate the objects you wish to persist. Decorate classes with the TableName attribute, and members (properties and fields as you see fit) with the TableColumn attribute.
There are additional attributes available which need only be used when no Analyzer class exists for the database you are using (see Database Provider - Implementation Status). The Analyzer classes are used to obtain metadata on the current schema directly from the database, thus bypassing the need for replicating this information in your code.
If no Analyzer exists, primary key columns must be decorated with the PrimaryKey attribute, and foreign keys and their mappings must be declared using the ForeignKey attribute. The TableColumn attribute provides properties allowing you to provide details on type, size and null-handling. If an Analyzer does exist, the information obtained automatically overrides any such setting.
Business objects may optionally inherit from the Persistent class, which provides a set of standard methods for persisting and retrieving objects. You can replicate these on a different base class if needed, or on a manager class if you prefer a more SOA-oriented design. Gentle provides support for identity columns (where the database assigns a primary key value to the row being inserted) to implementors of IPersistent (which includes the Persistent class).
The main access point into the framework functionality is provided by the PersistenceBroker class, which is responsible for orchestrating all access to a given database provider.
The PersistenceBroker is responsible for basic query construction and caching, as well as interaction with the database backends. You can create as many PersistenceBroker instances as needed, such as one for every database to which you need to connect. Various classes permit or require you to pass a PersistenceBroker instance, which will be used subsequently for all database operations performed by the class.
If you need to connect to a single database only, you can use the static Broker class, which delegates all calls to a default PersistenceBroker instance (using the DefaultProvider configured in the configuration file).
Persistent objects are identified by a Key, which is really just a Hashtable with some convenient methods for gathering property values from objects. The Key class knows how to populate itself when given an object instance and a set of property names, and also provides a means of obtaining a key holding just the primary key fields.
This is useful when constructing custom queries as constraints can be passed as Key instances to methods on both the (Persistence)Broker and SqlBuilder classes. This encapsulation also enables Gentle to work with multi-column primary keys.
To execute custom SQL statements use the SqlStatement class. Use the SqlBuilder class to construct instances of this class whenever the statement is for a supported type (i.e. a class decorated with the proper attributes as outlined above).
The SqlBuilder provides a database independent way of constructing queries and has many methods for adding constraints and otherwise customizing the query. It is used internally by the PersistenceBroker whenever it needs to generate statements.
You can declare a DataView layout using the CustomView attribute on the properties to include in the DataView. The actual DataView can be obtained using the ObjectView class by supplying an array of business objects.
Multiple statements can be transacted (grouped) using the Transaction class.
Enhancements:
- This release features a complete rewrite of the cache subsystem, with significant performance improvements as a result.
- There have also been several minor improvements and bugfixes throughout the code base.
Download (7.0MB)
Added: 2006-06-04 License: LGPL (GNU Lesser General Public License) Price:
1240 downloads
Devel::GDB::Reflect 0.2
Devel::GDB::Reflect is a reflection API for GDB/C++. more>>
Devel::GDB::Reflect is a reflection API for GDB/C++.
SYNOPSIS
use Devel::GDB;
use Devel::GDB::Reflect;
my $gdb = new Devel::GDB( -file => $foo );
my $reflector = new Devel::GDB::Reflect( $gdb );
print $gdb->get( "b foo.c:123" );
$gdb->print( "myVariable" );
Devel::GDB::Reflect provides a reflection API for GDB/C++, which can be used to recursively print the contents of STL data structures (vector, set, map, etc.) within a GDB session. It is not limited to STL, however; you can write your own delegates for printing custom container types.
The module implements the functionality used by the gdb++ script, which serves as a wrapper around GDB. You should probably familiarize yourself with the basic functionality of this script first, before diving into the gory details presented here.
Global Variables
The following global variables control the behavior of the "print" method.
$Devel::GDB::Reflect::INDENT
The number of spaces to indent at each level of recursion. Defaults to 4.
$Devel::GDB::Reflect::MAX_DEPTH
The maximum recursion depth. Defaults to 5.
$Devel::GDB::Reflect::MAX_WIDTH
The maximum number of elements to show from a given container. Defaults to 10.
<<lessSYNOPSIS
use Devel::GDB;
use Devel::GDB::Reflect;
my $gdb = new Devel::GDB( -file => $foo );
my $reflector = new Devel::GDB::Reflect( $gdb );
print $gdb->get( "b foo.c:123" );
$gdb->print( "myVariable" );
Devel::GDB::Reflect provides a reflection API for GDB/C++, which can be used to recursively print the contents of STL data structures (vector, set, map, etc.) within a GDB session. It is not limited to STL, however; you can write your own delegates for printing custom container types.
The module implements the functionality used by the gdb++ script, which serves as a wrapper around GDB. You should probably familiarize yourself with the basic functionality of this script first, before diving into the gory details presented here.
Global Variables
The following global variables control the behavior of the "print" method.
$Devel::GDB::Reflect::INDENT
The number of spaces to indent at each level of recursion. Defaults to 4.
$Devel::GDB::Reflect::MAX_DEPTH
The maximum recursion depth. Defaults to 5.
$Devel::GDB::Reflect::MAX_WIDTH
The maximum number of elements to show from a given container. Defaults to 10.
Download (0.015MB)
Added: 2007-05-08 License: Perl Artistic License Price:
899 downloads
KeyNote 2.3
KeyNote is a simple and flexible trust-management system designed to work well for applications. more>>
KeyNote is a simple and flexible trust-management system designed to work well for applications.
Trust management, introduced in the PolicyMaker system [BFL96], is a unified approach to specifying and interpreting security policies, credentials, and relationships; it allows direct authorization of security-critical actions. A trust-management system provides standard, general-purpose mechanisms for specifying application security policies and credentials. Trust-management credentials describe a specific delegation of trust and subsume the role of public key certificates; unlike traditional certificates, which bind keys to names, credentials can bind keys directly to the authorization to perform specific tasks.
A language for describing `actions, which are operations with security consequences that are to be controlled by the system.
A mechanism for identifying `principals, which are entities that can be authorized to perform actions.
A language for specifying application `policies, which govern the actions that principals are authorized to perform.
A language for specifying `credentials, which allow principals to delegate authorization to other principals.
A `compliance checker, which provides a service to applications for determining how an action requested by principals should be handled, given a policy and a set of credentials.
The trust-management approach has a number of advantages over other mechanisms for specifying and controlling authorization, especially when security policy is distributed over a network or is otherwise decentralized.
Trust management unifies the notions of security policy, credentials, access control, and authorization. An application that uses a trust- management system can simply ask the compliance checker whether a requested action should be allowed. Furthermore, policies and credentials are written in standard languages that are shared by all trust-managed applications; the security configuration mechanism for one application carries exactly the same syntactic and semantic structure as that of another, even when the semantics of the applications themselves are quite different.
Trust-management policies are easy to distribute across networks, helping to avoid the need for application-specific distributed policy configuration mechanisms, access control lists, and certificate parsers and interpreters.
For a general discussion of the use of trust management in distributed system security, see [Bla99].
KeyNote is a simple and flexible trust-management system designed to work well for a variety of large- and small- scale Internet-based applications. It provides a single, unified language for both local policies and credentials. KeyNote policies and credentials, called `assertions, contain predicates that describe the trusted actions permitted by the holders of specific public keys. KeyNote assertions are essentially small, highly-structured programs. A signed assertion, which can be sent over an untrusted network, is also called a `credential assertion. Credential assertions, which also serve the role of certificates, have the same syntax as policy assertions but are also signed by the principal delegating the trust.
In KeyNote:
Actions are specified as a collection of name-value pairs.
Principal names can be any convenient string and can directly represent cryptographic public keys.
The same language is used for both policies and credentials.
The policy and credential language is concise, highly expressive, human readable and writable, and compatible with a variety of storage and transmission media, including electronic mail.
The compliance checker returns an application-configured `policy compliance value that describes how a request should be handled by the application. Policy compliance values are always positively derived from policy and credentials, facilitating analysis of KeyNote-based systems.
Compliance checking is efficient enough for high-performance and real-time applications.
This document describes the KeyNote policy and credential assertion language, the structure of KeyNote action descriptions, and the KeyNote model of computation.
<<lessTrust management, introduced in the PolicyMaker system [BFL96], is a unified approach to specifying and interpreting security policies, credentials, and relationships; it allows direct authorization of security-critical actions. A trust-management system provides standard, general-purpose mechanisms for specifying application security policies and credentials. Trust-management credentials describe a specific delegation of trust and subsume the role of public key certificates; unlike traditional certificates, which bind keys to names, credentials can bind keys directly to the authorization to perform specific tasks.
A language for describing `actions, which are operations with security consequences that are to be controlled by the system.
A mechanism for identifying `principals, which are entities that can be authorized to perform actions.
A language for specifying application `policies, which govern the actions that principals are authorized to perform.
A language for specifying `credentials, which allow principals to delegate authorization to other principals.
A `compliance checker, which provides a service to applications for determining how an action requested by principals should be handled, given a policy and a set of credentials.
The trust-management approach has a number of advantages over other mechanisms for specifying and controlling authorization, especially when security policy is distributed over a network or is otherwise decentralized.
Trust management unifies the notions of security policy, credentials, access control, and authorization. An application that uses a trust- management system can simply ask the compliance checker whether a requested action should be allowed. Furthermore, policies and credentials are written in standard languages that are shared by all trust-managed applications; the security configuration mechanism for one application carries exactly the same syntactic and semantic structure as that of another, even when the semantics of the applications themselves are quite different.
Trust-management policies are easy to distribute across networks, helping to avoid the need for application-specific distributed policy configuration mechanisms, access control lists, and certificate parsers and interpreters.
For a general discussion of the use of trust management in distributed system security, see [Bla99].
KeyNote is a simple and flexible trust-management system designed to work well for a variety of large- and small- scale Internet-based applications. It provides a single, unified language for both local policies and credentials. KeyNote policies and credentials, called `assertions, contain predicates that describe the trusted actions permitted by the holders of specific public keys. KeyNote assertions are essentially small, highly-structured programs. A signed assertion, which can be sent over an untrusted network, is also called a `credential assertion. Credential assertions, which also serve the role of certificates, have the same syntax as policy assertions but are also signed by the principal delegating the trust.
In KeyNote:
Actions are specified as a collection of name-value pairs.
Principal names can be any convenient string and can directly represent cryptographic public keys.
The same language is used for both policies and credentials.
The policy and credential language is concise, highly expressive, human readable and writable, and compatible with a variety of storage and transmission media, including electronic mail.
The compliance checker returns an application-configured `policy compliance value that describes how a request should be handled by the application. Policy compliance values are always positively derived from policy and credentials, facilitating analysis of KeyNote-based systems.
Compliance checking is efficient enough for high-performance and real-time applications.
This document describes the KeyNote policy and credential assertion language, the structure of KeyNote action descriptions, and the KeyNote model of computation.
Download (0.13MB)
Added: 2006-07-14 License: (FDL) GNU Free Documentation License Price:
1253 downloads
demexp 0.8.0
demexp is a client/server system for direct democracies. more>>
demexp is a client/server system for direct democracies. demexp makes it possible to ask questions in the system, add new answers to those questions, and vote on proposed answers.
The voting procedure used is Condorcet voting. Questions are classified, and a delegation system allows ones vote for certain questions to be assigned to a chosen delegate.
The software is tailored to the needs of the Democratic Experience project.
Enhancements:
- A new configuration file that supports version upgrading.
- Support for client internationalization. Translations of the (English) client into French and Esperanto.
- An experimental Web client in OCaml (using WDialog). Improvement of the Windows installer.
- Simplification of the clients interface.
- Tooltips on column titles.
- Various bugfixes in the client and the server.
<<lessThe voting procedure used is Condorcet voting. Questions are classified, and a delegation system allows ones vote for certain questions to be assigned to a chosen delegate.
The software is tailored to the needs of the Democratic Experience project.
Enhancements:
- A new configuration file that supports version upgrading.
- Support for client internationalization. Translations of the (English) client into French and Esperanto.
- An experimental Web client in OCaml (using WDialog). Improvement of the Windows installer.
- Simplification of the clients interface.
- Tooltips on column titles.
- Various bugfixes in the client and the server.
Download (0.17MB)
Added: 2006-10-10 License: GPL (GNU General Public License) Price:
1109 downloads
Template::Alloy::Parse 1.006
Template::Alloy::Parse is a Perl module with common parsing role for creating AST from templates. more>>
Template::Alloy::Parse is a Perl module with common parsing role for creating AST from templates.
The Template::Alloy::Parse role is reponsible for storing the majority of directive parsing code, as well as for delegating to the TT, HTE, Tmpl, and Velocity roles for finding variables and directives.
ROLE METHODS
parse_tree
Used by load_tree. This is the main grammar engine of the program. It delegates to the syntax found in $self->{SYNTAX} (defaults to alloy) and calls the function found in the $SYNTAX hashref. The majority of these syntaxes use methods found in the $DIRECTIVES hashref to parse different DIRECTIVE types for each particular syntax.
A template that looked like the following:
Foo
[%- GET foo -%]
[%- GET bar -%]
Bar
would parse to the following AST:
[
Foo,
[GET, 6, 15, [foo, 0]],
[GET, 22, 31, [bar, 0]],
Bar,
]
The "GET" words represent the directive used. The 6, 15 represent the beginning and ending characters of the directive in the document. The remaining items are the variables necessary for running the particular directive.
parse_expr
Used to parse a variable, an expression, a literal string, or a number. It returns a parsed variable tree. Samples of parsed variables can be found in the VARIABLE PARSE TREE section.
my $str = "1 + 2 * 3";
my $ast = $self->parse_expr($str);
# $ast looks like [[undef, +, 1, [[undef, *, 2, 3], 0]], 0]
parse_args
Allow for the multitudinous ways that TT parses arguments. This allows for positional as well as named arguments. Named arguments can be separated with a "=" or "=>", and positional arguments should be separated by " " or ",". This only returns an array of parsed variables. To get the actual values, you must call play_expr on each value.
dump_parse_tree
This method allows for returning a string of perl code representing the AST of the parsed tree.
It is mainly used for testing.
dump_parse_expr
This method allows for returning a Data::Dumper dump of a parsed variable. It is mainly used for testing.
parse_*
Methods by these names are used by parse_tree to parse the template. These are the grammar. They are used by all of the various template syntaxes Unless otherwise mentioned, these methods are not exposed via the role.
<<lessThe Template::Alloy::Parse role is reponsible for storing the majority of directive parsing code, as well as for delegating to the TT, HTE, Tmpl, and Velocity roles for finding variables and directives.
ROLE METHODS
parse_tree
Used by load_tree. This is the main grammar engine of the program. It delegates to the syntax found in $self->{SYNTAX} (defaults to alloy) and calls the function found in the $SYNTAX hashref. The majority of these syntaxes use methods found in the $DIRECTIVES hashref to parse different DIRECTIVE types for each particular syntax.
A template that looked like the following:
Foo
[%- GET foo -%]
[%- GET bar -%]
Bar
would parse to the following AST:
[
Foo,
[GET, 6, 15, [foo, 0]],
[GET, 22, 31, [bar, 0]],
Bar,
]
The "GET" words represent the directive used. The 6, 15 represent the beginning and ending characters of the directive in the document. The remaining items are the variables necessary for running the particular directive.
parse_expr
Used to parse a variable, an expression, a literal string, or a number. It returns a parsed variable tree. Samples of parsed variables can be found in the VARIABLE PARSE TREE section.
my $str = "1 + 2 * 3";
my $ast = $self->parse_expr($str);
# $ast looks like [[undef, +, 1, [[undef, *, 2, 3], 0]], 0]
parse_args
Allow for the multitudinous ways that TT parses arguments. This allows for positional as well as named arguments. Named arguments can be separated with a "=" or "=>", and positional arguments should be separated by " " or ",". This only returns an array of parsed variables. To get the actual values, you must call play_expr on each value.
dump_parse_tree
This method allows for returning a string of perl code representing the AST of the parsed tree.
It is mainly used for testing.
dump_parse_expr
This method allows for returning a Data::Dumper dump of a parsed variable. It is mainly used for testing.
parse_*
Methods by these names are used by parse_tree to parse the template. These are the grammar. They are used by all of the various template syntaxes Unless otherwise mentioned, these methods are not exposed via the role.
Download (0.14MB)
Added: 2007-07-14 License: Perl Artistic License Price:
832 downloads
mod_auth_user_dir 1.0
mod_auth_user_dir is a module for Apache 2, you can create private user folders using WebDAV protocol. more>>
mod_auth_user_dir is a module for Apache 2, you can create private user folders using WebDAV protocol. Users have only permissions to access to their own directory. Without this module, a htaccess file must be created inside every user folder. This is completely unmanageable when the number of users is big.
We can build a file server accessible from Windows and Linux using WebDAV and a web server like Apache. Because the protocol is build upon HTTP, the server uses ports TCP 80 (HTTP) and TCP 443 (HTTPS). These ports are commonly open in firewalls without any other special requirement.
User authentication (login and password) are delegated to other Apache modules like mod_auth_ldap.
Installation:
download the binary or compile the source. It should work with all Apache 2.x versions.
install the module with /usr/local/apache2/bin/apxs -i -a -n auth_user_dir libmod_auth_user_dir.la
configure directory options in httpd.conf. Option AUTHUSERDIRROOT can be defined for every Directory, and it is the root folder where user folders will be created.
restart Apache: apachectl restart
<<lessWe can build a file server accessible from Windows and Linux using WebDAV and a web server like Apache. Because the protocol is build upon HTTP, the server uses ports TCP 80 (HTTP) and TCP 443 (HTTPS). These ports are commonly open in firewalls without any other special requirement.
User authentication (login and password) are delegated to other Apache modules like mod_auth_ldap.
Installation:
download the binary or compile the source. It should work with all Apache 2.x versions.
install the module with /usr/local/apache2/bin/apxs -i -a -n auth_user_dir libmod_auth_user_dir.la
configure directory options in httpd.conf. Option AUTHUSERDIRROOT can be defined for every Directory, and it is the root folder where user folders will be created.
restart Apache: apachectl restart
Download (0.009MB)
Added: 2006-05-24 License: GPL (GNU General Public License) Price:
1248 downloads
SleekOffice 1.1
SleekOffice is a web-based application that allows individuals and workgroups to increase their productivity. more>>
SleekOffice project is a web-based application that allows individuals and workgroups to increase their productivity.
Manage your contacts, calendar items, files, projects and more from one interface! Get more done in less time!
Share and Synchronize Data
SleekOffice features sharing capabilities, allowing you to share information and delegate tasks among team members. Share contacts, calendars, notes and files easily. Additionally, use our sync tool to synchronize your data with Palm Desktop or Microsoft Outlook for mobile productivity!
Enhancements:
- Minor changes have been made to the installation wizard.
- The EULA was updated.
<<lessManage your contacts, calendar items, files, projects and more from one interface! Get more done in less time!
Share and Synchronize Data
SleekOffice features sharing capabilities, allowing you to share information and delegate tasks among team members. Share contacts, calendars, notes and files easily. Additionally, use our sync tool to synchronize your data with Palm Desktop or Microsoft Outlook for mobile productivity!
Enhancements:
- Minor changes have been made to the installation wizard.
- The EULA was updated.
Download (9.9MB)
Added: 2007-01-27 License: Freeware Price:
1002 downloads
RIR to DNS converter 0.1
RIR to DNS converter is a tool to convert Regional Internet Registry data to a DNS country lookup zone. more>>
RIR to DNS converter is a tool to convert Regional Internet Registry data to a DNS country lookup zone. You can use it to build your own DNS zone for looking up country codes from IP addresses.
It uses data directly from RIPE, ARIN, APNIC, LACNIC, and AFRINIC. The data can be updated on a schedule of your choosing.
The input data comes from:
ftp://ftp.afrinic.net/pub/stats/afrinic/delegated-afrinic-latest
ftp://ftp.apnic.net/pub/stats/apnic/delegated-apnic-latest
ftp://ftp.arin.net/pub/stats/arin/delegated-arin-latest
ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest
ftp://ftp.lacnic.net/pub/stats/lacnic/delegated-lacnic-latest
The input data format is described in:
http://www.apnic.net/db/rir-stats-format.html
The output is a BIND 9 zone file that can be used to look up country codes
in a similar fashion to in-addr.arpa. For example, to find out what country
203.30.47.58 is:
host 58.47.30.203.rir.example.com
58.47.30.203.rir.example.com has address 127.0.65.86
where 65 and 85 are ASCII for A and U, which means 203.30.47.58 is
in Australia (AU).
HOW TO USE IT
Just feed it the above delegated- -latest files into stdin and it will
spit out the zone file to stdout. The zone file will only have the IP addresses,
so you could $INCLUDE it into a zone file that contains NS records, SOA, $ORIGIN,
etc.
WHY USE IT
You dont need the resolution of MaxMinds GeoIP database, but you do want
something that is free and you want it kept up to date on a schedule that
you decide.
You could use this to block or tag email based on countries, block or redirect
visitors to your website based on end-user country, and so on. Be very
careful about blocking mail this way, though, as you may block legitimate
email. Instead of blocking outright, use it in a SpamAssassin rule to add
something to the spam level, based on where the email comes from.
HOW IT WORKS
The RIR files contain ranges of IP addresses, and indicate what CC each range is allocated to. At the simplest level, rir2dns just sorts the ranges then iterates
through the IPs in each range and generates a reverse-dns-style A record that
represents the country code.
HOW IT WORKS - IN DETAIL
Rather than iterate through each IP address, the program tries to skip through
entire classes at a time (256 IPs, 65536 IPs, etc). Rather than iterate
through each IP, the loop iterates through classes or IP ranges (whichever are
smaller at the loop control), using control-breaks to accummulate neighbouring
ranges where possible so that entire classes that are in the same country dont
generate huge numbers of records.
Firstly, IPs are considered to be 4-digit numbers, but in base-256. In other
words, each octet is dealt with as if it were a single base-256 digit. This
turns out to be convenient because optimisations of large chunks of IP space can be done by looking for places where least-significant base-256 digits are zero.
Next, IP ranges are broken down into the following sub-ranges:
Optional individual IP addresses (ie: 4 octets)
Optional A-class ranges (ie: 3 octets)
Optional B-class ranges (ie: 2 octets)
Optional C-class ranges (ie: 1 octet)
Optional B-class ranges (ie: 2 octets)
Optional A-class ranges (ie: 3 octets)
Optional individual IP addresses (ie: 4 octets)
Considering that there is a pattern here, Im sure theres an elegant way to
handle breaking this down into two loops (one reducing the octets and one
increasing the octets), but I cant be bothered, so Ill break it down into
seven loops. Kind of hard-coded, but at least its simple.
For ease of processing, the IP addresses are actually converted to 32-bit numbers, then back again. This simplifies mathematics and looping through ranges.
Thats pretty much it, really...
Note that currently there are about 80,000 RIR records between all five
registries. This takes about 35 seconds on a 2.4GHz P4 to process, and
generates a 26MB file with around 3/4 million lines (RRs). This causes BIND
to use about 100MB or so of memory, and on a slow machine will probably cause it to take too long to reply, while it searches the zone. That size zone can
take a minute or two to load, which is quite a while.
Basic algorithm:
Read & process RIR data:
Read RIR ranges
Sort RIR ranges by start IP address
Glue together contiguous ranges of the same country
For each range
Generate the IPs at the start of the range
Generate the A-classes at the start of the range
Generate the B-classes at the start of the range
Generate the C-classes in the middle of the range
Generate the B-classes at the end of the range
Generate the A-classes at the end of the range
Generate the IPs at the end of the range
<<lessIt uses data directly from RIPE, ARIN, APNIC, LACNIC, and AFRINIC. The data can be updated on a schedule of your choosing.
The input data comes from:
ftp://ftp.afrinic.net/pub/stats/afrinic/delegated-afrinic-latest
ftp://ftp.apnic.net/pub/stats/apnic/delegated-apnic-latest
ftp://ftp.arin.net/pub/stats/arin/delegated-arin-latest
ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest
ftp://ftp.lacnic.net/pub/stats/lacnic/delegated-lacnic-latest
The input data format is described in:
http://www.apnic.net/db/rir-stats-format.html
The output is a BIND 9 zone file that can be used to look up country codes
in a similar fashion to in-addr.arpa. For example, to find out what country
203.30.47.58 is:
host 58.47.30.203.rir.example.com
58.47.30.203.rir.example.com has address 127.0.65.86
where 65 and 85 are ASCII for A and U, which means 203.30.47.58 is
in Australia (AU).
HOW TO USE IT
Just feed it the above delegated- -latest files into stdin and it will
spit out the zone file to stdout. The zone file will only have the IP addresses,
so you could $INCLUDE it into a zone file that contains NS records, SOA, $ORIGIN,
etc.
WHY USE IT
You dont need the resolution of MaxMinds GeoIP database, but you do want
something that is free and you want it kept up to date on a schedule that
you decide.
You could use this to block or tag email based on countries, block or redirect
visitors to your website based on end-user country, and so on. Be very
careful about blocking mail this way, though, as you may block legitimate
email. Instead of blocking outright, use it in a SpamAssassin rule to add
something to the spam level, based on where the email comes from.
HOW IT WORKS
The RIR files contain ranges of IP addresses, and indicate what CC each range is allocated to. At the simplest level, rir2dns just sorts the ranges then iterates
through the IPs in each range and generates a reverse-dns-style A record that
represents the country code.
HOW IT WORKS - IN DETAIL
Rather than iterate through each IP address, the program tries to skip through
entire classes at a time (256 IPs, 65536 IPs, etc). Rather than iterate
through each IP, the loop iterates through classes or IP ranges (whichever are
smaller at the loop control), using control-breaks to accummulate neighbouring
ranges where possible so that entire classes that are in the same country dont
generate huge numbers of records.
Firstly, IPs are considered to be 4-digit numbers, but in base-256. In other
words, each octet is dealt with as if it were a single base-256 digit. This
turns out to be convenient because optimisations of large chunks of IP space can be done by looking for places where least-significant base-256 digits are zero.
Next, IP ranges are broken down into the following sub-ranges:
Optional individual IP addresses (ie: 4 octets)
Optional A-class ranges (ie: 3 octets)
Optional B-class ranges (ie: 2 octets)
Optional C-class ranges (ie: 1 octet)
Optional B-class ranges (ie: 2 octets)
Optional A-class ranges (ie: 3 octets)
Optional individual IP addresses (ie: 4 octets)
Considering that there is a pattern here, Im sure theres an elegant way to
handle breaking this down into two loops (one reducing the octets and one
increasing the octets), but I cant be bothered, so Ill break it down into
seven loops. Kind of hard-coded, but at least its simple.
For ease of processing, the IP addresses are actually converted to 32-bit numbers, then back again. This simplifies mathematics and looping through ranges.
Thats pretty much it, really...
Note that currently there are about 80,000 RIR records between all five
registries. This takes about 35 seconds on a 2.4GHz P4 to process, and
generates a 26MB file with around 3/4 million lines (RRs). This causes BIND
to use about 100MB or so of memory, and on a slow machine will probably cause it to take too long to reply, while it searches the zone. That size zone can
take a minute or two to load, which is quite a while.
Basic algorithm:
Read & process RIR data:
Read RIR ranges
Sort RIR ranges by start IP address
Glue together contiguous ranges of the same country
For each range
Generate the IPs at the start of the range
Generate the A-classes at the start of the range
Generate the B-classes at the start of the range
Generate the C-classes in the middle of the range
Generate the B-classes at the end of the range
Generate the A-classes at the end of the range
Generate the IPs at the end of the range
Download (0.60MB)
Added: 2007-04-27 License: GPL (GNU General Public License) Price:
913 downloads
PerlMagick 6.2.7
PerlMagick is an objected-oriented Perl interface to ImageMagick. more>>
PerlMagick project is an objected-oriented Perl interface to ImageMagick. Use the module to read, manipulate, or write an image or image sequence from within a Perl script. This makes it very suitable for Web CGI scripts. You must have ImageMagick 6.2.0 or above and Perl version 5.005_02 or greater installed on your system for either of these utilities to work.
There are a number of useful scripts available to show you the value of PerlMagick. You can do Web based image manipulation and conversion with MagickStudio, or use L-systems to create images of plants using mathematical constructs, and finally navigate through collections of thumbnail images and select the image to view with the WebMagick Image Navigator.
Installation:
The following instructions for Unix apply only to the unbundled PerlMagick as obtained from CPAN. PerlMagick is included as a subdirectory (PerlMagick) of the ImageMagick source distribution, and may be configured and built using the instructions provided in the ImageMagick distributions README.txt file. It is usually most convenient to install PerlMagick as part of the ImageMagick distribution.
ImageMagick must already be installed on your system. Next, get the PerlMagick distribution corresponding to the installed ImageMagick distribution (e.g. PerlMagick 6.22 for ImageMagick 6.2.2) and unpack it as shown below:
gunzip -c PerlMagick-6.22.tar.gz | tar -xvf -
cd PerlMagick
Next, edit Makefile.PL and change LIBS and INC to include the appropriate path information to the required libMagick library. You will also need paths to JPEG, PNG, TIFF, etc. delegates if they were included with your installed version of ImageMagick. Build and install it like this:
perl Makefile.PL
make
make install
For Unix, you typically need to be root to install the software. There are ways around this. Consult the Perl manual pages for more information.
<<lessThere are a number of useful scripts available to show you the value of PerlMagick. You can do Web based image manipulation and conversion with MagickStudio, or use L-systems to create images of plants using mathematical constructs, and finally navigate through collections of thumbnail images and select the image to view with the WebMagick Image Navigator.
Installation:
The following instructions for Unix apply only to the unbundled PerlMagick as obtained from CPAN. PerlMagick is included as a subdirectory (PerlMagick) of the ImageMagick source distribution, and may be configured and built using the instructions provided in the ImageMagick distributions README.txt file. It is usually most convenient to install PerlMagick as part of the ImageMagick distribution.
ImageMagick must already be installed on your system. Next, get the PerlMagick distribution corresponding to the installed ImageMagick distribution (e.g. PerlMagick 6.22 for ImageMagick 6.2.2) and unpack it as shown below:
gunzip -c PerlMagick-6.22.tar.gz | tar -xvf -
cd PerlMagick
Next, edit Makefile.PL and change LIBS and INC to include the appropriate path information to the required libMagick library. You will also need paths to JPEG, PNG, TIFF, etc. delegates if they were included with your installed version of ImageMagick. Build and install it like this:
perl Makefile.PL
make
make install
For Unix, you typically need to be root to install the software. There are ways around this. Consult the Perl manual pages for more information.
Download (MB)
Added: 2006-04-26 License: GPL (GNU General Public License) Price:
1297 downloads
saml-registry 2005-11-08
saml-registry is a SAML 2.0 Metadata management tool that is useful for building shibboleth-based federations. more>>
saml-registry is a SAML 2.0 Metadata management tool that is useful for building shibboleth-based federations.
The saml-registry is a j2ee-application intended as a federation management tool, primarily (but not exclusively) for use with shibboleth. Future versions will support full delegation of rights through container-based role-management. The current version relies on container-based authentication.
For convenience the current version of the sql database schema and a jboss datasource descriptor sample can be found here on the right.
Installation instructions
Download the ear-file from the maven repository and drop it in the deploy-directory of your jboss application server. This build has been tested with jboss 4.0.2 but later versions should work.
You may need to disable certain features in a standard jboss, notably the jboss-ws4ee.sar (which conflicts with webservices provided by saml-registry) - just remove it from the deploy directory. Newer versions of jboss may ship with included versions of myfaces and jsf. These files must also be removed from your jboss before deploying saml-registry (or you must repackage the application excluding these libraries from the ear).
Next create a datasource-file for the mysql datastore. The < jndi-name/ > must be set to jdbc/saml-registry. Now create the database (update the datasource file with the server, username and password). Drop this file next to the ear in the deploy-directory. Use the sql schema to populate the database.
Finally configure authentication and authorization for saml-registry. This is done in the container by editing the login-config.xml (for jboss). Create a security domain called saml-registry in login-config.xml. The attached login-config.xml contains a sample entry which is based on property-files. The UsersRolesLoginModule is described on the jboss wiki.
The authorization for saml-registry is also managed by the security domain using standard j2ee role-based security. The roles govern access to individual use-cases (represented by menu entries in the user interface). Future versions will add per-organizational access control to this basic framework so that management of entities can be delegated.
The use-cases and roles is documented by this usecase diagram. Once your security-domain is configured to serve these roles (by editing property-files or whatever) you should be able to point your browser to https://your-box.example.com/saml-registry and get the main menu (or a login page depending on how your security domain was setup).
Building from source
In order to build saml-registry from source (which can be obtained from the subversion repository) you need maven2 and java5 to build the sources. The saml-registry is based on an MDA toolchain called andromda. Normally maven2 should download and install all dependencies, however the user interface needs the jsf2 cartridge from the andromda plugins project which may not be distributed from the andromda maven repository. If maven2 complains about unresolved dependencies for jsf2 then checkout the andromda plugins project and build it manually.
<<lessThe saml-registry is a j2ee-application intended as a federation management tool, primarily (but not exclusively) for use with shibboleth. Future versions will support full delegation of rights through container-based role-management. The current version relies on container-based authentication.
For convenience the current version of the sql database schema and a jboss datasource descriptor sample can be found here on the right.
Installation instructions
Download the ear-file from the maven repository and drop it in the deploy-directory of your jboss application server. This build has been tested with jboss 4.0.2 but later versions should work.
You may need to disable certain features in a standard jboss, notably the jboss-ws4ee.sar (which conflicts with webservices provided by saml-registry) - just remove it from the deploy directory. Newer versions of jboss may ship with included versions of myfaces and jsf. These files must also be removed from your jboss before deploying saml-registry (or you must repackage the application excluding these libraries from the ear).
Next create a datasource-file for the mysql datastore. The < jndi-name/ > must be set to jdbc/saml-registry. Now create the database (update the datasource file with the server, username and password). Drop this file next to the ear in the deploy-directory. Use the sql schema to populate the database.
Finally configure authentication and authorization for saml-registry. This is done in the container by editing the login-config.xml (for jboss). Create a security domain called saml-registry in login-config.xml. The attached login-config.xml contains a sample entry which is based on property-files. The UsersRolesLoginModule is described on the jboss wiki.
The authorization for saml-registry is also managed by the security domain using standard j2ee role-based security. The roles govern access to individual use-cases (represented by menu entries in the user interface). Future versions will add per-organizational access control to this basic framework so that management of entities can be delegated.
The use-cases and roles is documented by this usecase diagram. Once your security-domain is configured to serve these roles (by editing property-files or whatever) you should be able to point your browser to https://your-box.example.com/saml-registry and get the main menu (or a login page depending on how your security domain was setup).
Building from source
In order to build saml-registry from source (which can be obtained from the subversion repository) you need maven2 and java5 to build the sources. The saml-registry is based on an MDA toolchain called andromda. Normally maven2 should download and install all dependencies, however the user interface needs the jsf2 cartridge from the andromda plugins project which may not be distributed from the andromda maven repository. If maven2 complains about unresolved dependencies for jsf2 then checkout the andromda plugins project and build it manually.
Download (MB)
Added: 2007-04-05 License: GPL (GNU General Public License) Price:
938 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above delegate search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
