dev-portal | SingularityNET Developer Portal where you can find | Blockchain library

When you make a call the generated access token will be cached. That's how generally it works. Go through the following documentation where it describes the configurations related to WSO2 APIM. By going through the part which explains cache mechanisms you will be able to get a proper understanding. https://apim.docs.wso2.com/en/next/reference/config-catalog/#gateway-token-cache

So I found a way but I couldn't find any documentation about it.

This code sample suggest that the Cloud Endpoints Portal needs ESP. But unlike Cloud Endpoints with OpenApi, Cloud Endpoints Framework does not use ESP, but:

a built-in API gateway that provides API management features that are comparable to the features that ESP provides for Endpoints for OpenAPI

Therefore, the openapi.json file generated by mvn endpoints-framework:openApiDocs is missing some info.

Here is what I changed:

At the class level, in the @Api annotation:

• added an audience (even though I don't have Android clients and, according to the documentation, audiences are for Android clients only)
• added a custom authenticator to handle ESP, similar to com.google.api.server.spi.auth.EspAuthenticator

In the openapi.json file, after it's generated with mvn endpoints-framework:openApiDocs

• section securityDefinitions, the authorizationUrl https://accounts.google.com/o/oauth2/v2/auth (I had an error otherwise)
• in the declaration of the path of my method, the security section with the OAuth scope in it

Sources:

API