Overview#

WebFinger is a protocol Discovery Mechanism specified by RFC 7033 that allows for discovery of information about Entities identified by a URI using standard Hypertext Transfer Protocol HTTP methods over a secure transport.[1]

Information about a person might be discovered via an "acct:" URI, for example, which is a URI that looks like an email address.

A WebFinger resource returns a JSON Resource Descriptor (JRD) describing the entity that is queried.

WebFinger is specified as the discovery protocol for OpenID Connect.

WebFinger is a Well-known URI#

WebFinger has a suffix of "webfinger" registered as a Well-Known URI

/.well-known/webfinger

A WebFinger resource returns a JavaScript Object Notation (JSON) object describing the entity that is queried. The JSON Object is referred to as the JSON Resource Descriptor (JRD).

Example OpenID Provider Issuer Discovery [2]#

OpenID Provider Issuer Discovery uses WebFinger!! More Information There might be more information for this subject on one of the following:

• Issuer
• JSON Identity Suite
• OAuth 2.0 Authorization Server Metadata
• OpenAM Endpoints
• OpenID Connect
• OpenID Connect Discovery
• OpenID Provider Issuer Discovery
• Openid-configuration
• RFC 7033
• Self-Issued OpenID Provider
• WebFinger
• Why OAuth 2.0

More Information#

---

• [#1] - WebFingerContent unavailable! (broken link)https://ldapwiki.com/wiki/images/out.png - based on data observed:2015-05-18
• [#2] - Discovery Webfinger and OpenID ConnectContent unavailable! (broken link)https://ldapwiki.com/wiki/images/out.png - based on data observed:2015-05-18