Obtaining Business Owner Details from Wso2 APPM 2.1.0

At the time when I'm writing this APPM 2.1.0 is yet to release and I will use APPM 2.1.0 Alpha pack to obtain business owner details.

How to register the API client application

 

We can use post man client to send below payload with the headers to register API client application.

Headers
Authorization : Basic YWRtaW46YWRtaW4= ('YWRtaW46YWRtaW4=' is base64 encoded value of admin:admin)
Content-Type  :application/json

Payload
{ "callbackUrl":"www.google.lk",clientName":"app_11_04_0013","tokenScope":
"Production","owner":"admin","grantType":"password refresh_token","saasApp":true}
















The sample response is as below
{"clientId":"9Xb0a5VIqM3lh40Sz9nKNDTHK5ga","clientName":"app_11_04_0013",
"CallBackURL":"www.google.lk","clientSecret":"JxqHRTejpwQ3JomezwxAZZBGC3Ia"}

 

 Obtaining the access token

 

We need to get the base64encoded value of clientId:clientSecret to generate the curl command to obtain the access token. We can encode it from here.
The following curl command can be used to request the access token.
curl -X POST -H "Authorization: Basic OVhiMGE1VklxTTNsaDQwU3o5bktORFRISzVnYTpKeHFIUlRlanB3UTNKb21lend4QVpaQkdDM0lh" -H "Host: 127.0.0.1:9763" -H "Content-Type:application/x-www-form-urlencoded" http://localhost:9763/oauth2/token -d 'username=admin&password=admin&grant_type=password&scope=appm:read'

  The response will be as below.

 {"scope":"appm:read","token_type":"Bearer","expires_in":3600,"refresh_token":"d3b3fd808971155175081da473748b6d","access_token":"c7f5b01843b28ae7090a22f9db198c71"}


 Obtaining business owner details


Defining business owners can be done by using admin-dashboard which can be accessed using https://localhost:9443/admin-dashboard. You can find more details on business owners functionality form here

 
The request to obtain business user request

curl -X GET -H "Authorization: Bearer c7f5b01843b28ae7090a22f9db198c71" "http://localhost:9763/api/appm/publisher/v1.1/administration/businessowner/1" -i



 The response obtained
HTTP/1.1 200 OK Date: Thu, 02 Jun 2016 05:45:33 GMT Content-Type: application/json Transfer-Encoding: chunked Server: WSO2 Carbon Server {"site":"","email":"hasanthi@gmail.com","description":"","name":"hasanthi","properties":[],"id":1}

Comments

Post a Comment

Popular posts from this blog

Applying CORS Filter to wso2 Identity Server

When we are invoking an endpoint in oauth2 war from a javascript of a web app which is located in a different domain than identity server domain we are getting "No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://XXXXXXX is therefore not allowed access." The issue is occurring as the script on your page is running from a specifc domain and would try to request the resource via an XmlHttpRequest or XDomainRequst from a different domain as this is a cross -origin request. In order to get rid of this we need to enable this by sending below header using a custom filter.  Access-Control-Allow-Origin: http: //example.com   (Here  http://example.com is the domain name of where page with that script is hosted) Invoking UserInfo endpoint of wso2 Identity Server from JavaScript We have two possible solutions to apply the CORS header.  1. Customizing OpenIDConnectUserEndpoint.java as below and replacing the oauth
Read more

JWKS endpoint of wso2 IS

What is JWKS endpoint? The JSON Web Key Set (JWKS) endpoint is a read-only endpoint. This url returns the Identity Server's public key set in Json web key set format. This contains the signing key(s) the RP uses to validate signatures from the Identity Server. This endpoint is defined loosely by the OpenID Connect Discovery specification . Try JWKS endpoint with Identity Server The endpoint url for the super tenant: https://localhost:9443/oauth2/jwks The jwks for the super tenant will be as follows: { "keys" : [ { "alg" : "RS256" , "kty" : "RSA" , "use" : "sig" , "n" : " AJSn-hXW9Zzz9ORBKIC9Oi6wzM4zhqwHaKW2vZAqjOeLlpUW7zXwyk4tkivwsydPNaWUm-9oDlEAB2lsQJv7jwWNsF7SGx5R03kenC-cf8Nbxlxwa-Tncjo6uruEsK_Vke244KiSCHP8BOuHI-r5CS0x9edFLgesoYlPPFoJxTs5 " , "e" : "AQAB" , "kid" : " d0ec514a32b6f88c0abd12a2840699bdd3deba9d "
Read more

DCR VS DCRM with WSO2 Identity server

Image
What is DCR (Dynamic Client Registration) Dynamic Client registration is a protocol which allows OAuth clients to register applications in an authorization server. Before this mechanism which is introduced from the spec [1] the client registration happened manually. With this implementation the client registration could be done in two ways.  - A client can be registered dynamically with the authorization server itself  - A programmer can register a client programmatically. Following is the protocol flow of DCR 1. A client sends a registration request with as follows. This should be a post request. 2. Server sends information response with 201 created. Request : POST   https://localhost:9443/api/identity/oauth2/dcr/v1.0/register HTTP/1.1 Authorization : Basic   YWRtaW46YWRtaW4= Content-Type :   application/json Content -Length :   114 Host: localhost :9443 {    "redirect_uris" : [      " http://localhost"    ],   
Read more