Hi Dilan, Did you tried sending the scope (Production / Sandbox) parameter along with the token request?
Thanks, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: [email protected] Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com <http://wso2.com/>* lean.enterprise.middleware. On Mon, Dec 22, 2014 at 12:49 PM, Dilan Udara Ariyaratne <[email protected]> wrote: > Hi All, > > I have been working on writing some test cases for a solution provided to > emm product on the following issue. > https://wso2.org/jira/browse/EMM-695 > > During the process of writing a test case for the insert query of device > registration functionality of EMM, > I have noticed the following behavior at the API Management module of EMM. > > [1] I have tried to access both client key(id) and client secret of admin > user for the default application > through both > http://localhost:9763/productapistore/site/pages/subscriptions.jag ui and > the rest client. > As expected, those values happened to be similar. > > Please refer to screenshot 1 and 2 for this. > > [2] Then, I tried to access the access token from the rest client as shown > in screenshot 3 and > was able to successfully retrieve an access token from the > http://localhost:9763/oauth2/token endpoint. > > However the problem is that the access token value I am getting from > the product-api-store web app ui (as in screenshot 1) > and the access token I am getting from the rest client call (as in > screenshot 3) are two different values. > > Is this a bug or the standard behaviour of the module? > > Highly appreciate any feedback on this. > > Thanks. > > > *Dilan U. Ariyaratne* > Software Engineer > WSO2 Inc. <http://wso2.com/> > Mobile: +94775149066 > lean . enterprise . middleware >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
