Using OAuth applications
How to install pre-packed OAuth applications.
Last updated
Was this helpful?
v4.1
How to install pre-packed OAuth applications.
Last updated
Was this helpful?
Appmixer comes with set of prepared components (applications). Some of them use OAuth 1 (Twitter) authentication mechanism and some of them (Slack, Google) use OAuth 2 authentication mechanism.
If you try to use Slack component right after fresh Appmixer installation you will get an error Missing client ID.
In case of OAuth 1 application the error will be Missing consumer key. As described in the OAuth applications need these secrets. The reason we do not provide these secrets with Appmixer is simple. Part of the OAuth application registered in the third party service is the redirect URL which points to your server URL where the Appmixer backend API is running.
Therefore you need to create these OAuth application on your own. At the end of the process you will always get client ID and client Secret (OAuth 2). Appmixer expects these variables to be part of ENV. Here is the list of all ENV variables that you can set for the pre-packed applications if you want to start using them.
There is another ENV variable that is used for Oauth redirects. It is called GRIDD_URL.
By default, the GRIDD_URL will be set to http://localhost:2200. This is fine for local development. For most of the services, you can register http://localhost:2200 as a callback URL. In production, this has to point to your Appmixer's public API URL.
If you run the following command:
Another way would be replacing the variables directly in docker-compose.yml file.
Or you can set just the GRIDD_URL like this:
If APPMIXER_API_URL is not set, Appmixer will use value from GRIDD_URL.
Appmixer engine will print out values of these variables when starting so you can check they are set correctly:
It will set both the APPMIXER_API_URL and the GRIDD_URL to the .
