This sample shows how use the OAuth 1.0a - 3 legged flow
It contains the following policies:
- An OAuth 1.0 GenerateRequestToken Policy to generate the request token, called the RequestToken Endpoint. This request token is required to generate verifier and the access token.
- An GenerateVerifier Policy (A ServiceCallout Policy) to create the externally passed verifier code, associating it to the request token generated in the above step.
- An OAuth 1.0 GenerateAccessToken Policy to generate an access token using the request token and its verifier, called the AccessToken Endpoint.
- An OAuth 1.0 VerifyAccessToken Policy, to validate the OAuth 1.0 AccessToken and its signature, before requesting for the protected resource.
- The username and password that you use to login to enterprise.apigee.com.
- The name of the organization in which you have an account. Login to enterprise.apigee.com and check account settings.
/setup/setenv.shwith your environment details
Configure API products, developers, and apps in your organization
Import and deploy sample project
To deploy, run
$ sh deploy.sh
To test, run
$ sh invoke.sh
For assistance, please use StackOverflow and add the tag "apigee".
Copyright © 2014 Apigee Corporation
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
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.