Skip to main content

Posts

Showing posts from 2015

Integrate WSO2 registry lifecycle with WSO2 API Manager 1.10

An API artifact has its own lifecycle to govern.A life-cycle contains set of states,actions happened during each state transitions and check list items before do a state transition.With previous APIM previous releases,we had a pre-defined lifecycle with pre-defined six states as ‘CREATED’,’PROTOTYPED’,’PUBLISHED’,’BLOCKED’,’DEPRECATED’,’RETIRED’ and pre-defined actions engaged with each state transitions  which cannot be extend or customize.There was a requirement came from many users,can’t they extend the default API lifecycle engaged with WSO2 API Manager as to add their defined state names,invoke their custom actions during state transitions [eg:send notifications at each transition],add custom checklist items before state transitions. To achieve above,we decided to integrate WSO2 registry based lifecycle with APIManager.WSO2 registry based lifecycle provides a configurable way to define the lifecycle of an artifact which a user can easily extend.For more information ,re

Set custom password policies to APIStore signup

In WSO2 Identity Server, it can define custom password policies and enforce them at user creation. Could the same feature use in  WSO2 APIStore self signup?Yes ,it's possible with following below steps. To  set the user password policy during sign up for Store   in AM 1.9.1,first user need to install the " Account Recovery and Credential Management' feature on top of API Manager 1.9.1.   1. Log into the APIM's Management Console [ https://localhost:9443/carbon ] 2. On the left side menu section 'Configure', go to features -> repository Management and add Repository with a relevant name e.g. account-mgt 3. Give the following as the repository URL  and add the repository. http://dist.wso2.org/p2/ carbon/releases/turing/ 4. Then select  " Show only the latest versions" option in the showing features installation UI and click on  "Find the features" button. 5. Then select "Account Recovery and Credential

How to lock a user to avoid token generation via password grant type in APIM 1.7.0

First have to install user lock/unlock feature in APIM 1.7.0. Login to APIM 1.7.0 management console and navigate to ‘features’ menu via           left menu ‘Configure -> Features’  and select ‘Add Repository’ from shown UI as below.            Then add a new repo with giving the url as http://product-dist.wso2.com/p2/carbon/releases/turing/  and click ‘Add’ button as shown below.    4) Then click on ‘Find Features’ button shown in UI.    5) There will be a list of features shown based on products. To install user account        locking/unlocking feature to AM 1.7.0,you have to select the feature “ Account Recovery and Credential Management -version 4.2.0 ” from ‘Identity Server 4.5.0 feature group’ under Identity Management features section. Select the feature and click on ‘install’ button as shown below. 6) Then proceed the feature installation process as shown below. 7) Once you successfully installed the above feature,finally you’ll s

WSO2 API Manager features integration with Governance Center of WSO2 Governance Registry 5.0.0

For past five months I was involved with the team effort of integrating APIM capabilities to the governance center which is released as WSO2 Governance Registry (GReg) product 5.0.0.Let's get into more details on the topic. WSO2 Governance Registry 5.0.0 WSO2 GReg product is a fully open source SOA integrated repository for storing and managing metadata related to service artifacts.In other words,it's a repository to store metadata like policies, wsdls, wadls,swagger definitions related to SOAP/REST services and store SOAP/REST services themselves. Each of these metadata models can be called as an asset type.Such that GReg can be introduced as a repository to keep different asset types as wsdl,wadl,policy,soap service,rest service.Additionally a user can configure and extend GReg to add their customized metadata models via adding "configurable governance artifacts" option(rxt) which is described in here . In previous GReg releases [before 5.0.0 version