Views:

Related resources:

Explanation

Tutorials

How-to guides

You can pull (that is, reference or use) information from the Configuration Store in the following applications in the LUSID ecosystem:

  • Luminesce. For example, you could store your credentials for a service such as Slack and then use the appropriate Finbourne-supplied provider to post messages.
  • Scheduler. For example, you could store your credentials for the LUSID Python SDK and then pull them into a Scheduler job that calls the SDK to upsert transactions.
  • Notification service. For example, you could store your credentials for a service such as JIRA and then pull them into a webhook triggered by a LUSID event.

Authorising the Configuration Store to act on your behalf

Before you can pull information into Scheduler and/or the Notification Service, you must authorise the Configuration Service to 'run as you'.

This is a one-time operation. Once you have performed it, you don't need to do so again for either service. You don't need to perform this operation at all if you just want to pull information into Luminesce.

To do this:

  1. Obtain an API access token. This must be a short-lived OAuth2.0-compliant token from LUSID's identity provider, Okta. It cannot be your personal access token.
  2. Run the following command for your LUSID domain, passing in your API access token:
    curl -X PUT https://<your-domain>.lusid.com/configuration/api/sets/personal/me?action=ensure
      -H 'Content-Length:0'
      -H "Authorization: Bearer <your-API-access-token>"