Why an IAM Testbed?
Potential adopters of one or more open source packages supporting IAM need to see working solutions to problems they are trying to solve. The goal of the IAM Testbed effort is to provide this environment and make it easy to use for demos.
What's in the Testbed?
The Testbed idea is just getting hatched. It is certain to be an iterative process of bringing more components online over time and knitting them into the Testbed framework. Some of the offerings have open access with test accounts. Others require users request that a guest account be created. The anchor offerings, on their way to being wired up for demo solutions include:
- Penn State's Open Source version of the Central Person Registry running in the Amazon Cloud
- An instance of 389 Directory Server (LDAP) running in the Amazon Cloud
- An instance of the Grouper group and permission management package from Internet2 running on a Linode VM
- The SCIM SDK from UnboundId (released under a non-exclusive, royalty-free license); installed on a Linode VM
- A full installation of Apache ActiveMQ on a Linode VM (Note that this incorporates a full version of Apache Camel as well)
- The Apache CAMEL integration package (implementing all the integration patterns found in the Enterprise Integration Patterns book) installed on a Linode VM
- An instance of Apache Servicemix on a Linode VM
- An instance of uPortal on a Linode VM
- Coming next: CAS, Shib and the Confluence wiki
How to use the Testbed
We are still very early in the Testbed roll-out. If you have experiments you would like to try or questions or suggestions regarding the Testbed, please send email to iamtestbed (at) gmail (dot) com
Testbed developers: We're using github issue tracking for coordinating our development tasks and milestones: https://github.com/apereo/iam-testbed Email iamtestbed (at) gmail (dot) com to request access to the github repo.