Welcome to WSO2 Identity Server

Branch	Build Status
master

WSO2 Identity Server is an open source Identity and Access Management solution federating and managing identities across both enterprise and cloud service environments. It supports a wide array of authentication protocols such as SAML 2.0 Web SSO, OpenID, OAuth 2.0/1.0a, OpenID Connect and WS-Federation Passive. It supports role based authorization and fined grained authorization with XACML 2.0/3.0 while inbound/outbound provisioning is supported through SCIM and SPML.

This is based on the revolutionary WSO2 Carbon framework. All the major features have been developed as pluggable Carbon components.

System Requirements

Minimum memory - 2 GB
Processor - 2 Core/vCPU 1.1GHz or higher
Java SE Development Kit 1.8
The Management Console requires full Javascript enablement of the Web browser.
To build WSO2 Identity Server from the Source distribution, it is also necessary that you have Maven 3 or later.

For more details see

https://is.docs.wso2.com/en/latest/setup/installation-prerequisites/ (For latest released version)
https://is.docs.wso2.com/en/next/setup/installation-prerequisites/ (For current development version)

Project Resources

Home page : http://wso2.com/products/identity-server
Library : http://wso2.org/library/identity
Wiki
- Latest released version : https://is.docs.wso2.com/en/latest/
- Current development version : https://is.docs.wso2.com/en/next/
Issue Tracker : https://github.com/wso2/product-is/issues
Forums : http://stackoverflow.com/questions/tagged/wso2is/
WSO2 Developer List: dev@wso2.org

Building the distribution from source

Install Java SE Development Kit 1.8
Install Apache Maven 3.x.x(https://maven.apache.org/download.cgi#)
Get a clone from https://github.com/wso2/product-is.git or download the source
Run the one of the below maven commands from product-is directory,
- mvn clean install (To build the binary and source distributions with the tests)
- mvn clean install -Dmaven.test.skip=true (To build the binary and source distribution, without running any of the unit/integration tests)
You can find the binary distribution in product-is/modules/distribution/target directory.

Installation and Running

Extract the downloaded/built binary distribution zip file
Run the wso2server.sh or wso2server.bat file in the /bin directory
Once the server starts, point your Web browser to https://localhost:9443/carbon/
User dashboard is available at https://localhost:9443/dashboard
For more information, see the Installation Guide

WSO2 Identity Server Distribution Directory Structure

        CARBON_HOME
        ├── bin
        ├── dbscripts
        ├── lib
        ├── repository
        │   ├── components
        │   ├── conf
        │   │   └── identity
        │   │       ├── identity-providers
        │   │       └── service-providers
        │   ├── database
        │   ├── deployment
        │   ├── logs
        │   ├── resources
        │   │   ├── identity
        │   │   └── security
        │   └── tenants
        └── tmp


- bin
  Contains various scripts .sh & .bat scripts.

- dbscripts
  Contains the database creation & seed data population SQL scripts for
  various supported databases.

- lib
  Contains the basic set of libraries required to startup Carbon.

- repository
  The repository where Carbon artifacts & Axis2 services and 
  modules deployed in WSO2 Carbon are stored. 
  In addition to this other custom deployers such as
  dataservices and axis1services are also stored.

    - components
      Contains all OSGi related libraries and configurations.

    - conf
      Contains server configuration files. Ex: axis2.xml, carbon.xml

        - identity
          Contains all configurations related to identity.

            - identity-providers
              Identity providers configured using file

            - service-providers
              Service providers configured using file

    - database
      Contains the WSO2 Registry & User Manager database.

    - deployment
      Contains server side and client side Axis2 repositories. 
      All deployment artifacts should go into this directory.

    - logs
      Contains all log files created during execution.

    - resources
      Contains additional resources that may be required.

- tenants
  Directory will contain relevant tenant artifacts 
  in the case of a multitenant deployment.

- tmp
  Used for storing temporary files, and is pointed to by the
  java.io.tmpdir System property.


- LICENSE.txt
  Apache License 2.0 under which WSO2 Carbon is distributed.

- README.txt
  This document.

- release-notes.html
  Release information for WSO2 Carbon ${carbon.product.version}.

Secure sensitive information in carbon configuration files

There are sensitive information such as passwords in the carbon configuration. You can secure them by using secure vault. Please go through following steps to secure them with default mode.

Configure secure vault with default configurations by running ciphertool script from bin directory.

ciphertool.sh -Dconfigure (in UNIX)

This script would do following configurations that you need to do by manually

(i) Replaces sensitive elements in configuration files, that have been defined in cipher-tool.properties, with alias token values.
(ii) Encrypts plain text password which is defined in cipher-text.properties file. (iii) Updates secret-conf.properties file with default keystore and callback class.

cipher-tool.properties, cipher-text.properties and secret-conf.properties files can be found at repository/conf/security directory.

Start server by running wso2server script from bin directory

wso2server.sh (in UNIX)

By default mode, it would ask you to enter the master password (By default, master password is the password of carbon keystore and private key)

Change any password by running ciphertool script from bin directory.

ciphertool -Dchange (in UNIX)

For more details see https://is.docs.wso2.com/en/5.10.0/administer/carbon-secure-vault-implementation

Support

We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity, visit http://wso2.com/support/.

For more information on WSO2 Carbon, visit the WSO2 Oxygen Tank (http://wso2.org)

For more information about WSO2 Identity Server please see http://wso2.org/projects/identity or visit the WSO2 Oxygen Tank developer portal for addition resources.

For further details, see the WSO2 Carbon documentation at https://docs.wso2.com/display/Carbon4411/WSO2+Carbon+Documentation

kratosmat/product-is