|
| 1 | +Single Sign-On (SSO) and OAuth Environments |
| 2 | +=========================================== |
| 3 | + |
| 4 | +A percentage of extension users may be trying to operate with a |
| 5 | +Confluence instance which deploys some sort of single sign-on (SSO) or |
| 6 | +OAuth capability. How an instance is configured and the means to interact |
| 7 | +can vary per organization, even per instance. There are no definitive steps |
| 8 | +for configuring this extension to guarantee a graceful setup. That being |
| 9 | +said, there should be a means to allow interaction when using this extension. |
| 10 | +This guide may be useful for users configuring this extension for the first |
| 11 | +time in a corporate environment. |
| 12 | + |
| 13 | +Confluence Authentication Token |
| 14 | +------------------------------- |
| 15 | + |
| 16 | +Users be using either an API token (Confluence Cloud) or personal access |
| 17 | +token (PAT; Confluence Data Center) for authenticating with Confluence. |
| 18 | +This means that :lref:`confluence_api_token` (along with |
| 19 | +:lref:`confluence_server_user`) should be used in a Confluence Cloud |
| 20 | +setting, and :lref:`confluence_publish_token` should be used in a Confluence |
| 21 | +Data Center setting (e.g. corporate/self-hosted). |
| 22 | + |
| 23 | +Initial Test |
| 24 | +------------ |
| 25 | + |
| 26 | +Once a token has been configured, it is recommended to perform a connection |
| 27 | +attempt. This is to help ensure a project configuration and extension is |
| 28 | +ready to perform interaction with a Confluence instance, as well as to |
| 29 | +perform a sanity check that additional SSO/OAuth configuration is required. |
| 30 | + |
| 31 | +From the working directory of a project, perform a |
| 32 | +:ref:`connection test <confluence_connection_troubleshooting>`: |
| 33 | + |
| 34 | +.. code-block:: shell-session |
| 35 | +
|
| 36 | + $ python -m sphinxcontrib.confluencebuilder connection-test |
| 37 | + Fetching configuration information... |
| 38 | + ... |
| 39 | +
|
| 40 | +Configuring for Identity or Authorization Instance |
| 41 | +-------------------------------------------------- |
| 42 | + |
| 43 | +This extension uses Requests_ for HTTP requests. Options are available to |
| 44 | +help allow a user tailor requests. These options can be used to inject |
| 45 | +additional token/session information in a request required for a front-end |
| 46 | +of a Confluence instance. |
| 47 | + |
| 48 | +The following options may help: |
| 49 | + |
| 50 | +- :lref:`confluence_publish_headers`: Used to set HTTP headers for |
| 51 | + requests made to a Confluence instance. |
| 52 | +- :lref:`confluence_server_cookies`: Used to provide cookie data for |
| 53 | + requests made to a Confluence instance. |
| 54 | +- :lref:`confluence_server_auth`: Used to provide a custom Requests-capable |
| 55 | + authentication handler for requests made to a Confluence instance. |
| 56 | + |
| 57 | +Which option and values to use will vary. It is recommended, if available, |
| 58 | +to refer to any documentation provided by the Confluence instance about |
| 59 | +what setup is used and what header/cookie data they expect. If no such |
| 60 | +information is available, it is recommended to either create a ticket with |
| 61 | +the service desk associated with the Confluence instance or talk with a |
| 62 | +system administrator for the Confluence instance. |
| 63 | + |
| 64 | +Additional information |
| 65 | +---------------------- |
| 66 | + |
| 67 | +- To help debug the network traffic between this extension and a Confluence |
| 68 | + instance, the :lref:`confluence_publish_debug` option may be used. |
| 69 | +- Refer to `connection-issused issues`_ reported by users. |
| 70 | + |
| 71 | +.. references ------------------------------------------------------------------ |
| 72 | +
|
| 73 | +.. _Requests: https://requests.readthedocs.io/ |
| 74 | +.. _connection-issused issues: https://github.com/sphinx-contrib/confluencebuilder/issues?q=label%3Aconnection-issues |
0 commit comments