authentication-and-environments: Starting out and working with different Etna environments

In magmaR: R-Client for Interacting with the 'UCSF Data Library'

Starting out and working with different Etna environments

Description

Starting out and working with different Etna environments

Authorization via 'token's

Access to magma via magmaR is authenticated via 'token's which users can obtain from Janus. A valid token must be provided to magmaR before any calls to magma can be successfully performed. To provide this token, users should obtain their token from Janus, then provide it to magmaR functions using the magmaRset function. See the function's own documentation and other functions' examples for further details and usage code.

Non-production Environments

The code base relies on 2 different ecosystems of all of its components for purposes of "development" of new tools and features, and "production", the release version which most users see. We won't get into the details too much more here, but users with access to the development environment can access it magmaR.

To do so, users should provide the url of their alternative version of magma to magmaR functions using the magmaRset function. If proxy or other curl-request settings need to be adjusted, users can provide these via the opts input of this same magmaRset function. At a minimum, you will likely want to use opts = list(ssl_verifyhost = FALSE, ssl_verifypeer = FALSE).

See Also

magmaRset

magmaR documentation built on June 8, 2025, 10 a.m.