Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note multiple API endpoint base paths in spec.yaml #118

Closed
michielbdejong opened this issue Sep 5, 2024 · 1 comment
Closed

Note multiple API endpoint base paths in spec.yaml #118

michielbdejong opened this issue Sep 5, 2024 · 1 comment
Labels

Comments

@michielbdejong
Copy link
Contributor

In spec.yaml we define:

  • https://<discovery-fqdn>/.well-known/ocm
  • https://<discovery-fqdn>/ocm-provider
  • https://<ocm-fqdn>/<ocm-base-path>/shares
  • https://<ocm-fqdn>/<ocm-base-path>/notifications
  • https://<ocm-fqdn>/<ocm-base-path>/invite-accepted

(<discovery-fqdn> = is an OCM server's <fqdn> or fallback to whatever FQDN its SRV DNS record redirects to)
(<ocm-fqdn> and <ocm-base-path> come from discovery endPoint value)

We should make it clear that the two discovery endpoints live on a different base URL than the three API endpoints.

@glpatcern glpatcern added the bug label Sep 30, 2024
@glpatcern
Copy link
Member

This was closed at some stage, the spec now mentions discovery-fqdn only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants