I believe you meant this configuration (attached).
I already have it.
Please let me know if you mean something else?
Regards
Shib
On Fri, Jun 29, 2018 at 10:40 AM, Pubudu Gunatilaka
wrote:
> Please find the link in [1].
>
>
> [1] - https://docs.wso2.com/display/AM210/Include+
>
Please find the link in [1].
[1] -
https://docs.wso2.com/display/AM210/Include+Additional+Headers+in+the+API+Console
On Fri, Jun 29, 2018 at 10:34 AM shibsankar wrote:
> your Link is not opening.
>
> Could you please check and resend the link?
>
> Regards
> Shib
>
>
> On Fri, Jun 29, 2018 at
your Link is not opening.
Could you please check and resend the link?
Regards
Shib
On Fri, Jun 29, 2018 at 10:25 AM, Pubudu Gunatilaka
wrote:
> Hi Shib,
>
> Have you enabled CORs for token endpoint? If not could you please enable
> CORs for token as in
Hi Shib,
Have you enabled CORs for token endpoint? If not could you please enable
CORs for token as in
https://docs.wso2.com/display/AM210/Include+Additional+Headers+in+the+API+Console.
Last part of the document explains how to enable CORs for token endpoint
and other Oauth2 APIs.
Thank you!
Any comments to this?
For your convenience, I'm also attaching Chrome browser console Network
report for token API call
Is there anything I'm missing?
why I'm getting *Failed to
load http://xx-xx-xxx-xx-xx.xx.xx..com:8280/token
Hi Shib,
Configuration changes to enable CORS in wso2 server seem to be correct.
I think you have to explicitly set withCredentials atribute which is a
client side attribute to false from your
angular application or whitelist the origin in api-manager.xml without
using '*'.
Please refer [1]
