Versions Compared

Key

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

...

The WSO2 Identity Server version 4.0.0 is the successor of version 3.2.3 and built on Carbon 4.0.3 base platform. It has several enhancements and defect fixes included in it. For a list of fixed defects in this release, refer to:  

New Features and Enhancements:

  • XACML 3.0
  • OAuth 2.0
  • SCIM 1.1
  • IWA Authenticator 
  • Support for Multiple User Stores (inherited from new and enhanced Carbon 4.0.3)
  • WS-XACML
  • Read/Write Active Directory User Store Manager 
  • SAML2 Basic Attribute Profile

Known Issues

For a list of known issues in the Identity Server version 4.0.0, please refer to the following link in WSO2 Oxygen Tank:  

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 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:

...

.

...

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:

...


Excerpt
hiddentrue

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

...