Skip to content

This is a code to deploy sharedflows which are used when your backend is secured by GCP OAuth (via Service Account) or IAP (via Service Account).

Notifications You must be signed in to change notification settings

thomasdesplaces/apigee_get_oauth_gcp_token

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

APIGEE - SECURE GCP BACKEND WITH OAUTH OR IAP

Apigee

alt version alt production alt docker

This is a code to deploy sharedflows which are used when your backend is secured by GCP OAuth (via Service Account) or IAP (via Service Account).

Prerequisite

  • A GCP Project with, for example, an App Engine.
  • A service Account with good rights to call your App Engine and his JSON Key.
  • An Apigee account with an organization (free or paid).
  • Maven or apigeetools install on your computer to deploy the sharedflow.
  • Maven install on local computer.

Installation

  • Create a new encrypted Key Value Map on your Apigee Organisation which name is gcp-service-account-credentials.
  • In this KVM, add a new key/value pair with a key name credentials and for value the JSON Key value.
  • Update cache files with good timeout in seconds for each environment :

Deploy

This repository contain the maven configuration to deploy this sharedflow on 3 environments : dev, test or prd.

How to use it :

cd sharedflows/gcp-token-oauth
mvn install -P=dev -Dusername=XXXX -Dpassword=YYYY -Dorganization=ZZZZ

About

This is a code to deploy sharedflows which are used when your backend is secured by GCP OAuth (via Service Account) or IAP (via Service Account).

Topics

Resources

Stars

Watchers

Forks