[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[[["\u003cp\u003eThis document serves as a glossary of terms used within the Cloud Endpoints documentation, offering brief definitions and links to further information.\u003c/p\u003e\n"],["\u003cp\u003eIt covers a variety of concepts related to API management, including API keys, authentication services like Auth0 and Firebase, and token formats like JWT and Google ID tokens.\u003c/p\u003e\n"],["\u003cp\u003eThe document also explains the role of software like Docker, Kubernetes, and NGINX, highlighting their connection to containerization and API deployment.\u003c/p\u003e\n"],["\u003cp\u003eKey components of the Cloud Endpoints ecosystem are defined, such as the Extensible Service Proxy (ESP) and Extensible Service Proxy V2 (ESPv2), along with the standards they support, like OpenAPI and gRPC.\u003c/p\u003e\n"],["\u003cp\u003eIt also covers tools like \u003ccode\u003ekubectl\u003c/code\u003e which is used to interact with Kubernetes clusters, which is a deployment option.\u003c/p\u003e\n"]]],[],null,["# Glossary\n\nOpenAPI \\| [gRPC](/endpoints/docs/grpc/glossary \"View this page for the Cloud Endpoints gRPC docs\")\n\n\u003cbr /\u003e\n\nThis page provides brief definitions and links to more information of terms\nthat are used in the Cloud Endpoints documentation.\n\nAPI key\n: A code passed in by a client application when it calls an API. API\n keys identify the application or the Google Cloud project making\n the call to the API. See\n [Why and when to use API keys](/endpoints/docs/openapi/when-why-api-key)\n for more information on using an API key with your Endpoints API.\n\nAuth0\n: A service that lets you define how users authenticate to applications. See\n [Auth0](https://auth0.com) for more information.\n\nCloud Endpoints Frameworks\n: Endpoints Frameworks for the App Engine standard environment\n consists of tools, libraries, and capabilities that let you generate APIs and\n client libraries from an App Engine application. See\n [About Endpoints Frameworks](/endpoints/docs/frameworks/java/about-cloud-endpoints-frameworks)\n for more information.\n\ncontainer\n: A software package that contains the libraries, frameworks, and settings.\n that an application requires to run. See\n [What is a container](https://www.docker.com/what-container)\n for more information.\n\nCORS\n: Cross-Origin Resource Sharing (CORS) is a specification that provides a way\n for web applications to access resources on a server in another domain\n (technically, in another origin). To learn more about CORS, see the\n [Mozilla Developer Network (MDN) web docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)\n and the [Fetch Living Standard](https://fetch.spec.whatwg.org/).\n\nDocker\n: Open source software that lets you automate deploying applications inside\n software containers. See [What is Docker](https://www.docker.com/what-docker)\n for more information.\n\nExtensible Service Proxy\n: The Extensible Service Proxy (ESP) is an Nginx-based high-performance, scalable proxy\n that runs in front of an OpenAPI or gRPC API backend and provides API management\n features such as authentication, monitoring, and logging. See\n [About Endpoints](/endpoints/docs/openapi/about-cloud-endpoints)\n and\n [Endpoints: Architectural overview](/endpoints/docs/openapi/architecture-overview)\n for more information.\n\nExtensible Service Proxy V2\n\n: The Extensible Service Proxy V2 (ESPv2) is an [Envoy](https://www.envoyproxy.io/docs/envoy/latest/)-based\n high-performance, scalable proxy that runs in front of an OpenAPI or gRPC API backend and provides API management\n features such as authentication, monitoring, and logging. See\n [About Endpoints](/endpoints/docs/openapi/about-cloud-endpoints)\n and\n [Endpoints: Architectural overview](/endpoints/docs/openapi/architecture-overview)\n for more information.\n\n: ESPv2 supports version 2 of the\n [OpenAPI Specification](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md) and [gRPC](http://www.grpc.io) Specifications.\n\nFirebase authentication\n\n: Google's authentication service that supports end user sign-in for client\n applications by using credentials from popular federated identity providers\n such as Google, Facebook, or Twitter. See\n [Firebase authentication](https://firebase.google.com/docs/auth/)\n for more information.\n\nGoogle ID token\n\n: A JSON Web Token (JWT) that contains the [OpenID\n Connect](https://developers.google.com/identity/protocols/OpenIDConnect)\n fields needed to identify a Google user account or service account, and that\n is signed by Google's authentication service, `https://accounts.google.com`.\n\ngRPC\n\n: A high performance, open source universal RPC framework developed by Google.\n In gRPC, a client application can directly call methods on a server application\n on a different machine as if it was a local object. See\n [Cloud Endpoints for gRPC APIs](/endpoints/docs/grpc/about-grpc)\n for information on using gRPC with Endpoints and the\n [gRPC](http://www.grpc.io)\n website for general information.\n\nJWT\n\n: JSON Web Token is an open standard access token format for use in HTTP\n Authorization headers and URI query parameters. See\n [Introduction to JSON Web Tokens](https://jwt.io/introduction/) for general\n information.\n\nkubectl\n\n: A command-line interface for running commands against Kubernetes clusters. You\n use `kubectl` when deploying an API for Endpoints on a Kubernetes\n or\n [Google Kubernetes Engine](/kubernetes-engine/docs/clusters)\n cluster.\n See [Overview of `kubectl`](https://kubernetes.io/docs/user-guide/kubectl-overview/)\n for more information.\n\nKubernetes\n\n: Open source software that lets you automate the deployment, management,\n and scaling of containerized applications across clusters of hosts.\n See [Kubernetes](https://kubernetes.io/) for more information.\n\nNGINX\n\n: An open source, high-performance HTTP server and service proxy that\n ESP is based on. See the\n [NGINX Wiki](https://www.nginx.com/resources/wiki/)\n for more information. For information on ESP, see\n [About Cloud Endpoints](/endpoints/docs/openapi/about-cloud-endpoints)\n and [Endpoints: Architectural overview](/endpoints/docs/openapi/architecture-overview).\n\nOpenAPI\n\n: The [Open API Initiative](http://openapis.org) is an industry-wide effort to\n standardize the description of REST APIs. APIs that are described with the\n [OpenAPI Specification](https://github.com/OAI/OpenAPI-Specification) (formerly\n the [Swagger Specification](http://swagger.io)) can be supported with common\n tools that create documentation, automate testing, and generate code for clients\n and servers. See\n [OpenAPI overview](/endpoints/docs/openapi/openapi-overview)\n for more information.\n\nOpenAPI document\n\n: A configuration file in either YAML or JSON format that you use to describe\n your API.\n\nsurface\n\n: The public interface of an API. An API's surface consists of the methods\n as well as the parameters and return types used in the methods."]]
