Implementer Draft: OAuth Core 1.0 Rev A (Draft 3)
Abstract The OAuth protocol enables websites or applications (Consumers) to access Protected Resources from a web service (Service Provider) via an API, without requiring Users to disclose their Service Provider credentials to the Consumers. More generally, OAuth creates a freely-implementable and generic methodology for API authentication. An example use case is allowing printing service printer.
Implementers' Draft: OAuth Session 1.0 Draft 1
Abstract This specification defines the concept of an Authorization Session which represents the authorization granted to the Consumer to access Protected Resources on behalf of the User. OAuth Core 1.0 assumes that the Authorization Session lifetime and the Access Token lifetime are equal. This specification defines a mechanism for Service Providers to issue Access Tokens with shorter life
Implementers' Draft: OAuth Request Body Hash 1.0 Draft 4
Abstract This specification extends the OAuth signature to include integrity checks on HTTP request bodies with content types other than application/x-www-form-urlencoded. Table of Contents 1. Notation and Conventions 2. Introduction 3. The oauth_body_hash Parameter 3.1. Hash Algorithm 3.2. Signing the Request 3.3. Verifying the Request 4. Example 5. Security Considerations Appendi
Implementers' Draft: OAuth Consumer Request 1.0 Draft 1
Abstract This memo describes a method for using the OAuth flow to sign a request made between a Consumer and Service Provider where no User is involved. This enables OAuth to be used as a replacement to HTTP Basic authentication, which is not as complex as HTTP Digest authentication, and extends the capabilities of the OAuth Consumer credentials. OAuth Core 1.0 defines a protocol for delegating us
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
