Skip to content

Latest commit

 

History

History
61 lines (41 loc) · 2.69 KB

comp_edi.rst

File metadata and controls

61 lines (41 loc) · 2.69 KB

EDI

Technologies used GoLang
Distribution representation Docker Image
Source code location legion/legion/operator
Can be used w/o Legion Platform? Yes
Does it connect to another services? Yes (Kubernetes API)
Can be deployed locally? If local Kubernetes cluster is present
Does it provide any interface? Yes (HTTP REST API)

:term:`EDI` is a service which allows to manage Legion Platform entities such as:

Also :term:`EDI` provides possibility to retrieve:

Things that :term:`EDI` can not do:

How to reach EDI in target cluster

By default, :term:`EDI` service is available on URL edi.<cluster-name>, where <cluster name> is target cluster's base URL (e.g. edi.my-cluster.lab.university.com. But this address can be configured during Legion's HELM chart installation.

What URLs does it provide

All information about URLs that :term:`EDI` provides can be viewed using auto generated, interactive Swagger (OpenAPI) documentation web page, located at <edi-address>/swagger/index.html. You can read all up-to-date documentation and invoke all methods (allowed for your account) right on this webpage.

Authentication and authorization

:term:`EDI` analyzes incoming HTTP headers for JWT token, extracts client's scopes from this token and approves / declines incoming requests based on these (provided in JWT) scopes.

Details of realization

:term:`EDI` is a HTTP REST API server, written using GoLang. For easily integration it provides swagger endpoint with up-to-date protocol information.