Motivation:
Feature request: DIRAC REST API.
Allow better integration of DIRAC client when jobs are submitted by a service that works as a broker for requests posted by a provided frontend form.
Use case:
For the common use cases of DIRAC we have the user submitting the jobs directly to DIRAC. But when there is a service entrusted to manage that asynchronously after a user request, we need to place the usual CLI commands embedded within the service software.
The provided DIRAC API SDKs are limited in language support and requires library dependencies and environment setup for GRID authorization that are adverse to the DIRAC protocol integration with service software.
Integration success:
There are an interesting group of use cases that can start using the GRID, that now only run jobs standalone in the cloud. The key points of the service integration success using DIRAC REST API are:
- allows to bypass the dependencies required by the DIRAC SDK and environment details such as proxy authorization
- avoids clients with the requirement of creating a local REST service to run aside the main software
- reduce the integration code efforts and future maintenance for all interested use cases
- REST API provides an independent language solution (schema complaint), surpassing the SDK language centric limited support from DIRAC client
Implementation proposal
Update interface to provide REST API and integrate it into the required regression tests for future releases.
Implement the support for OIDC and SAML authentication from external IdP for REST API access.
Map the user group attributes and proxy certificate for the job authorization, complying to the CE demands.
Motivation:
Feature request: DIRAC REST API.
Allow better integration of DIRAC client when jobs are submitted by a service that works as a broker for requests posted by a provided frontend form.
Use case:
For the common use cases of DIRAC we have the user submitting the jobs directly to DIRAC. But when there is a service entrusted to manage that asynchronously after a user request, we need to place the usual CLI commands embedded within the service software.
The provided DIRAC API SDKs are limited in language support and requires library dependencies and environment setup for GRID authorization that are adverse to the DIRAC protocol integration with service software.
Integration success:
There are an interesting group of use cases that can start using the GRID, that now only run jobs standalone in the cloud. The key points of the service integration success using DIRAC REST API are:
Implementation proposal
Update interface to provide REST API and integrate it into the required regression tests for future releases.
Implement the support for OIDC and SAML authentication from external IdP for REST API access.
Map the user group attributes and proxy certificate for the job authorization, complying to the CE demands.