
datatracker.ietf.org/doc/html/rfc7628.html
Preview meta tags from the datatracker.ietf.org website.
Linked Hostnames
7- 59 links todatatracker.ietf.org
- 24 links towww.rfc-editor.org
- 2 links toopenid.net
- 1 link togithub.com
- 1 link tomailarchive.ietf.org
- 1 link totrustee.ietf.org
- 1 link towww.tschofenig.priv.at
Thumbnail

Search Engine Appearance
https://datatracker.ietf.org/doc/html/rfc7628.html
RFC 7628: A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth
A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth (RFC 7628, )
Bing
RFC 7628: A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth
https://datatracker.ietf.org/doc/html/rfc7628.html
A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth (RFC 7628, )
DuckDuckGo

RFC 7628: A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth
A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth (RFC 7628, )
General Meta Tags
11- titleRFC 7628 - A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- descriptionA Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth (RFC 7628, )
Open Graph Meta Tags
10- og:titleRFC 7628: A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth
- og:urlhttps://datatracker.ietf.org/doc/html/rfc7628.html
- og:site_nameIETF Datatracker
- og:descriptionOAuth enables a third-party application to obtain limited access to a protected resource, either on behalf of a resource owner by orchestrating an approval interaction or by allowing the third-party application to obtain access on its own behalf. This document defines how an application client uses credentials obtained via OAuth over the Simple Authentication and Security Layer (SASL) to access a protected resource at a resource server. Thereby, it enables schemes defined within the OAuth framework for non-HTTP-based application protocols. Clients typically store the user's long-term credential. This does, however, lead to significant security vulnerabilities, for example, when such a credential leaks. A significant benefit of OAuth for usage in those clients is that the password is replaced by a shared secret with higher entropy, i.e., the token. Tokens typically provide limited access rights and can be managed and revoked separately from the user's long-term password.
- og:typearticle
Twitter Meta Tags
1- twitter:cardsummary_large_image
Link Tags
12- alternate/feed/document-changes/rfc7628/
- apple-touch-iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/html/rfc7628.html
- iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-32.png
- iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-16.png
Emails
4- wmills%40yahoo-inc.com
- tjs%40mirapoint.com
- Hannes.Tschofenig%40gmx.net
- [email protected]?subject=rfc7628
Links
89- http://openid.net/specs/openid-connect-core-1_0.html
- http://openid.net/specs/openid-connect-discovery-1_0.html
- http://trustee.ietf.org/license-info
- http://www.rfc-editor.org/info/rfc2119
- http://www.rfc-editor.org/info/rfc3501