Atlas Knowledge Base
Dashboard
Sedona

Sedona


Not in use: the Sedona integration is not in use. This page is kept for reference.

HTTP proxy from APIEngine to a Sedona Office REST endpoint. The single route forwards any supported verb and path to the configured Sedona base URL, adds Basic authentication from SBN options, copies the request headers and (for POST and PUT) the request body, and returns Sedona's response.

Setup

Set these SBN options, then reload options in APIEngine.


Option

Purpose

sed_url

Sedona REST base URL. A trailing / is removed.

sed_usr

Basic-auth user name sent on every forwarded request

sed_pas

Basic-auth password sent on every forwarded request

Auth

  1. Inbound: the proxy route takes no APIEngine user token. Restrict access to it at the network level.
  2. Outbound: every forwarded request carries Authorization: Basic built from sed_usr and sed_pas. The inbound Host, Content-Type and Content-Length headers are dropped; all other inbound headers are forwarded.

Endpoints


Verb

Route

Purpose

GET, POST, PUT, DELETE, OPTIONS

/api/v1/sedona/proxy?command=<path>

Forwards to <sed_url>/<path>. A leading / on the path is removed. POST and PUT bodies are re-sent as application/json; charset=utf-8. Redirects from Sedona are not followed.

Version differences


Behavior

v95 and earlier

v96 and later

Response

Sedona's status code, headers and body are returned as received.

Sedona's body is returned with its content type (default application/octet-stream) and HTTP 200.

Proxy failure

HTTP 500 with the error detail

Standard APIEngine error response

Notes

  1. Every forwarded call (verb, URL, headers, body, response status and response body) is written to the APIEngine log.




Was this helpful?