Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

The WSO2 Identity Server is an enterprise-ready, fully-open source, lean, component-based solution for facilitating security and identity management of enterprise web applications, services, and APIs. Based on the award-winning WSO2 Carbon platform, the WSO2 Identity Server is lean, lightweight and consists of only the required components for efficient functioning. It does not contain unnecessary bulk, unlike many over-bloated, proprietary solutions.

As an enterprise's applications, services, and API adoptions grow, managing identities (i.e. employees, vendors, partners, and customers) across internal, shared, and SaaS services becomes a significant challenge. The WSO2 Identity and Entitlement management server with support for OpenID, Information Cards, XACML, and SAML 2.0.

This is based on the revolutionary WSO2 Carbon framework.

All the major features have been developed as pluggable Carbon components.

Key Features

  • Entitlement Engine with XACML 2.0 support
  • Claim-based Security Token Service with SAML 1.1/SAML 2.0 support
  • Information cards support for SAML 1.1/2.0
  • OpenID Provider
  • Extension points for SAML assertion handling
  • XMPP based multi-factor authentication
  • Improved User Management
  • Claim Management
  • User Profiles and Profile Management
  • XKMS
  • Separable front-end and back-end (a single front-end server can be used to administer several back-end servers)
  • Information Cards provider supporting Managed Information Cards backed by user name/password and self-issued cards
  • Multi-factor authentication with Information Cards

New Features In This Release

  • Thrift support in EntitlementService for PEP-PDP communication
  • Various improvements to security token service including performance improvements and token persistence support
  • Various bug fixes and enhancements including architectural improvements to Apache Axis2/Rampart/Sandesha2, WSO2 Carbon, and other projects. A fixed issue list is available.

Open Source Components of WSO2 Identity Server

  • WSO2 Carbon
  • Apache Axis2 (SOAP)
  • Apache Axiom (High performance XML Object Model)
  • Apache Rampart/Apache WSS4J (WS-Security, WS-SecureConversation)
  • Apache Rahas(WS-Trust)
  • WS-Addressing implementation in Axis2
  • Apache Neethi (WS-Policy)
  • WS-SecurityPolicy implementation in Axis2
  • Apache XML Schema
  • OpenID4Java
  • SunXACML
  • OpenSAML2
  • Apache Directory Server

Excerpt

hiddentrue
General information about the WSO2 Identity ServerServer enables enterprise architects and developers to efficiently overcome these challenges. It helps improve customer experience by reducing identity provisioning time, guaranteeing secure online interactions, and delivering a reduced single sign-on environment. The WSO2 Identity Server decreases identity management, entitlement management and administration burden by including role-based access control (RBAC) convention, fine-grained policy-based access control, and SSO bridging.

Known Issues

For a list of known issues in the Identity Server version 3.2.3, please refer to the following link in WSO2 Oxygen Tank: WSO2 Identity Server 3.2.3 - Known Issues.

Community Resources

WSO2 is willing to provide you guidance for any technical issues or questions regarding the Identity Server product. You can communicate with the WSO2 Identity Server development team directly using the relevant mailing lists mentioned here: http://wso2.org/mail.

WSO2 encourages you to report issues and enhancement requests for WSO2 Identity Server using the publicJIRA available at https://wso2.org/jira/browse/IDENTITY . You can also track their resolutions and comment on the progress.

Questions regarding the Identity Server can also be raised through http://stackoverflow.com. Ensure that you tag the question with appropriate keywords such as WSO2 and Identity Server so that our team can easily find your questions and provide answers.

For tutorials, articles, Webinars and similar resources, visit the WSO2 Oxygen Tank and search under the Resources menu.

Support Options

WSO2 also offers a variety of development and production support programs, ranging from Web-based support during normal business hours, to premium 24x7 phone support. WSO2 is committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that support leverages the open development methodology and is provided by the very same engineers who build the products. For additional support information please refer to http://wso2.com/support. 

Get Involved 

WSO2 invites you to contribute by checking out the source from SVN using the following commands. This project uses Subversion to manage its source code. Instructions on Subversion can be found at http://svnbook.red-bean.com.

The WSO2 Identity Server release 3.2.3 is based on Carbon 3.2.0.

Anonymous Checkout 

The complete source including the Carbon platform can be checked out anonymously from SVN with this command:

Code Block
$ svn checkout http://svn.wso2.org/repos/wso2/branches/carbon/3.2.0 wso2carbon

The list of commands that can be run are as follows. If you only want to build the Application Server, you have to always use the option "-Dproduct=is".

  
mvn clean install -Dproduct=isTo create the complete release artifacts of WSO2 Identity Server including the binary and source distributions.
mvn clean install -Dmaven.test.skip=true -Dproduct=isTo create the complete release artifacts of WSO2 Identity Server including the binary and source distributions, without running any of the unit tests.
mvn clean install -Dmaven.test.skip=true -Dproduct=is -oTo create the complete release artifacts of WSO2 Identity Server including the binary and source distributions, without running any of the unit tests, in offline mode. This can be done only if you've already built the source at least once.

Developer Access 

Everyone can access the Subversion repository via HTTPS, but Committers must checkout via HTTPS. The Carbon framework related source code can be checked out using the following commands.

Code Block
$ svn checkout https://svn.wso2.org/repos/wso2/branches/carbon/3.2.0/wso2carbon

The Carbon core project is the root project of the OSGi platform on which the Java product stack is built. The Carbon components contain all the components not just the Application Server specific ones. Therefore, you need to build just the set of components required by the Application Server, using the following command:

Code Block
$ mvn clean install -Dproduct=is

Execute the following command to commit your changes (SVN will prompt you for password).

Code Block
$ svn commit --username your-username -m "A message"

Access through a Firewall

If you are behind a corporate firewall which is blocking http access to the Subversion repository, you can try the developer connection:

Code Block
$ svn checkout https://svn.wso2.org/repos/wso2/trunk/carbon carbon

Access through a Proxy

The Subversion client can be configured to access through a proxy.

 1) Specify the proxy to use in the "servers" configuration file in:

  • "~/.subversion" directory for Linux/Unix
  • "%APPDATA%\Subversion" hidden directory for Windows. (Try "echo %APPDATA%")

2) There are comments in the file explaining what to do. If you don't have this file, get the latest Subversion client and run any command. It will create the configuration directory and template files.

Example : Edit the 'servers' file and add something similar to:

Code Block
[global]
http-proxy-host = your.proxy.name
http-proxy-port = 3128
Excerpt
hiddentrue

WSO2 Identity Server - community resources, forums and support options.