References¶
Standards¶
- OAuth 2.0 (RFC 6749): the framework, including refresh tokens.
- PKCE (RFC 7636): protects the authorization code flow.
- Token revocation (RFC 7009): how a refresh token gets withdrawn.
- Token introspection (RFC 7662): how a service asks about a token.
- Token exchange (RFC 8693): the per-hop exchange, and
act. - Resource indicators (RFC 8707): how the next hop is named.
- Device authorization grant (RFC 8628): login without a browser on the same machine.
- JWT access tokens (RFC 9068): the profile that services validate.
- HTTP semantics (RFC 9110): 401 and 403, and why
Max-Forwardsdoesn't fit. - OAuth 2.0 security best current practice (RFC 9700): applies to all clients here.
- OpenID Connect Core: login, and user info.
- W3C Trace Context:
traceparent. - AARC-G069 and AARC-G027: the forms of group and capability entitlements.
- Identity and authorization chaining across domains (draft): for more than one identity provider.
- JWT profile for authorization grants (RFC 7523): used by that draft.
GA4GH specifications and Work Stream pages¶
- GA4GH Federated Analysis Work Stream: the group whose products this blueprint is for.
- WES product page, specification, repository: the API of a workflow system.
- TES product page, specification, repository: the API of gateways and nodes.
- TRS product page, repository: where tools come from.
- DRS product page, repository: where data comes from.
- GA4GH data security: the security work of GA4GH, and its AAI profile.
- 2024 Cloud Work Stream roadmap: the Work Stream's plans under its earlier name.
- Cloud APIs comic: an introduction to how the APIs fit together.
Background¶
- proTES #391: the proposal that the testbed checks.
- proTES: the gateway that
gatewaystands in for. - Krini: the portal that
clientstands in for. - FOCA: the framework whose token validation the services follow.
- Cloud Registry: the registry that could one day list targets.
- ELIXIR On-Cloud: the setting of this work.
- ELIXIR Cloud & AAI: the community behind those services.
Tooling¶
mock-oauth2-server: the mock.- uv: the optional development path.
- OAuth Tools: Curity's web client for OAuth flows, for an optional cross-check by hand. All requests pass through Curity's server, so see the warning there. With made-up values, its Token Exchange Flow is also a good first look at the request: the form shows it as a
curlcommand, and nothing is sent until you press the button.
LS Login and Perun docs¶
These cover several Perun instances, so they may not describe LS Login exactly.
- LS Login: the identity provider under test.
- Service registration app: where clients are registered.
- Entitlements, Group entitlement, Resource capability: how entitlements get released, and their forms.
- Facility, Resource: the entities behind the group release.
- Create (and remove) a resource, How to assign a group(s) to a resource: how to set up the release.
- Perun roles and their rights: for which role assigning groups needs.
- Understanding consent pages, Access denied after login: for users who lose access.
- Using Life Science Hostel account, Checking your membership: for test accounts.
- IdP OP Playground: for looking at what an account releases.
- Terms of Use for Service Providers: apply to services that rely on LS AAI.
- Service Provider Re-registration: names the
/cas/oidcissuer.
Papers¶
- The GA4GH Task Execution Application Programming Interface: Enabling Easy Multicloud Task Execution (2024): the TES API.
- Sapporo: a workflow execution service that encourages the reuse of workflows in various languages in bioinformatics: a WES implementation.
- Executing workflows in the cloud with WESkit: another WES implementation.
Further reading¶
- The GA4GH Work Stream's page: lists more papers and implementations in its "Products in Action" section.