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/ On Wed, Dec 11, 2019 at 9:37 PM Bernard Paris <[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/ > > 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"; -H "accept: */*" -H > "Authorization: Bearer eyJ0eXAiOiJKV…." > > <ams:fault > xmlns:ams="http://wso2.org/apimanager/security";><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] > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Harsha Kumara* Technical Lead, WSO2 Inc. Mobile: +94775505618 Email: [email protected] Blog: harshcreationz.blogspot.com GET INTEGRATION AGILE Integration Agility for Digitally Driven Business
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
