"the freedom to choose how interfaces are built"
Project OpenPTK is an open source Identity Provisioning Toolkit. The project is hosted at java.net
in the Identity Management community. Project OpenPTK exposes Java API's,
RESTful Web Service, WSDL-based Web Services, HTML Taglibs, JSR-168
Portlets with user self-service and administration examples. The
architecture supports several pluggable back-end services including
Service Provisioning Markup Language v1 and v2 (SPML), Databases (JDBC), LDAPv3 (UnboundID LDAP SDK, JNDI) and Oracle Identity Manager API.
Dear OpenPTK Community,
The project founders/developers are working on an enhancement: http://java.net/jira/browse/OPENPTK-340 that will introduce a format change.This enhancement is focused on improving JSON output from the READ and SEARCH operations. This issue is currently planned for release 2.2. Implementing this enhancement will create JSON outputs (READ and SERACH) that are NOT compatible with prior releases. The code "trunk" is being update to support this enhancement. The latest tagged version (2.1) is still available and it is NOT effected by this development change.
As always, we welcome your comments on this and other project issues.
Regards … Project OpenPTK Founders.
The OpenPTK owners are pleased to announce that release 2.1 is available. It has been "tagged" in the svn repository. See the download page for details.
This release is an update to version 2.0. This release contains bug fixes, enhancements to existing capabilities, and new features. The most notable change in this release is the use of maven, instead of ant, for the build process. The adoption of maven has made the project more modular, reduced its download size (less bundled jar files) and will enable the future support of Project OpenPTK in a maven repository.
The Project OpenPTK overview presentation has been updated. You can access it from the "References" page, or from this Download
A new Self-Service Registration
example has been created which leverages the reCAPTCHA
service. This sample application can be used as a reference for how a registration interface can be created with an increased level of assurance that a "real person" is entering the data and reduce automated "bot type" registrations. See the Self-Service Sample page
The OpenPTK owners are pleased to announce that release 2.0 was completed. It has been "tagged" in the svn repository. See the download page for details.
Release 2.0 of Project OpenPTK builds on the success of Release 1.x.
The goal ... enable developers to create custom interfaces to a variety of repositories ...
Release 2.0 gives the developer more choices for how they want to create custom interfaces. Release 2.0 supports more back-end repositories: SPML 1 and 2, LDAP, JDBC, Oracle Identity Manager 11g. Here is a summary of the major new features in version 2.0:
- Servlet-Based (Engine Architecture)
- RESTful-based Web Service
- Service / Operation Level Configuration
- Client-Side Java API
- Models, Views and Relationships
- Definition Functions
- Enhanced Search
Services can now take advantage of an automatic "re-start" feature. The new RestartService will attempt to re-start an Operations connection to its back-end data repository. The Service will attempt to "re-start" the connection if it was off-line when the OpenPTK Server booted. The Service will also attempt to "re-start" the Operations connection if it was dropped due to network issues or connection / idle timeouts. The Operation implementations have been updated to leverage this new feature.
This new Service uses the JavaDB (Derby) embedded database. A pre-loaded (sample data) embedded database has been created and is now the default pre-configured Context. The embedded database enables new users of Project OpenPTK to easily start evaluating the project and create custom interfaces without having to install, configure, load, and connect to a external database. The sample data includes over 500 "Employees", 20 "Locations" and photos of employees.
You don't have an LDAP server available for testing or piloting OpenPTK? No problem, the UnboundID LDAP SDK
service now support the built in functionality of an In-Memory Directory Server. All you need is an LDIF file to initialize the In-Memory Directory Server and you can immediately start using OpenPTK for your own application testing.
The UnboundID LDAP SDK
has be used to create a new LDAP Service. This service includes all features within the traditional standard JNDI service and implements additional features such as built in LDAP connection pools
An Oracle Database (JDBC-based) Service/Operations has been created along with sample SQL schema creation scripts.