Hi Harsha, Thanks a lot for your mail, it has solved my problem.
Bernard Le 11 déc. 2019 à 17:17, Harsha Kumara <[email protected]<mailto:[email protected]>> a écrit : Hi Bernard, Did you generate a new keystore? if so newly generated keystores, public certificate should be added to client-trustore.jks with alias of gateway_certificate_alias by replacing the existing one. https://apim.docs.wso2.com/en/latest/Learn/APISecurity/OAuth2DeepDive/AccessTokenTypes/jwt-tokens/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapim.docs.wso2.com%2Fen%2Flatest%2FLearn%2FAPISecurity%2FOAuth2DeepDive%2FAccessTokenTypes%2Fjwt-tokens%2F&data=02%7C01%7C%7C92cbf38fa12544e5a4cc08d77e55a337%7C7ab090d4fa2e4ecfbc7c4127b4d582ec%7C0%7C0%7C637116778585518114&sdata=yB8NxxEpi0Dsa5Rf7VGLv93iv7BjTgoFQ%2FUr2W0PAsc%3D&reserved=0> On Wed, Dec 11, 2019 at 9:37 PM Bernard Paris <[email protected]<mailto:[email protected]>> wrote: Hi devs, I'm testing wso2am-3.1.0-m4 I'm not sure this is n issue or a missing configuration stuff, here is the problem: On my own "localhost" workstation I can with no problem configure and run the example at https://apim.docs.wso2.com/en/latest/GettingStarted/quick-start-guide/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapim.docs.wso2.com%2Fen%2Flatest%2FGettingStarted%2Fquick-start-guide%2F&data=02%7C01%7C%7C92cbf38fa12544e5a4cc08d77e55a337%7C7ab090d4fa2e4ecfbc7c4127b4d582ec%7C0%7C0%7C637116778585523108&sdata=cTKs2LfpRf9jLL9EyvNcxOq8VzELKcSzxP7asg0BQTk%3D&reserved=0> I have installed wso2am-3.1.0-m4 on a server, edit the "hostname" entry in deployment.toml file, and set the certificate for this hostname in the keystone. I'm unable to request the APIs because of strange security reasons. For example configure and run the same helloWorld example as before then requesting the API with: curl -X GET "https://my.server:8243/hello/v1<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmy.server%3A8243%2Fhello%2Fv1&data=02%7C01%7C%7C92cbf38fa12544e5a4cc08d77e55a337%7C7ab090d4fa2e4ecfbc7c4127b4d582ec%7C0%7C0%7C637116778585528094&sdata=R4Y3PjOjGoef8LGvAjfu99CFWIwPQV%2FXSGrb5QjsFOw%3D&reserved=0>" -H "accept: */*" -H "Authorization: Bearer eyJ0eXAiOiJKV…." <ams:fault xmlns:ams="http://wso2.org/apimanager/security<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwso2.org%2Fapimanager%2Fsecurity&data=02%7C01%7C%7C92cbf38fa12544e5a4cc08d77e55a337%7C7ab090d4fa2e4ecfbc7c4127b4d582ec%7C0%7C0%7C637116778585528094&sdata=Qq9%2BNYAGbLQWv4fKbxzzNM576Y2eZGiJLegzVCmAVmo%3D&reserved=0>"><ams:code>900901</ams:code><ams:message>Invalid Credentials</ams:message><ams:description>Invalid JWT token. Make sure you have provided the correct security credentials</ams:description></ams:fault> What do you think ? Bernard _______________________________________________ Dev mailing list [email protected]<mailto:[email protected]> http://wso2.org/cgi-bin/mailman/listinfo/dev<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwso2.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fdev&data=02%7C01%7C%7C92cbf38fa12544e5a4cc08d77e55a337%7C7ab090d4fa2e4ecfbc7c4127b4d582ec%7C0%7C0%7C637116778585533091&sdata=P47xWCXEhu1agFq5ziO8WlDLzqyywlPsXwWxRNW63Cw%3D&reserved=0> -- Harsha Kumara Technical Lead, WSO2 Inc. Mobile: +94775505618 Email: [email protected]<mailto:[email protected]> Blog: harshcreationz.blogspot.com<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fharshcreationz.blogspot.com&data=02%7C01%7C%7C92cbf38fa12544e5a4cc08d77e55a337%7C7ab090d4fa2e4ecfbc7c4127b4d582ec%7C0%7C0%7C637116778585538079&sdata=URYZRtBmW96XVG%2FO8Rlx5euwoaMt%2F1bn4Mjb4vjmpPo%3D&reserved=0> GET INTEGRATION AGILE Integration Agility for Digitally Driven Business
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
