apigee/api-platform-samples

Working samples for the Apigee API Platform

Apigee Edge sample API proxies

• Audience
• Intro
• Before you begin
• Using the sample proxies
• Setting up
• Deploying a sample proxy
• Invoking a sample proxy
• Modifying a sample proxy
• Bulk deployment
• What else is here?
• Ask questions on the Apigee Community
• Apigee Edge documentation

Audience

You are an Apigee Edge API proxy developer, or you would like to learn about developing APIs that run on Apigee Edge. At a minimum, we assume you're familiar with Apigee Edge and how to create simple API proxies. To learn more, we recommend this getting-started tutorial.

These samples were built to work with Apigee EDGE. The current version of Apigee is known as Apigee X. Most of these samples will work with Apigee X, but the deployment scripts will not, and the instructions for administrative actions (eg, sign up for an account at apigee.com) will not work either. In those cases, you will need to substitute the appropriate actions relating to Apigee X!

Bear with us, please!

Intro

This repository contains a collection of sample API proxies that you can deploy and run on Apigee Edge.

The samples provide a jump-start for developers who wish to design and create Apigee Edge API proxies. Each proxy sample includes a deploy.sh and invoke.sh script. These scripts let you easily deploy and run the proxies.

In addition, you'll find:

• API proxy schemas that you can reference
• Tools for deploying proxies to Apigee Edge
• Cookbook samples, which illustrate specific use cases

Before you begin

1. If you don't have one, you'll need to obtain an Apigee account. Sign up for a free trial account.

2. You also need to have Python on your system, to use the deployment tool.

3. Download this project from GitHub to your system.

Using the sample proxies

Most developers begin by identifying an interesting sample based on a specific use case or need. You'll find the samples in the ./api-platform-samples/sample-proxies folder. The Apigee doc site also has a handy samples overview page.

For example, if you're interested in doing XML to JSON transformations, check out api-platform-samples/sample-proxies/xmltojson.

Setting up

Set up your deployment environment.

1. Open the file ./api-platform-samples/setup/setenv.sh in a text editor.|

2. Edit the file with your Apigee Edge account settings and save it. For example:

   org=myorg
   [email protected]
   url="https://api.enterprise.apigee.com"
   env=test
   api_domain="apigee.net"
   

Deploying a sample proxy

We make it easy:

1. Be sure you've updated ./api-platform-samples/setup/setenv.sh as explained previously.

2. cd to one of the sample proxy folders in ./api-platform-samples/sample-proxies.

3. Be sure you can execute the deploy.sh script. For example:

   chmod 744 deploy.sh

4. Execute the deploy script.

   ./deploy.sh

Note: If you already have the proxy deployed, the script will undeploy it first, then redeploy a new revision.

Output like this means a successful deployment:

    Imported new proxy version 3
    Undeploying revision 2 in same environment and path:
    Environment: test
      Revision: 3 BasePath = /
      State: error
    If 'State: deployed', then your API Proxy is ready to be invoked.
    Run 'invoke.sh'

Invoking a sample proxy

We make this easy too! Each sample API proxy directory contains a script, invoke.sh, that issues a sample HTTP request to the API. Deploy the proxy and follow these steps:

1. Be sure you've updated ./api-platform-samples/setup/setenv.sh as explained previously.

2. cd to one of the sample proxy folders in ./api-platform-samples/sample-proxies.

3. Be sure you can execute the invoke.sh script. For example:

   chmod 744 invoke.sh

4. Open the invoke.sh file and take a look at the code. Basically, the invoke scripts make curl requests to Apigee Edge. In some cases, invoke.sh performs other setup tasks, such as creating products, developer apps, and other entities on Edge.

   Tip: Always open invoke.sh and look through it before executing it -- this will give you valuable insight into how the API proxy is called and any setup steps that are performed.

5. Execute the invoke.sh script.

   ./invoke.sh

Modifying a sample proxy

Feel free to modify and build upon the sample proxies. You can make changes in the Edge management UI or by editing the proxy XML files locally and redeploying. Whichever approach is comfortable for you.

Tip: If you use Sublime for local development, check out the Sweetlime project on GitHub. Sweetlime is a Sublime plugin for developing API proxies for Apigee Edge.

Simply redeploy the proxies for changes to take effect.

Bulk deployment

You can deploy all of the samples to your organization at once using a simple setup script provided in this distribution.

1. Update the file /setup/setenv.sh with settings for your Apigee account.

2. Run deploy_all.sh

   Note: This step deploys all API products, developers, and apps needed for samples that use OAuth.

What else is here?

In addition to the sample proxies, this project includes the following:

/learn-edge

The Learn Edge series is a hands-on learning experience for beginning Edge developers. Each example is designed to be quick and easy to do, teaches a core Apigee Edge concept or technique, and follows three basic steps:

1. Deploy it.
2. Run it.
3. Trace it.

The best way to learn Apigee Edge is by doing!

/schemas

XML schemas that you can use as a reference when working with policies, API proxy configuration, API products, apps, and developers.

/setup

Simple scripts to help you deploy the sample API proxies and profiles that they rely on, including API products, developers, and apps.

Set you Apigee API Platform account settings in setenv.sh (Register for a free Apigee account)

To deploy a single sample, run deploy.sh proxyName, where proxyName is the name of the directory under /sample-proxies that contains the proxy you want to deploy.

To deploy all samples and API products, run deploy_all.sh

/tools

• deploy.py: Uploads an API proxy to an organization on the Apigee Edge API Services platform and then deploys it to the environment specified.

• proxy_gen.sh: A simple script that interacts with the API Services platform to locally generate an API proxy scaffold.

• /org-snapshot: A configurable tool that retrieves organization settings from the API Services platform by using management server API calls.

Ask questions on the Apigee Community

Apigee Edge documentation

The Apigee Edge docs are here.

---

Copyright © 2018 Apigee Corporation, 2024 Google LLC

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

api-platform-samples's Issues

invoke.sh in all the sample has issue while hitting from curl.

Hi, I have successfully configured the setup, provisioned the sample all but whenever I run ./invoke.sh from any environment the curl throw an error.

`curl http://itravindrasingh-eval-test.https://itravindrasingh-eval-test.apigee.net/v1/learn-edge/json?apikey=dLKTcVdGoSqVnD3JsBpBuw75F091Syy3

Response:
curl: (6) Could not resolve host: itravindrasingh-eval-test.https`

Because in invoke.sh file the $org-$env.$api_domain are getting concatenation which seems incorrect or maybe it is apigeetool configuration issue with the console.

Source for Kerberos Mediation example?

Would it be possible for the Java source for the Kerberos Mediation example proxy to be posted as well? Right now, only the JAR file is available. We'd like to be able to investigate it to ensure it meets our security requirements before deploying it.

Validator module version is set to its latest in dependencies

As it seems like 'validator' module version has been set to its latest in dependencies and as a result validation logic written in login.js and registration.js` files are not functioning now:

api-proxy: login-app
package.json

  "name": "oauth-login-consent",
  "version": "1.0.1",
  "description": "Lightweight web app to support OAuth2 authorization_code grant login/consent flow.",
  "main": "app.js",
  "repository": "https://github.com/apigee/api-platform-samples.git",
  "dependencies": {
    "apigee-access": "^1.3.0",
    "body-parser": "^1.9.2",
    "cookie-parser": "^1.3.3",
    "ejs-locals": "^1.0.2",
    "express": "^4.10.2",
    "express-session": "^1.9.1",
    "less-middleware": "^0.1.12",
    "serve-favicon": "^2.1.6",
    "validator": ">2.0.0"
  },
  "devDependencies": {},
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "Apigee Corporation",
  "license": "MIT"
}

Error:

TypeError: org.mozilla.javascript.Undefined@0 is not a function, it is undefined.
    at /organization/environment/api/routes/registration.js:117:0
    at /organization/environment/api/routes/registration.js:24:0
    at handle (/organization/environment/api/node_modules/express/lib/router/layer.js:95:0)
    at next (/organization/environment/api/node_modules/express/lib/router/route.js:137:0)
    at dispatch (/organization/environment/api/node_modules/express/lib/router/route.js:112:0)
    at handle (/organization/environment/api/node_modules/express/lib/router/layer.js:95:0)
    at /organization/environment/api/node_modules/express/lib/router/index.js:281:0
    at process_params (/organization/environment/api/node_modules/express/lib/router/index.js:335:0)
    at next (/organization/environment/api/node_modules/express/lib/router/index.js:275:0)
    at /organization/environment/api/node_modules/body-parser/lib/read.js:130:0
    at invokeCallback (/organization/environment/api/node_modules/raw-body/index.js:224:0)
    at done (/organization/environment/api/node_modules/raw-body/index.js:213:0)
    at onEnd (/organization/environment/api/node_modules/raw-body/index.js:273:0)
    at emit (events.js:92:0)
    at _stream_readable.js:943:0
    at _tickDomainCallback (trireme.js:491:0)
    at _tickFromSpinner (trireme.js:422:0)

HTTPTargetConnection not part of TargetEndpoint within the configuration_schemas.xsd

I've created a TargetEndpoint and used the configuration_schemas.xsd. My IDE (IntelliJ) complains that HTTPTargetConnection is not allowed and IMO the reason is, that its missing in the xsd.

The same is true for the HTTPProxyConnection in the ProxyEndpoint.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TargetEndpoint
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/apigee/api-platform-samples/master/schemas/configuration/configuration_schemas.xsd"
  name="default">
  <PreFlow name="PreFlow">
    <Request>
      <Step>
        <Name>am-custompathprefix-default</Name>
      </Step>
    </Request>
    <Response/>
  </PreFlow>
  <Flows>
    <Flow name="add-user-path">
      <Description>Adds /user as path prefix to certain endpoints</Description>
      <Request>
        <Step>
          <Name>am-custompathprefix-user</Name>
        </Step>
      </Request>
      <Response/>
    </Flow>
  </Flows>
  <PostFlow name="PostFlow">
    <Request/>
    <Response/>
  </PostFlow>
  <HTTPTargetConnection>
    <LoadBalancer>
      <Server name="test"/>
    </LoadBalancer>
    <Path>{customPathPrefix}</Path>
  </HTTPTargetConnection>
</TargetEndpoint>

How do I get the 'oauth-advanced' sample to work with SSO?

Our enterprise has SSO set up for logging into Apigee. As a result, I can no longer deploy this sample successfully. This makes sense as the sample is following Basic Authentication. Could anyone give guidance on how to switch from Basic Authentication and use SSO Bearer Tokens instead? I tried altering a few files, but unfortunately continue to receive the following error:

Error: Get API info returned status 401

Any help would be greatly appreciated!

Proxy twitter-mobile-timeline not working due to Twitter API deprecation

Got the following message when running the invoke.sh script.

{"errors":[{"message":"The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.","code":64}]}

Error while deploying advanced-api-services proxy

Import failed to /v1/organizations/nielsendevjam/apis?action=import&name=advanced-api-services with status 400:
{
"code" : "messaging.config.beans.InvalidBundle",
"message" : "Bundle is invalid. Unable to read/find APIProxy contents",
"contexts" : [ ]
}

unable to add user defined targetEndPoints with proxy_gen.sh

While creating proxy it is not taking proxy and target end points

Tried with both content type JSON and XML

JSON:- curl -H "Content-type:application/json" -X POST -d '{"name" : "Products", "targetEndpoints":[{"targetEndpoint" : {"targetEndpoint" : "BOD-Products-Endpoint"} }] }' https://api.enterprise.apigee.com/v1/o/$org/apis -u $username:$password

XML:- curl -H "Content-type:application/xml" -X POST -d "<APIProxy name="Products">defaultBOD-Product-Endpointfalse" https://api.enterprise.apigee.com/v1/o/$org/apis -u $username:$password

deployment failure on simplest-proxy

Hi, I am trying to deploy the simplest-proxy and getting below error while running ./deploy.sh. Please find the attach screenshot if my explanation is unclear

../../setup/userconf.sh: line 13: $'\r': command not found
../../setup/userconf.sh: line 19: syntax error near unexpected token $'\r'' './../setup/userconf.sh: line 19: _get_var()

Important *not* to include client credentials but then we do

Could you please clarify what below comment means? It states "its important not to include it" but then it is included. Also can you please expand on how exactly a caller might gain access tokens from that endpoint without supplying consumer key and secret? I am a bit scared to install this after reading the comments! Many thanks.

api-platform-samples/default-proxies/oauth/apiproxy/policies/GenerateAccessTokenClient.xml

Lines 7 to 10 in a0ececb

	<!-- This part is very important: most real OAuth 2.0 apps will want to use other
	grant types. In this case it is important to NOT include the "client_credentials"
	type because it allows a client to get access to a token with no user authentication -->
	<GrantType>client_credentials</GrantType>

ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:590)

From last Friday till today, we have been facing an issue in the deployments of proxies. Sometimes it works but most of the time we see SSL error (attached code below).

Writing ../build/test/testcase-update-user-attributes-by-region.sh to test/testcase-update-user-attributes-by-region.sh 
Writing ../build/test/testcase-update-user-attributes.sh to test/testcase-update-user-attributes.sh 
Traceback (most recent call last): 
File "deploy.py", line 204, in <module> 
resp = httpCall('POST', uri, hdrs, body) 
File "deploy.py", line 29, in httpCall 
conn.request(verb, uri, body, hdrs) 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 1053, in request 
self._send_request(method, url, body, headers) 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 1093, in _send_request 
self.endheaders(body) 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 1049, in endheaders 
self._send_output(message_body) 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 893, in _send_output 
self.send(msg) 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 855, in send 
self.connect() 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 1274, in connect 
server_hostname=server_hostname) 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 352, in wrap_socket 
_context=self) 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 579, in __init__ 
self.do_handshake() 
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 808, in do_handshake 
self._sslobj.do_handshake() 
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:590) 
If 'State: deployed', then your API Proxy is ready to be invoked. 

Many of our colleagues are facing this issue, we tried using mac os and linux OS.

Please have a look urgently, as we are unable to deploy proxy on time.

authentication error

I have cloned git repository into my Ubuntu machine but I am getting following terminal output after running "sh deploy.sh". It seems shell script is not prompting me for any password and generate following error.

"Be sure to populate values in setenv.sh in this directory before running this script.
Using in .
Enter your password for the Apigee Enterprise organization , followed by [ENTER]:
deploy_all.sh: 13: read: Illegal option -s
Verifying credentials...
Authentication failed!
Please re-run the script using the right username/password."

Any suggestion ? Thanks!

Error at running /api-platform-samples/sample-proxies/oauth-advanced/login-app/deploy.sh

When I try to run ./deploy.sh in ./api-platform-samples/sample-proxies/oauth-advanced/login-app
it gives following error
Error: Error: NPM install failed with status code 504

But when look at the server I can see the login-app has been created. What is the reason for that?

Implicit grant flow is not secure

This is the implicit grant flow:

1.- Authorization Request:

https://$org-$env.$api_domain/oauth/authorize?response_type=token&client_id=$consumerkey&redirect_uri=$callback&scope=READ&state=foobar

2.- The API Provider Login Page Redirection URI:

https://$org-$env.$api_domain/oauth/samplelogingpage?client_id={request.queryparam.client_id}&response_type={request.queryparam.response_type}&scope={request.queryparam.scope}

3.- On successful authentication, login application invokes this url and it returns the AccessToken to the App

https://$org-$env.$api_domain/oauth/token?client_id=$consumerkey&response_type=code&app_enduser={userId}

In my opinion this is insecure, anybody knowing the app_enduser and the client_id could call the token endpoint and get a bearer token, without the user having authenticated at all in the login page, because the token endpoint is not protected at all.

Imagine the scenario where we would be saving that app_enduser as custom attribute linked to the bearer token and then we have some other endpoint where we verify the access token and fetch that app_enduser from the token and pass it over to a target endpoint. Any malicious user could be actually impersonating the actual app end user.

is it ok to use pull request to add repos?

I'm planning to open source some of my code on Apigee like a shared flow that takes the request payload and assign it as query string. and another project to camel case the payload or snake case it.

is it ok to add those sample in Apigee's space? as I don't have the target audience I want to share this code with.

thank you.
Lama.

Error when deploying postman-oauth

}Writing images/postman-oauth.png to ./postman-oauth.png
Import failed to /v1/organizations/{org_name}/apis?action=import&name=images with status 400:
{
"code" : "messaging.config.beans.InvalidBundle",
"message" : "Bundle is invalid. Unable to read/find APIProxy contents",
"contexts" : [ ]
}

Missing json_threat_protection.xsd

There's a reference to json_threat_protection.xsd in policies/all.xsd. The referenced .xsd is missing from the "policies" directory.

oath-advanced sample registration fails with certain password values

If you register with password like 566559aa, the registration fails with a stack trace. However, if you use apigee123, the registration succeeds as expected.

The Oauth Advanced sample should use a real consent app

Currently the "consent app" is HTML that is rendered through RaiseFault or AssignMessage or something like that.

Instead the consent app should be a self-standing app, perhaps implemented in nodejs and deployed in a distinct API proxy.

Need REST API url code for fetching the zip file uploaded on GIT HUB

Hello,

I have a file loaded on Master branch with MyZipFile.zip, what would be REST API URL to fetch such file.

Regards
Harshad Dani

Incorrect code in com.apigee.SimpleNonBlockingExecutionReturnError

...
        } catch (Exception ex) {
            ExecutionResult executionResult = new ExecutionResult(false, ExecutionResult.Action.ABORT);
...
            return new ExecutionResult(false, ExecutionResult.Action.ABORT);
        }
...

It should be Action.ABORT.

Validation error in jwt.xsd

https://github.com/apigee/api-platform-samples/blob/master/schemas/policy/jwt.xsd

contains a typo:

org.xml.sax.SAXParseException; 
systemId: file://.../api-platform-samples/schemas/policy/jwt.xsd; 
lineNumber: 152; columnNumber: 5; 
The element type "xs:schema" must be terminated by the matching end-tag "</xs:schema>".

Checking line 152, looks like there is an additional `</xs:complexType> line that should be removed.

....
151: </xs:complexType>
152: </xs:complexType>
153: <xs:complexType name="decodeJWTStepDefinitionBean">
...

Error while deploying images proxy

Import failed to /v1/organizations/nielsendevjam/apis?action=import&name=images with status 400:
{
"code" : "messaging.config.beans.InvalidBundle",
"message" : "Bundle is invalid. Unable to read/find APIProxy contents",
"contexts" : [ ]
}

Problem with oauth-login-app - potentially insecure flow

It is possible that I'm not getting something right, but I think there is an issue with the suggested "web server flow" described in the oauth-login-app sample proxy:
https://github.com/apigee/api-platform-samples/tree/89aaaf327153f2bd1ba357eb58c39a6601d4fc2d/sample-proxies/oauth-login-app

First, the client app redirects the browser to the /authorize endpoint of the proxy. That endpoint redirects the browser to an external login application. That application authenticates the user and redirects the browser to the /authorizationcode endpoint of the proxy passing the user ID as a GET parameter.

Now I'm missing some kind of validation that the authentication process really happened. It seems that the client app may redirect the browser to the /authorizationcode endpoint directly passing any user ID as a GET parameter. The server should not trust anything that passes through the browser, as it can be modified.

Unable to connect with SSO enabled user

Unable to deploy oauth-advanced proxy

Import failed to /v1/organizations/nielsendevjam/apis?action=import&name=oauth-advanced with status 400:
{
"code" : "messaging.config.beans.InvalidBundle",
"message" : "Bundle is invalid. Unable to read/find APIProxy contents",
"contexts" : [ ]
}

Error while doing manual install

LM0002702:~ vipul.thakur$ node --version
v17.0.1
LM0002702:~ vipul.thakur$ npm --version
8.3.0
LM0002702:~ vipul.thakur$ yo oauth-auth-code-grant-sample
(node:4213) [DEP0128] DeprecationWarning: Invalid 'main' field in '/usr/local/lib/node_modules/generator-oauth-auth-code-grant-sample/node_modules/isbinaryfile/package.json' of './lib/panino.js'. Please either fix that or report it to the module author
(Use node --trace-deprecation ... to show where the warning was created)
Error oauth-auth-code-grant-sample

primordials is not defined
LM0002702:~ vipul.thakur$

async callout sample does not work

http://weather.yahooapis.com/forecastrss?w=... is no longer available. Please consider an update with the YQL service instead. Thanks. https://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20weather.forecast%20where%20woeid%20in%20(select%20woeid%20from%20geo.places(1)%20where%20text%3D%22nome%2C%20ak%22)&format=json&env=store%3A%2F%2Fdatatables.org%2Falltableswithkeys

getting http version not supported error in nodejs_baas_cookbook example

when making GET request to api proxy, it gives the http 505 version not supported

I think step No. 2 should be corrected.

The xml file name to create cache in environment should be oauth-token-cache.xml, that's what available in this sample project.
Also, the curl command should reflect the same.

Thanks,
Rajesh

Error in implementing 3 legged oauth in Windows 10 OS

I tried to implement Authorization code grant type example in Windows 10 OS using the sample-proxies/oauh-advanced code available in Git. I have deployed the sample as specified [https://github.com/apigee/api-platform-samples/tree/master/sample-proxies/oauth-advanced] but when i used the command yo oauth-auth-code-grant-sample it showed

'.' is not recognized as an internal or external command, operable program or batch file. The system cannot find the path specified.

in the screen. When I tried clicking the button at http://myorg-myenv.apigee.net/web I did not get any response. When I went through the proxy I identified that developer app, product and developer was not created in my organization and so it was not able to fetch my client id.

Since I am trying to implement it in Windows 10, can you please help to make it working in windows also, Even though it works fine with Mac or Linux OS.

Error while deploying 3 legged OAuth1a flow.

Import failed to /v1/organizations/nielsendevjam/apis?action=import&name=oauth10a-3legged with status 400:
{
"code" : "rest.ValidationFailure",
"message" : "Error occurred while validation of bean GenerateVerifier.xml. Reason: - Schema validation failed. Cause : unexpected element (uri:"", local:"Path"). Expected elements are <{}Headers>,<{}QueryParams>,<{}Payload>,<{}FormParams>. Line number : 4. Column number : 9. File name : GenerateVerifier.xml..",
"contexts" : [ ]
}

Security Policy violation Binary Artifacts

This issue was automatically created by Allstar.

Security Policy Violation
Project is out of compliance with Binary Artifacts policy: binaries present in source code

Rule Description
Binary Artifacts are an increased security risk in your repository. Binary artifacts cannot be reviewed, allowing the introduction of possibly obsolete or maliciously subverted executables. For more information see the Security Scorecards Documentation for Binary Artifacts.

Remediation Steps
To remediate, remove the generated executable artifacts from the repository.

First 10 Artifacts Found

• doc-samples/java-cookbook/apiproxy/resources/java/ResponseUppercase.jar
• doc-samples/java-cookbook/lib/expressions-1.0.0.jar
• doc-samples/java-cookbook/lib/message-flow-1.0.0.jar
• doc-samples/java-error/apiproxy/resources/java/edge-custom-policy-java-error.jar
• doc-samples/java-error/callout/target/classes/com/apigeesample/JavaError.class
• doc-samples/java-error/callout/target/edge-custom-policy-java-error.jar
• doc-samples/java-error/callout/target/lib/commons-lang-2.6.jar
• doc-samples/java-error/callout/target/lib/expressions-1.0.0.jar
• doc-samples/java-error/callout/target/lib/message-flow-1.0.0.jar
• doc-samples/java-error/lib/expressions-1.0.0.jar
• Run a Scorecards scan to see full list.

Additional Information
This policy is drawn from Security Scorecards, which is a tool that scores a project's adherence to security best practices. You may wish to run a Scorecards scan directly on this repository for more details.

---

Allstar has been installed on all Google managed GitHub orgs. Policies are gradually being rolled out and enforced by the GOSST and OSPO teams. Learn more at http://go/allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

weatheroauthauthcode/oauth/accesstoken request fails

when running invoke script getting "invalid request" reply due to:
Error :"Required param : grant_type" or
Error :"Invalid redirect_uri"

grant_type was set to authorization_code properly by the invoke script
and also redirect_url seems to be correct

java callout apiproxy is missing jar file in resources/java/

java-callout proxy is missing the jar in resources/java folder, is it expected for the user to compile it and put it in that folder?

Replace tools/deploy.py with directions for apigeetool

https://github.com/apigee/api-platform-tools

ERROR in /learn-edge/provisioning with ./setup.sh

error : ./setup.sh: 4: ./setup.sh: source: not found
line 4 of setup script: source ../../setup/userconf.sh || exit 1
userconf.sh does exist with in setup

. how could i go about fixing this?

Sample-proxies: api-key: Hardcoded api proxy

In file api-platform-samples/sample-proxies/apikey/invoke.sh there are some hard-coded things like

key=`curl -u $username:$password $url/v1/o/$org/developers/[email protected]/apps/thomas-app 2>/dev/null \
     | grep consumerKey | awk -F '\"' '{ print $4 }'`

JavaScript mashup doc sample does not work

https://github.com/apigee/api-platform-samples/tree/master/doc-samples/javascript-mashup-cookbook
Running 'sh invoke.sh' results in the following error:
{"error":TypeError: Cannot read property "status" from undefined}

Hint: the google maps API changed. 1) needs API key and 2) address is a required query param. Thanks.

oauth-advanced sample. I got an error after I clicked login button.

Hi, I'm looking into how to fix my issue. Can you help me?

Summary

I tried OAuth tutorial "oauth-advanced sample". But I got an error after I clicked login button.

https://github.com/apigee/api-platform-samples/tree/master/sample-proxies/oauth-advanced

Steps to Reproduce

$ mkdir oauth-sample
$ cd oauth-sample
$ npm install -g yo
$ npm install -g apigeetool
$ npm install generator-oauth-auth-code-grant-sample -g 
$ yo oauth-auth-code-grant-sample 
// Followed the prompts
// Open http://myorg-test.apigee.net/web 
// Click "Login with Apigee Example Auth" Button
// Enter Email address and Password. Click Login Button.

Expected Results

Redirect to the redirect url.

Actual Results

The following error occurred.

TypeError: org.mozilla.javascript.Undefined@11005018 is not a function, it is undefined.
    at /organization/environment/api/routes/login.js:162
    at /organization/environment/api/routes/login.js:60
    at handle (/organization/environment/api/node_modules/express/lib/router/layer.js:95)
    at next (/organization/environment/api/node_modules/express/lib/router/route.js:137)
    at dispatch (/organization/environment/api/node_modules/express/lib/router/route.js:112)
    at handle (/organization/environment/api/node_modules/express/lib/router/layer.js:95)
    at /organization/environment/api/node_modules/express/lib/router/index.js:281
    at process_params (/organization/environment/api/node_modules/express/lib/router/index.js:335)
    at next (/organization/environment/api/node_modules/express/lib/router/index.js:275)
    at /organization/environment/api/node_modules/body-parser/lib/read.js:130
    at invokeCallback (/organization/environment/api/node_modules/express-http-proxy/node_modules/raw-body/index.js:224)
    at done (/organization/environment/api/node_modules/express-http-proxy/node_modules/raw-body/index.js:213)
    at onEnd (/organization/environment/api/node_modules/express-http-proxy/node_modules/raw-body/index.js:273)
    at emit (events.js:92)
    at _stream_readable.js:943
    at _tickDomainCallback (trireme.js:491)
    at _tickFromSpinner (trireme.js:422)

all_policies.xsd schema validation error with xmllint

Hello, was hoping to use the all_policies.xsd to validate all of the XML files in our source tree that contain Apigee API Policies.

However, I get lots of schema validation errors using xmllint

../api-platform-samples/schemas/policy/access_entity.xsd:5: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/access_entity.xsd:24: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/access_entity.xsd:37: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/assign_message.xsd:5: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/assign_message.xsd:23: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/assign_message.xsd:36: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/basic_authentication.xsd:7: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/basic_authentication.xsd:22: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/basic_authentication.xsd:35: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/cache.xsd:11: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/cache.xsd:38: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/cache.xsd:51: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/extract_variables.xsd:16: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/extract_variables.xsd:38: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/extract_variables.xsd:51: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/flow_callout.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/flow_callout.xsd:14: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/flow_callout.xsd:27: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/java_callout.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/java_callout.xsd:15: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/java_callout.xsd:28: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/java_script.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/java_script.xsd:16: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/java_script.xsd:29: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/json_threat_protection.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/json_threat_protection.xsd:19: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/json_threat_protection.xsd:32: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/json_to_xml.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/json_to_xml.xsd:16: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/json_to_xml.xsd:29: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/keyvaluemap-operations.xsd:5: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'Property' does already exist.
../api-platform-samples/schemas/policy/keyvaluemap-operations.xsd:6: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/keyvaluemap-operations.xsd:32: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/keyvaluemap-operations.xsd:45: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/keyvaluemap-operations.xsd:79: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'propertyBean' does already exist.
../api-platform-samples/schemas/policy/ldap.xsd:6: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'Password' does already exist.
../api-platform-samples/schemas/policy/ldap.xsd:9: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/ldap.xsd:21: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/ldap.xsd:34: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/message_logging.xsd:5: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/message_logging.xsd:19: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/message_logging.xsd:32: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/message_validation.xsd:6: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/message_validation.xsd:19: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/message_validation.xsd:32: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v1.xsd:9: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'Property' does already exist.
../api-platform-samples/schemas/policy/oauth_v1.xsd:13: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v1.xsd:28: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v1.xsd:41: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v1.xsd:42: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'propertyBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'GenerateErrorResponse' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:5: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'GenerateResponse' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:9: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'Property' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:12: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:67: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:80: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:81: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'customAttribute' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:90: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'generateErrorResponse' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:99: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'generateResponse' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:105: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'propertyBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:113: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'propertyExpiryBean' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:120: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'token' does already exist.
../api-platform-samples/schemas/policy/oauth_v2_verify_api_key.xsd:189: element simpleType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}simpleType': A global simple type definition 'format' does already exist.
../api-platform-samples/schemas/policy/quota_spike_ratelimit.xsd:7: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'Property' does already exist.
../api-platform-samples/schemas/policy/quota_spike_ratelimit.xsd:14: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/quota_spike_ratelimit.xsd:28: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/quota_spike_ratelimit.xsd:41: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/quota_spike_ratelimit.xsd:76: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'propertyBean' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:15: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:28: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:39: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'copyAction' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:53: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'nameAction' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:83: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'action' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:86: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'nameEntry' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:90: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'removeAction' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:97: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'addAction' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:104: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'nameValueAction' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:133: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'nameValueEntry' does already exist.
../api-platform-samples/schemas/policy/raise_fault.xsd:140: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'setAction' does already exist.
../api-platform-samples/schemas/policy/regular_expression_protection.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/regular_expression_protection.xsd:24: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/regular_expression_protection.xsd:37: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/regular_expression_protection.xsd:137: element simpleType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}simpleType': A global simple type definition 'type' does already exist.
../api-platform-samples/schemas/policy/saml.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'Namespace' does already exist.
../api-platform-samples/schemas/policy/saml.xsd:5: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'Property' does already exist.
../api-platform-samples/schemas/policy/saml.xsd:7: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/saml.xsd:16: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/saml.xsd:29: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/saml.xsd:43: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'namespace' does already exist.
../api-platform-samples/schemas/policy/saml.xsd:61: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'propertyBean' does already exist.
../api-platform-samples/schemas/policy/script.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/script.xsd:15: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/script.xsd:28: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:5: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:18: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:31: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:45: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'copyAction' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:59: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'nameAction' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:89: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'action' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:92: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'nameEntry' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:96: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'removeAction' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:103: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'addAction' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:110: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'nameValueAction' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:139: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'nameValueEntry' does already exist.
../api-platform-samples/schemas/policy/service_callout.xsd:146: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'setAction' does already exist.
../api-platform-samples/schemas/policy/statistics_collector.xsd:3: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'Property' does already exist.
../api-platform-samples/schemas/policy/statistics_collector.xsd:6: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/statistics_collector.xsd:14: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'propertyBean' does already exist.
../api-platform-samples/schemas/policy/statistics_collector.xsd:37: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/statistics_collector.xsd:50: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/xml_threat_protection.xsd:4: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/xml_threat_protection.xsd:18: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/xml_threat_protection.xsd:31: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/xml_to_json.xsd:5: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/xml_to_json.xsd:18: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/xml_to_json.xsd:31: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
../api-platform-samples/schemas/policy/xsl.xsd:6: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element': A global element declaration 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/xsl.xsd:19: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'stepDefinitionBean' does already exist.
../api-platform-samples/schemas/policy/xsl.xsd:32: element complexType: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}complexType': A global complex type definition 'leafBean' does already exist.
WXS schema ../api-platform-samples/schemas/all_policies.xsd failed to compile

Is the all_policies.xsd intended to be used like this?

Regarding OAuth Advanced code

Using all the prerequisite steps I was able to deploy all the APIs and the developer Apps and the product to my org..
But the login-app API was deployed partially and I was getting the error that the revision is deployed but the traffic can't flow.
And when I checked all the .ejs file I was seeing the errors like expected an identifier and instead saw '<' .
Can anyone please help me regarding this.

Error oauth-auth-code-grant-sample primordials is not defined

What's wrong?

npm install generator-oauth-auth-code-grant-sample-jrenelg -g
mkdir oauth-sample
cd oauth-sample
yo oauth-auth-code-grant-sample

Error oauth-auth-code-grant-sample

primordials is not defined

version info.

npm --version
6.14.16
node --version
v14.19.1
yo --version
4.3.0

incorrect link in documentation

In the intro:

Audience
You are an Apigee Edge API proxy developer, or you would like to learn about developing APIs that run on Apigee Edge. At a minimum, we assume you're familiar with Apigee Edge and how to create simple API proxies. To learn more, we recommend this getting-started tutorial.

The link to the getting-started tutorial gives a 404. I'm guessing it should go here instead:
https://docs.apigee.com/api-platform/get-started/get-started