Skip to content

Prescribe use of JWS for Directory Service #309

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.

Sign up for GitHub

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

Merged
glpatcern merged 2 commits into from
Dec 10, 2025
Merged

Prescribe use of JWS for Directory Service #309

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7524d4b
Prescribe use of JWS for Directory Service
glpatcern Dec 9, 2025
a293f2d
Fixed trivial mistake
glpatcern Dec 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 26 additions & 18 deletions IETF-RFC.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1197,6 +1197,9 @@ https://datatracker.ietf.org/html/rfc6749)", October 2012.
[RFC8615] Nottingham, M. "[Well-Known Uniform Resource Identifiers
(URIs)](https://datatracker.ietf.org/doc/html/rfc8615)", May 2019

[RFC7515] Jones, M., Bradley, J., Sakimura, N., "[JSON Web Signature
(JWS)](https://datatracker.ietf.org/doc/html/rfc7515), May 2015."


# Appendix A: Multi-factor Authentication

Expand Down Expand Up @@ -1355,8 +1358,9 @@ request.

A third-party Directory Service is a back-end service used to federate
multiple OCM Servers and facilitate the Invite flow. It is expected to
expose, via anonymous HTTP GET, a JSON document with the following
format:
expose, via anonymous HTTPS GET, a signed JWS document [RFC7515], where
the signing key MUST be made available offline and the payload MUST
adhere to the following format:

* REQUIRED: `federation` - a human-readable name for the list of OCM
Servers exposed by the Directory Service
Expand All @@ -1372,25 +1376,29 @@ format:
- MUST NOT include userinfo, query, or fragment
- REQUIRED: `displayName` - a human-readable name
for the OCM Server
Example:
Example:

```json
{
"federation": "The ScienceMesh Directory",
"servers": [
{
"url": "https://ocm-server-1.example.org",
"displayName": "OCM Server 1"
},
{
"url": "https://ocm-server-2.example.org:4443",
"displayName": "OCM Server 2"
},
{
"url": "http://192.168.1.1:8080",
"displayName": "OCM Server 3"
}
]
"payload": {
"federation": "The ScienceMesh Directory",
"servers": [
{
"url": "https://ocm-server-1.example.org",
"displayName": "OCM Server 1"
},
{
"url": "https://ocm-server-2.example.org:4443",
"displayName": "OCM Server 2"
},
{
"url": "http://192.168.1.1:8080",
"displayName": "OCM Server 3"
}
]
},
"protected": {"alg": "RS256"},
"signature": "..."
}
```

Expand Down
Loading