diff --git a/openid-federation-1_0.xml b/openid-federation-1_0.xml
index 7fa24e2..314cbdb 100644
--- a/openid-federation-1_0.xml
+++ b/openid-federation-1_0.xml
@@ -78,7 +78,7 @@
-
+ OpenID Connect Working Group
@@ -1057,7 +1057,7 @@
"iss": "https://feide.no",
"sub": "https://ntnu.no",
"iat": 1516239022,
- "exp": 1516298022,
+ "exp": 1516843822,
"jwks": {
"keys": [
{
@@ -1065,7 +1065,7 @@
"alg": "RS256",
"use": "sig",
"kid": "NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs",
- "n": "pnXBOusEANuug6ewezb9J_...",
+ "n": "vHOJrp-zLST7FwvzAwelR9Vo...",
"e": "AQAB"
}
]
@@ -1478,7 +1478,7 @@
scheme and MAY contain port,
path, and query parameter components;
it MUST NOT contain a fragment component.
- Any federation Entity MAY publish a
+ Any Federation Entity MAY publish a
federation_resolve_endpoint.
@@ -1614,15 +1614,15 @@
The following is a non-normative example of an HTTP GET request for
- a Subordinate Statement from edugain.org about https://openid.sunet.se:
+ a Subordinate Statement from edugain.org about https://sunet.se:
API Request for a Subordinate Statement
@@ -4319,7 +4319,7 @@ Host: edugain.org
@@ -4561,7 +4561,7 @@ Host: openid.sunet.se
Content-Type: application/json
[
- "https://ntnu.andreas.labs.uninett.no/",
+ "https://ntnu.andreas.labs.uninett.no",
"https://blackboard.ntnu.no/openid/callback",
"https://serviceprovider.andreas.labs.uninett.no/application17"
]
@@ -4651,7 +4651,7 @@ GET /resolve?
sub=https%3A%2F%2Fop.example.it%2Fspid&
entity_type=openid_provider&
trust_anchor=https%3A%2F%2Fswamid.se HTTP/1.1
-Host: openid.sunet.se
+Host: sunet.se
]]>
@@ -4784,10 +4784,10 @@ Host: openid.sunet.se
In this example, the requesting party would make the following request to the Entity
- https://openid.sunet.se
+ https://op.sunet.se
to obtain its Entity Configuration:
@@ -5880,7 +5880,7 @@ Content-Type: application/json
@@ -5890,7 +5890,7 @@ Content-Type: application/json
The response is an Entity Configuration.
If the Entity is an Intermediate Entity or a Trust Anchor, the
- response MUST contain metadata for a federation Entity
+ response MUST contain metadata for a Federation Entity
(federation_entity).
@@ -5909,26 +5909,61 @@ Content-Type: application/json
Intermediate Entity:
- Entity Configuration Response JWT Claims Set
+ Entity Configuration Response JWT Claims Set for an Intermediate
+
+
+
+
+
+ The following is a non-normative example JWT Claims Set for a response from an
+ OpenID Provider Entity:
+
+
+ Entity Configuration Response JWT Claims Set for an OP
+
+
@@ -6522,7 +6559,7 @@ Content-Type: application/json
{
"typ": "oauth-authz-req+jwt",
"alg": "RS256",
- "kid": "that-kid-which-points-to-a-jwk-contained-in-the-trust-chain",
+ "kid": "kid-that-points-to-a-jwk-contained-in-the-trust-chain",
"trust_chain" : [
"eyJhbGciOiJSUzI1NiIsImtpZCI6Ims1NEhRdERpYnlHY3M5WldWTWZ2aUhm ...",
"eyJhbGciOiJSUzI1NiIsImtpZCI6IkJYdmZybG5oQU11SFIwN2FqVW1BY0JS ...",
@@ -10606,10 +10643,10 @@ HTTP/1.1 302 Found
},
"metadata": {
"openid_provider": {
- "issuer": "https://op.umu.se/openid",
- "signed_jwks_uri": "https://op.umu.se/openid/jwks.jose",
+ "issuer": "https://op.umu.se",
+ "signed_jwks_uri": "https://op.umu.se/jwks.jose",
"authorization_endpoint":
- "https://op.umu.se/openid/authorization",
+ "https://op.umu.se/authorization",
"client_registration_types_supported": [
"automatic",
"explicit"
@@ -10636,9 +10673,9 @@ HTTP/1.1 302 Found
"pairwise",
"public"
],
- "token_endpoint": "https://op.umu.se/openid/token",
+ "token_endpoint": "https://op.umu.se/token",
"federation_registration_endpoint":
- "https://op.umu.se/openid/fedreg",
+ "https://op.umu.se/fedreg",
"token_endpoint_auth_methods_supported": [
"client_secret_post",
"client_secret_basic",
@@ -11141,13 +11178,13 @@ Host: geant.org
exp Claim.
+ Fixed #327: Use separate examples for Intermediate and OP Entity Configurations.
+
+
+ Changed some "iss" and "exp" dates in examples so they make better sense.
+
+
+ Changed "kid" values in examples to be plausible JWK Thumbprint values for their keys.
Added informative references to OpenID Federation 1.1 and
OpenID Connect Federation 1.1 specifications.