credentials are entered in the src/main/resources application*.properties files application-dev.properties is not checked in and must be generated for local development, see below
server.port=3500
spring.devtools.restart.enabled=true
spring.devtools.livereload.enabled=true
google.client.client-id=zzzzzzzzzz
google.client.client-secret=zzzzzzz
google.client.access-token-uri=https://www.googleapis.com/oauth2/v3/token
google.client.user-authorization-uri=https://accounts.google.com/o/oauth2/auth
google.client.client-authentication-scheme=query
google.client.scope=profile,email,https://www.googleapis.com/auth/calendar
google.resource.user-info-uri=https://www.googleapis.com/oauth2/v2/userinfo
google.resource.prefer-token-info=false
In production the client-id and the client-secret will come in via system properties provided by heroku, along with server.port. The port setting is provided by heroku and gets to this app via command line overrides in the Procfile.
heroku login
heroku deploy:jar target/google-cal-api-0.0.1-SNAPSHOT.jar --app google-cal-api
URL: http://google-cal-api.herokuapp.com/ (application is not deployed at this time)
Api Manager console.
http://localhost:3500/login/google
http://localhost:3500/
http://google-cal-api.herokuapp.com/login/google
https://google-cal-api.herokuapp.com/login/google