FastFed Core 1.0 发布 draft 03,展示应用提供方元数据示例
来源标题:FastFed Core 1.0 – draft 03
FastFed Core 1.0 发布 draft 03,其中给出了 Application Provider Metadata 的非规范性示例,包含 entity_id、provider_domain、联系方式、展示设置以及认证、配置、schema、签名算法等能力声明。示例还列出 fastfed_handshake_register_uri,并说明元数据端点用于读取元数据文档。
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
The following is a non-normative example of Application Provider Metadata:
{ "application_provider": { "entity_id": "https://tenant-67890.app.example.com/" "provider_domain": "example.com", "provider_contact_information": { "organization": "Example Inc.", "phone": "+1-800-555-5555", "email": "support@example.com" }, "display_settings": { "display_name": "Example Application Provider", "logo_uri": "https://app.example.com/images/logo.png", "icon_uri": "https://app.example.com/images/icon.png", "license": "https://openid.net/intellectual-property/licenses/fastfed/1.0/" } "capabilities": { "authentication_profiles": [ "urn:ietf:params:fastfed:1.0:authentication:saml:2.0:enterprise" ], "provisioning_profiles": [ "urn:ietf:params:fastfed:1.0:provisioning:scim:2.0:enterprise" ], "schema_grammars": [ "urn:ietf:params:fastfed:1.0:schemas:scim:2.0" ], "signing_algorithms": [ "ES512", "RS256" ] }, "fastfed_handshake_register_uri": "https://tenant-67890.app.example.com/fastfed/register" }
- Metadata Endpoints
Metadata Endpoints describe the semantics for reading Metadata documents.
A request to this endpoint will return the Provider Metadata document defined in Section 3.3.
The Provider Metadata Endpoint MUST be accessible to other Providers who are permitted to initiate a FastFed Handshake Flow with the entity. Access to the Endpoint SHOULD NOT require Administrators to perform pre-configuration or pre-registration of any form between the two Providers, except the necessary act of inputting the URL for the Provider Metadata Endpoint (a.k.a. "FastFed URL") to initiate the FastFed Handshake if the endpoint location is not discoverable through other means. Requests to the endpoint may be rate-limited or otherwise limited to prevent a denial-of-service attack.
To prevent impersonation of Providers, the value of the provider_domain returned in the Metadata (Section 3.3.7) MUST suffix-match the domain of the Metadata Endpoint.
The Metadata Endpoint MAY be hosted at a subdomain of the provider_domain.
A TLS server certificate check MUST be performed when connecting to the Metadata Endpoint to verify Provider ownership of the domain. See Section 8.3.
The following is a non-normative example showing valid and invalid Metadata Endpoints.
For a Metadata document containing the following domain name: { "provider_domain: "idp.example.com", ... }
The name is valid if retrieved from any of these Endpoints:
https://idp.example.com/ --> OK. Exact Match. https://tenant-12345.idp.example.com/ --> OK. Suffix Match. https://idp.example.com/fastfed/metadata --> OK. Exact Match + Path.
The name is invalid if retrieved from any of these Endpoints:
https://idp.example.com.otherdomain.com/ --> INVALID. No suffix match. https://example.com/ --> INVALID. Incomplete match. http://idp.example.com/ --> INVALID. Not https.
If the provider_domain is invalid, the FastFed Handshake MUST be halted as specified in Section 7.1.4.
Discovering the location of a Provider Metadata Endpoint for a specific end-user can be achieved through several means. If the user's email address is available to the Application Provider, the RECOMMENDED method of discovery is via a WebFinger request [RFC7033] to the user's email domain.
WebFinger traditionally requires a webserver hosted at the root domain. For example, if a user's email address is "user@company.com", WebFinger requests are sent to "https://company.com/.well_known/webfinger".
However, administrators at large enterprises can experience organizational roadblocks when attempting to host a WebFinger discovery endpoint at the root domain. This is because the root domain is often the public-facing product or web presence for an organization. This domain is often maintained by different owners who possess security and operational privileges that FastFed administrators may not share.
Therefore, to simplify adoption, FastFed supports WebFinger discovery using subdomains. The subdomain location is determined by prefixing the email domain with "fastfed._well_known". For example, if the user email is "babs@example.com", the resulting Webfinger endpoint is "https://fastfed._well_known.example.com".
FastFed uses the following rel value in WebFinger:
To start discovery of FastFed endpoints, the Application Provider makes an HTTP GET request to the WebFinger [RFC7033] endpoint with the resource value set to the user email address prepended with the acct: scheme [RFC7565]. All WebFinger communication MUST utilize TLS in the manner described in Section 7.1.1.
The FastFed Provider Metadata location MUST be returned in the WebFinger response as the value of the href member of a links array element with rel member value http://openid.net/specs/fastfed/1.0/provider. (Per Section 7 of WebFinger [RFC7033], obtaining the WebFinger response may first involve following some redirects.)
The returned Issuer location MUST be a URI [RFC3986] with a scheme component that MUST be https, a host component, and optionally, port and path components and no query or fragment components. Note that the WebFinger request may return a metadata location hosted under a different domain than the user's email.
The WebFinger endpoint MAY return a static response to any query, regardless of input parameters. This can be useful, for example, when all users under the same domain will share the same Identity Provider. A static response allows the WebFinger hosting provider to use a static file and avoid the overhead of operating a full-featured WebFinger service.
To allow the use of static responses, subject MAY be omitted from the WebFinger response.
The following non-normative example demonstrates the discovery of FastFed Provider Metadata for jane@example.com. The WebFinger parameters are as follows:
The Application Provider makes a WebFinger request to the well-known FastFed subdomain endpoint (with line wraps for display purposes only):
GET / ?resource=acct%3Ajane%40example.com &rel=http%3A%2F%2Fopenid.net%2Fspecs%2Ffastfed%2F1.0%2Fprovider HTTP/1.1 Host: fastfed._well_known.example.com
HTTP/1.1 200 OK Content-Type: application/jrd+json
{ "subject": "acct:jane@example.com", "links": [ { "rel": "http://openid.net/specs/fastfed/1.0/provider", "href": "https://tenant-12345.idp.example.com/fastfed" } ] }
4.1.2.2. Alternative Discovery Mechanisms
Application Providers MAY use other means of discovering the FastFed URL for an Identity Provider. This is an implementation detail.
As a reference to implementers, another mechanism may be to ask the Administrator to read the single sign-on documentation provided by their Identity Provider to find the FastFed URL and then paste the value into a form field.
After the endpoint is discovered, Provider Metadata can be read by making an HTTP GET request to the Provider Metadata Endpoint.
The following is a non-normative example read request:
GET /fastfed/provider-metadata HTTP/1.1 Accept: application/json Host: provider.example.com
4.1.4. Read Response
Upon a successful read operation, the server SHOULD return all available Provider Metadata.
A successful response SHOULD use the HTTP 200 OK status code and return a JSON document [RFC4627] using the application/json_content type with the Provider Metadata values as top-level members of the root JSON object.
The following is a non-normative example read response (with line wraps within values for display purposes only):
HTTP/1.1 200 OK Content-Type: application/json { "identity_provider": { "entity_id": "https://tenant-12345.idp.example.com/" "provider_domain": "example.com", "provider_contact_information": { "organization": "Example Inc.", "phone": "+1-800-555-5555", "email": "support@example.com" }, "display_settings": { "display_name": "Example Identity Provider", "logo_uri": "https://idp.example.com/images/logo.png", "icon_uri": "https://idp.example.com/images/icon.png", "license": "https://openid.net/intellectual-property/licenses/fastfed/1.0/" } "capabilities": { "authentication_profiles": [ "urn:ietf:params:fastfed:1.0:authentication:saml:2.0:enterprise" ], "provisioning_profiles": [ "urn:ietf:params:fastfed:1.0:provisioning:scim:2.0:enterprise" ], "schema_grammars": [ "urn:ietf:params:fastfed:1.0:schemas:scim:2.0" ], "signing_algorithms": [ "ES512", "RS256" ] }, "jwks_uri": "https://idp.example.com/keys", "fastfed_handshake_start_uri": "https://tenant-12345.idp.example.com/fastfed/start", }
4.1.5. Metadata Refresh
Provider Metadata contains information that may be used on a recurring basis, such as the list of supported signing algorithms and URLs of image files. Consumers of the metadata SHOULD locally cache the metadata information and image files that will be used on an ongoing basis after the FastFed Handshake completes.
A Provider is permitted to refresh the following values from another Provider's Metadata Endpoint on a recurring basis, outside the context of a FastFed Handshake.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。