Info |
---|
This section offers information for Odoo users on how to configure their Confluence as an application in Odoo. |
Panel | ||
---|---|---|
| ||
|
Applications menu
Application list
Info |
---|
The list of active applications is displayed by default. |
Note |
---|
Inactive applications can be opened using seach filter and search for field Active with value is false |
Application configuration
Tip |
---|
Only users with Oregional Odoo App administrator permission can make settings for applications |
General settings
Info |
---|
General application configuration |
Name | Description | Notes |
---|---|---|
Logo | The logo of the application | |
Name | The name of the application | The name of the Confluence instance as recognized by the users |
Client ID | The client id of the Confluence application Must be used when setting up the connection in Confluence, more information: Odoo Connector for Admins | Unique identifier of the Confluence application in this Odoo instance. The Confluence application will use this when identifying itself to the Odoo instance. |
Client Secret | The client secret of the Confluence application Must be used when setting up the connection in Confluence, more information: Odoo Connector for Admins | Unique secret of the Confluence application in this Odoo instance. The Confluence application will use this when identifying itself to the Odoo instance. |
Own ID | The id of the Odoo instance | Not used currently for Confluence connections |
Own Secret | The secret of the Odoo instance | Not used currently for Confluence connections |
Model Scheme | The linked model scheme | For more information on model schemes, see Model scheme settings. |
Description | Additional information about the application |
URIs tab
Info |
---|
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
Info |
---|
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 |
Audit tab
Info |
---|
On the audit tab admins can find information about:
|