Expose OAuth Endpoints

Zapier Zapier gives me a list of things that I will need to configure for the zapier app to be able to communicate with my app vi OAuth. I think this is a good way to call out the routes I need to build. Authentication Type OAuth V2 w/refresh Client ID AKA “Consumer Key” or “API Key” zapier Client Secret AKA “Consumer Secret” or “API Secret” asdjhalsgdhgaposdigu (some string) Authorization URL For now I will list what I see the consent app presenting.

Run Hydra on a Mac for Testing

These are the steps (both up and down) to get get the Hydra Consent Flow example working locally on a Mac. Infrastructure Create Database Up echo "create database hydra" | mysql -uroot -proot Down echo "drop database hydra" | mysql -uroot -proot Export Stuff Up export DATABASE_URL=mysql://root:root@tcp(docker.for.mac.localhost:3306)/hydra?parseTime=true export SYSTEM_SECRET=yJFLIU44byGmmKLwJHvrIamNknAmSQR27C Down Nothing. Migrations Up docker run -it --rm \ oryd/hydra:v0.10.10 \ migrate sql $DATABASE_URL Down Nothing. Run Hydra Container Up docker run -d \ --name ory-hydra-example--hydra \ --network hydraguide \ -p 9000:4444 \ -e SYSTEM_SECRET=$SYSTEM_SECRET \ -e DATABASE_URL=$DATABASE_URL \ -e ISSUER=https://localhost:9000/ \ -e CONSENT_URL=http://localhost:9020/consent \ -e FORCE_ROOT_CLIENT_CREDENTIALS=admin:demo-password \ oryd/hydra:v0.

Zapier and the OAuth2.0 Mountain

Background Zapier is effectively a task runner. Integrating with them would put FlowMojo in a marketplace of other productivity applications. I think it will really fuel adoption. To get in the door with Zapier, I need to become an OAuth provider. You can create a Zapier Application for your WebApp and give that to Zapier. Then, your users that also have Zapier accounts can go to Zapier and choose to make a ‘Zap’ with the Zapier Application you created.