How to configure your Confluence as an application in Odoo
1) Applications menu
Application list
Application form
Generate own id and secret
The buttons are only available during editing.
Only system administrators can perform this operation.
General settings
General application configuration
| Name | Description | Notes |
|---|---|---|
| Logo | The logo of the application | |
| Name | The name of the application | For audit purposes you might need to keep a record of issued authorization codes |
| Client ID | The client id of the Confluence application Must be used when stting up the connection in Confluence: READ MORE HERE | Unique identifier of the Confluence application in this Odoo instance. The Confluence application will use this when |
| Client Secret | The client secret of the Confluence application Must be used when stting up the connection in Confluence: READ MORE HERE | |
| Own ID | The id of the Odoo instance | Not used currently |
| Own Secret | The secret of the Odoo instance | Not used currently |
| Description | Additional information about the application |
Models tab
List of Odoo models availble for the Confluence application when using the macro to select the Odoo record, see HERE
Not all models make sense to a user in Confluence, so it can be useful to limit what can be searched in Confluence.
There are three ways to limit the list of models:
- None: there is no limit, all models are available
- Blacklist: all models except for the listed models are available
- Whitelist: only the listed models are available
The actually available models depend on the Odoo user's permisssion!
This list only controlls what is made available for the application for listing purposes!
Users can still perform operations in models related to the listed models if they have the appropriate permissions in Odoo!
| Name | Description | Notes |
|---|---|---|
| Model | The technical name of the model in Odoo | |
| Model Description | The human readable name of the model in Odoo | This is what users see when using the macro |
URIs tab
List of valid, available callback URIs for the application defining the callback endpoints of the remote application
| Name | Description | Notes |
|---|---|---|
| URI | The full path of the URI | The uri is verified as a string when an endpoint is called from Confluence. Use https in the URI to enforce secure connection |
| Description | Additional information | Optional details about the URI |
Settings tab
Perform various settings for the applications
| Name | Description | Notes |
|---|---|---|
| OAuth 2.0 | ||
| Authorization Code Expiry | When should the authorization code expire (expressed in seconds) Default: 600 | There are various practices, pick what suits you needs |
| Authorization Code Retain | How long should the system keep track of issued authorization codes (expressed in days) Default: 0 | For audit purposes you might need to keep a record of issued authorization codes |
| Access Token Expiry | When should the access token expire (expressed in seconds) Default: 3600 | RFC sample defines 3600s, which is the default, but you can set what you want |
| Refresh Token Expiry | When should the refresh token expire (expressed in seconds) Default: 0 (never expires) | Some like it never to expire, some like it expire after some time, set what you need |