Hi,
We suspect that bug is there in rest API implementation change or transport
level change. There are 2 options to avoid this.
01. Remove post fix uri parameter and invoke /token API
02. Build incoming message inside in sequence (put full log
inside in-sequence).
We need to check this with ESB team. If you are testing AM for the moment
use following token definition.
<api name="_WSO2AMTokenAPI_" context="/token">
<resource methods="POST" url-mapping="/*">
<inSequence>
<log level="full">
<property name="STATUS" value="Executing default token
endpoint"/>
</log>
<send>
<endpoint>
<address uri="https://localhost:9443/oauth2/token"/>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</resource>
</api>
Thanks,
Sanjeewa.
On Thu, Aug 22, 2013 at 10:36 AM, Ruwan Yatawara <[email protected]> wrote:
> Hi All,
>
> I am getting an invalid response when invoking the /token api to create
> User tokens.
>
> Steps Followed ;
>
> URL : https://localhost:8243/token
> Headers : Authorization : Bearer base64-encoded<consumer key>:<consumer
> sector>
>
> Payload
> : grant_type=password&username=USER_NAME&password=PASSWORD&scope=PRODUCTION
>
> The response I get is : <token_type>
> bearer
> </token_type>
>
> This should not be the case.
>
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Software Engineer,
> WSO2 Inc.
> lean . enterprise . middleware
>
> email : [email protected]
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*
*
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
<http://sanjeewamalalgoda.blogspot.com/>blog
:http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
