Skip to main content

Connect wso2 API Manager(1.8.0) with Identity Server(5.0.0)

1. start the identity server with  wso2server.bat
if you are working on windows environment use wso2server.bat -Dcarbon.home=Path_IS_Without_Quotation


2. Add Key Manger and Registery Extenstions Feature
     if you are working in windows environment, you have to follow 1st step before install features

3.  Copy the api-manager.xml file from the <APIM_HOME>/repository/conf directory and paste it into the <IS_HOME>/repository/conf directory.

4. Change following tags in api-manager.xml file in <IS_HOME>/repository/conf

<GatewayType>None</GatewayType>

 <RevokeAPIURL>https://localhost:8243/revoke</RevokeAPIURL> 
 you need to add https.nio.port for revokeapiurl and its 8243 for api manager

<ServerURL>https://localhost:9443/services/</ServerURL> 

<EnableThriftServer>false</EnableThriftServer> 

5. Restart and test whether IS is running upto this step. 

6. follow the document (https://docs.wso2.com/display/CLUSTER420/Configuring+the+Identity+Server+5.0.0+with+the+API+Manager+1.8.0+or+1.7.0) 9th steps to 17th step

if you get any error like 'ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes' when running db scripts,  you have to change database charset utf to latin1

7. add mysql connector jar file (5.1.* versions) to 
 <APIM_HOME>/repository/components/libs and
<IS_HOME>/repository/libs

8. Follow the instructions under Configuring the API Manager and do the configurations for all the steps.



Possible Faliures :-
      * if you change mysql connector, you have to remove them from both repository/components/lib folder and repository/components/dropins folder.you have to use 5.1.* versions for mysql connector.  




Comments

Popular posts from this blog

Reverse Proxy configuration with WSO2 Identity Server 5.0.0

Reverse proxy is a type of a proxy which can hide back end servers from the client applications. According to the above figure, Original servers are not exposed to the internet. Only reverse proxy is exposed to the internet.Client knows only the reverse proxy IP address. So he thinks that he is sending a request to the reverse proxy.He doesn't know anything about the original server. You can avoid some attacks using this architecture. Today I'm going to configure Apache HTTPD server(reverse proxy) and WSO2 identity server 5.0. Please download WSO2 identity server 5.0 from here You can install apache httpd server using below commands sudo apt - get update sudo apt - get install apache2 Restart the newly install apache server sudo service apache2 restart Apache is a modular server. This implies that only the most basic functionality is included in the core server.So You have to enable few other required features. Please use below command

Essential Debug Logs for WSO2 Identity Server

Essential Debug loggers for WSO2 Identity Server  When you are working with WSO2 products, you have to enable debug logs to investigate issues. Its better to enable debug logs only for particular module that you need to investigate. It reduce debug writing time and unnecessary debug reading time.So you can easily understand the root cause when you are reading the console.I'm going to discuss about debug lines one by one. You have to add debug line to [WSO2_HOME]\repository\conf\log4j.properties file, all debug lines are displayed in the console and write to the wso2carbon.log file. To enable loggers for user core.This is helpful to investigate user related issues. log4j.logger.org.wso2.carbon.user.core=DEBUG      To enable debug logs for identity module. This debug log will be helpful to investigate identity related issues. log4j.logger.org.wso2.carbon.identity=DEBUG If you need to investigate saml assertion or assertion related issue, you can enable debug

CURL commands to get access token from WSO2 Identity Server

WSO2 Identity server supports all grant types those are defined in oAuth2 core specification Four grant types: Authorization Code Grant Implicit Grant Resource Owner Password Credentials Grant (password) Client Credentials Grant We cannot use curl command directly to get an access token for Authorization code grant type and Implicit grant type. I'm going through other two grant types one by one and provide the curl command to get access token. 3. Get access token using password grant type curl -k -d "grant_type=password&username=admin&password=admin" -H "Authorization: Basic ME5fbXdWRXpTVnhfalJIbDV2cmc4RHIycHZBYTp0RmZjcHVFRFM5V1d2eFFEc1ZCd0tWVGd0dE1h, Content-Type: application/x-www-form-urlencoded" https://localhost:9443/oauth2/token ME5fbXdWRXpTVnhfalJIbDV2cmc4RHIycHZBYTp0RmZjcHVFRFM5V1d2eFFEc1ZCd0tWVGd is the encoded value of 0N_mwVEzSVx_jRHl5vrg8Dr2pvAa:tFfcpuEDS9WWvxQDsVBwKVTgttMa (<client_id>:<client_secret>). these