[Download] | [Documentation Home] | [ Release Note]
This document provides information and instructions on the functionality of the Management Console of WSO2 Identity Server.
Your feedback on WSO2 Identity Server is most appreciated. Please send them to our mailing lists.
Download and install Identity Server as in here.
Point your browser to https://host:port/carbon. If you haven't changed the default settings then you should be able to login to https://localhost:9443/carbon using user name "admin" and password "admin".
This allows to define, import and evaluate entitlement policies defined in XACML 2.0. Following feature are supported with this release
External References:
WSO2 Identity Server works out of the box with the default internal user store.
Also we can configure Identity Server to work with external user stores via Active Directory, LDAP and JDBC.
The Claim Management component of the Identity Server enables to map a set of attributes from the underlying user store to a set of defined claims
The Claim Management component of the WSO2 Carbon enables to map a set of attributes from the underlying user store to a set of defined claims
The underlying user store can be either the external user store or the internal user store.
A set of claims are identified as a dialect.
The Profile Configuration Management component of the Identity Server allows to add/modify and delete profile configuration. The profile configuration controls how user's empty claim values behave in his profile. If a Claim in a user's profile is not given a value explicitly, then it is given a value based on the following configuration.
Key store management manages the keys that are stored in a database. A Key store must contain a key pair with a certificate signed by a trusted Certification Authority (CA). The WSO2 Carbon uses the JKS type private key called WSO2 Carbon.
WSO2 Carbon ships with an in built XKMS trust web service which is being built on top of XKMS specification and consists of 5 services which can be used to simplify key management
This shows the existing Log4j configuration. And it also allows you to modify existing configuration. You can either modify the global Log4j configuration, an Appender or a Logger. If you select Persist all Configurations Changes check box, all the modifications will be persisted and they will be available even after a server restart.
The Information Cards issuer component of the Identity Server enables to configure cards issuer settings
The Security Token Service component of the Identity Server to configure the generic STS to issue claim based security tokens
You can use the Shutdown/Restart feature to shutdown and restart the server.
The machine can be shutdown gracefully or forcefully.
The available options are:
All resources found in the Registry, can be searched through this interface. Search could be refined by optionally providing, resource name, created date range, updated date range, tags, comments, property name, property value and the content