draft: OpenID OAuth Extension
Abstract This draft describes a mechanism to combine an OpenID authentication request with the approval of an OAuth request token. Table of Contents 1. Requirements notation 2. Terminology 3. Purpose of this Specification 4. Overview 5. Extension Namespace 6. Discovery 7. Before Requesting Authentication - Registration 8. Requesting Authentication 9. Authorizing the OAuth Request
Draft 1: OAuth Extension for Response Data Format - Draft 1
2. Notation and Conventions The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.). Domain name examples use [RFC2606] (Eastlake, D. and A. Panitz, “Reserved Top Level D
Implementers' Draft: OAuth Key Rotation Extension Draft 1
Abstract OAuth Core 1.0 defines a protocol for delegating user access to Consumer applications without sharing the user's private credentials. Some consumer applications use the RSA_SHA1 signature method. To verify RSA_SHA1 signatures, Service Providers need to be in possession of an authentic copy of the consumer application's public key. Whenever a consumer application changes the private key it
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Implementers' Draft: OAuth Discovery 1.0 Draft 2
Draft 2: OAuth Extension for Specifying User Language Preference - Draft 2
Implementers' Draft: OAuth Gadgets Extension Draft 1
Implementers' Draft: OAuth Consumer Request 1.0 Draft 1