Orenosp SSO lets employees to log in with existing username and passwords (e.g., AD) while outside partners can log in with their OpenID URLs. Once logged into Orenosp SSO, the user can access internal apps without re-authentication.
For example, if you have an IT infrastructure consisting of an Exchange server (OWA) and a Sharepoint server in your company and want to collaborate with your partners using your IT infrastructure, you would be facing many issues around user authentication, password insecurity and management chores. Orenosp V2 SSO offers an solution for such a case.
| Version | Feature | Description | Release Target | Status |
|---|---|---|---|---|
| 2.0 | Single-Sign-On using OpenID | Offers a practical solution for solving cross-organizational authentication
issues when trying to collaborate with partners using commercial web applications like Exchange Server and SharePoint Services. |
Currently in Beta. Release data TBD | First beta version, Beta-1 is available. Note: Please see Beta Evaluation Guide for installation and usage for this beta.
|
| 2.1 | Performance-enhancing Cache and Web Application Accelerator for Branch Offices |
Compressed Cache: content caching in gzipped-compressed form to optimze for disk storage, network bandwidth and CPU load. Web Application Accelerator : locating Orenosp on the client side (i.e., branch offices) to accelerate access to web applications at the data center. |
TBD | In Planning |
More detailed enhancements roadmap will be coming soon as another document.
Orenosp uses OpenSSL Toolkit developed by the OpenSSL Project (http://www.openssl.org/).
Orenosp V2 uses libopkele, OpenID protocol library written in C++. If you are interested in using libopkele from Windows applications written in C/C++, please see my patch for libopkele here.