[B! oauth] gom68ã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

gom68 id:gom68

oauthã«é–¢ã™ã‚‹gom68ã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (25)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

OAuth2ã®æ¬¡ã«æ¥ã‚‹ã¨è¨€ã‚ã‚Œã‚‹èªå¯ãƒ—ãƒãƒˆã‚³ãƒ«GNAPã¨ã¯ãªã«ã‹ | ãƒ¡ãƒ«ã‚«ãƒªã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ãƒªãƒ³ã‚°
Merpay Advant Calendar 2020ã€23æ—¥ç›®ã®è¨˜äº‹ã¯ã€è¶£å‘³ã§èªè¨¼èªå¯ã‚’ã‚„ã£ã¦ã„ã‚‹ @nerocrux ãŒé€ã‚Šã„ãŸã—ã¾ã™ã€‚ æœ€è¿‘ GNAP ã¨ã„ã†èªå¯ãƒ—ãƒãƒˆã‚³ãƒ«ã®ãƒ¯ãƒ¼ã‚ãƒ³ã‚°ã‚°ãƒ«ãƒ¼ãƒ—ãƒ‰ãƒ©ãƒ•ãƒˆãŒå‡ºã¦ã„ã¦é ‘å¼µã£ã¦ç´°ã‹ãèªã¿ã¾ã—ãŸã®ã§ã€ï¼ˆæ¬¡å›žã¯ã„ã„åŠ æ¸›ã«ä»•äº‹ã§ã‚„ã£ã¦ã‚‹ã“ã¨ã«ã¤ã„ã¦ãŠè©±ã—ã¾ã™ãŒï¼‰ä»Šå›žã¯ãã® GNAP ã«ã¤ã„ã¦ç´¹ä»‹ã•ã›ã¦ãã ã•ã„ã€‚ GNAP ã¨ã¯ãªã«ã‹ï¼Ÿ GNAP ã¯ Grant Negotiation and Authorization Protocol ã®ç•¥ã§ã€èªå¯ã®ãƒ—ãƒãƒˆã‚³ãƒ«ã§ã™ã€‚Justin Richerã•ã‚“ã¨ã„ã†æ–¹ã‚’ä¸å¿ƒã«ç–å®šã—ã¦ã„ã¾ã™ã€‚ä½œè€…ã«ã‚ˆã‚‹ã¨ã€GNAP ã®ç™ºéŸ³ã¯ ã’ãªã£ã· ã«ãªã‚Šã¾ã™ã€‚ èªå¯ï¼ˆAuthorizationï¼‰ãƒ—ãƒãƒˆã‚³ãƒ«ã¨è¨€ãˆã°ã€OAuth 2.0 (RFC6749) ãŒåºƒãçŸ¥ã‚‰ã‚Œã€é‹ç”¨ã•ã‚Œã¦ã„ã¾ã™ã€‚GNAP ã¯ OAuth 2 ã®å¾Œç¶™ã¨ã—
gom68 2020/12/24
oauth

identity
ãƒªãƒ³ã‚¯
OAuth2.0æ‹¡å¼µä»•æ§˜ã®PKCEå®Ÿè£…ç´¹ä»‹ ã€œ Yahoo! IDé€£æºã«å°Žå…¥ã—ã¾ã—ãŸ
ãƒ¤ãƒ•ãƒ¼æ ªå¼ä¼šç¤¾ã¯ã€2023å¹´10æœˆ1æ—¥ã«LINEãƒ¤ãƒ•ãƒ¼æ ªå¼ä¼šç¤¾ã«ãªã‚Šã¾ã—ãŸã€‚LINEãƒ¤ãƒ•ãƒ¼æ ªå¼ä¼šç¤¾ã®æ–°ã—ã„ãƒ–ãƒã‚°ã¯ã“ã¡ã‚‰ã§ã™ã€‚LINEãƒ¤ãƒ•ãƒ¼ Tech Blog ã“ã‚“ã«ã¡ã¯ã€‚ ã‚µãƒ¼ãƒ“ã‚¹çµ±æ‹¬æœ¬éƒ¨ã®éƒ½ç‘(@kazuki229_dev)ã§ã™ã€‚ æ–°å’4å¹´ç›®ã§æ™®æ®µã¯Yahoo! IDé€£æºã®ã‚µãƒ¼ãƒãƒ¼ã‚µã‚¤ãƒ‰ã€iOSã®SDKã®é–‹ç™ºãªã©ã‚’æ‹…å½“ã—ã¦ã„ã¾ã™ã€‚ Yahoo! IDé€£æºã¨ã¯ã€Yahoo! JAPANã®ã‚·ãƒ³ã‚°ãƒ«ã‚µã‚¤ãƒ³ã‚ªãƒ³ã‚„ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®å±žæ€§æƒ…å ±ã‚’å–å¾—ã™ã‚‹IDé€£æºã®ä»•çµ„ã¿ã§ã™ã€‚ Yahoo! IDé€£æºã¨ã¯ ã“ã®Yahoo! IDé€£æºã§ã¯PKCEã¨ã„ã†OAuth2.0ã®æ‹¡å¼µä»•æ§˜ã‚’å®Ÿè£…ã—ã¾ã—ãŸã€‚ https://developer.yahoo.co.jp/changelog/2019-12-12-yconnect.html ãã“ã§ã€PKCEã®åŸºæœ¬çš„ãªè©±ã¨ã€å®Ÿè£…ã®éš›ã«èª¿æŸ»ã—ãŸã“ã¨ã‚’ã¾ã¨ã‚ã¦ã¿ã¾ã—ãŸã€‚ PKCEã¨ã¯
gom68 2019/12/19
oauth

security
ãƒªãƒ³ã‚¯
OAuth 2.0/OpenID Connectã®2ã¤ã®ãƒˆãƒ¼ã‚¯ãƒ³ã®ä½¿ã„ã¿ã¡ - Qiita
{ "active": true, "client_id": "l238j323ds-23ij4", "username": "jdoe", "scope": "read write dolphin", "sub": "Z5O3upPC88QrAjx00dis", "aud": "https://protected.example.net/resource", "iss": "https://server.example.com/", "exp": 1419356238, "iat": 1419350238, "extension_field": "twenty-seven" } ä¸Šè¨˜ä¾‹ã®ã‚ˆã†ã«ã€IDãƒˆãƒ¼ã‚¯ãƒ³ã¨ç•°ãªã‚Šã€audã«ã¯å—ã‘å–ã‚Šå´ã§ã‚ã‚‹ãƒªã‚½ãƒ¼ã‚¹ã‚µãƒ¼ãƒã‚’è¡¨ã™æ–‡å—åˆ—ãŒå…¥ã‚Šã¾ã™ã€‚client_idã«ã¯OAuth 2.0ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆIDãŒå…¥ã‚Šã¾ã™ã®ã§ã€ã©ã®OAuth 2.0ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«ã€
gom68 2018/09/17
oauth

openid

aws
ãƒªãƒ³ã‚¯
OAuth for Native Apps | GREE Engineering
GREE Advent Calendar 9æ—¥ç›®ã¯ @nov ãŒæ‹…å½“ã—ã¾ã™ã€‚ åƒ•ã¯ GREE ã§ã¯ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£éƒ¨ã«æ‰€å±žã—ã¦ãŠã‚Šã€ç¤¾å¤–ã§ã¯ OAuth ã‚„ OpenID Connect ãªã©ã® Identity é–¢é€£æŠ€è¡“ã«ã¤ã„ã¦ã®ç¿»è¨³ã‚„è¬›æ¼”ãªã©ã‚’è¡Œã£ãŸã‚Šã‚‚ã—ã¦ã„ã¾ã™ã€‚ ä»Šæ—¥ã¯ GREE Advent Calendar ã¨ã„ã†ã“ã¨ã§ã€Native App ã‚³ãƒ³ãƒ†ã‚ã‚¹ãƒˆã§ã® OAuth ã®è©±ã‚’å°‘ã—æ›¸ã„ã¦ã¿ã‚ˆã†ã¨æ€ã„ã¾ã™ã€‚ ã¯ã˜ã‚ã« Native App ã‚’é–‹ç™ºã—ã¦ã„ã‚‹ã¨ã€Backend Server ã¨ã®ã‚„ã‚Šã¨ã‚Šã‚„ Facebook Login ã‚„ Google Sign-in ãªã©ã§ã€å¿…ãšã¨è¨€ã£ã¦ã„ã„ã»ã© OAuth 2.0 ã¨ã„ã†ã®ãŒå‡ºã¦ãã¾ã™ã€‚ OAuth 1.0 ã¨ç•°ãªã‚Šãƒªã‚¯ã‚¨ã‚¹ãƒˆã«ç½²åãŒä¸è¦ã ã£ãŸã‚Šã€Client Secret (a.k.a Consumer Secret) ç„¡ã—ã§ã‚‚
gom68 2015/12/09
oauth
ãƒªãƒ³ã‚¯
OAuth 2.0ã®Access Tokenã¸ã®JSON Web Token(JSON Web Signature)ã®é©ç”¨ - r-weblife
ã“ã‚“ã°ã‚“ã¯ã€ritouã§ã™ã€‚ ä¹…ã€…ã®æŠ•ç¨¿ãªæ°—ãŒã—ã¾ã™ãŒã€ä»Šå›žã¯OAuth 2.0ã®ãƒªã‚½ãƒ¼ã‚¹ã‚¢ã‚¯ã‚»ã‚¹æ™‚ã®è¨è¨ˆã®è©±ã§ã™ã€‚ ãšãƒ¼ã£ã¨å‰ã‹ã‚‰æ›¸ã“ã†ã¨æ€ã„ã¤ã¤æ›¸ã„ã¦ãªã‹ã£ãŸã®ã§ã€ã“ã“ã«æ›¸ã„ã¦ãŠãã¾ã™ã€‚ å‡ºã¦ãã‚‹ç”¨èªžã‚„ä»•æ§˜ã¯ã€ä¸‹è¨˜ã®ç¿»è¨³ãƒªãƒ³ã‚¯ã‚’å‚ç…§ã—ã¦ãã ã•ã„ã€‚ The OAuth 2.0 Authorization Framework JSON Web Signature (JWS) æƒ³å®šã™ã‚‹ç’°å¢ƒ ã‚ã‚Šã¨ã‚ˆãã‚ã‚‹ç’°å¢ƒã‚’æƒ³å®šã—ã¦ã„ã¾ã™ã€‚ OAuth 2.0ã§èªå¯ã‚µãƒ¼ãƒãƒ¼ã¨ãƒªã‚½ãƒ¼ã‚¹ã‚µãƒ¼ãƒãƒ¼ãŒã‚ã‚‹ èªå¯ã‚µãƒ¼ãƒãƒ¼ãŒAccess Tokenã‚’ç™ºè¡Œ ãƒªã‚½ãƒ¼ã‚¹ã‚µãƒ¼ãƒãƒ¼ãŒAPIãƒªã‚¯ã‚¨ã‚¹ãƒˆã«å«ã¾ã‚Œã‚‹Access Tokenã‚’æ¤œè¨¼ã™ã‚‹ ã‚ˆãã‚ã‚‹å®Ÿè£…ã¨ãã®æ‚©ã¿ã©ã“ã‚ã‚’ã€JSON Web Token(JSON Web Signature)ã«ã‚ˆã‚Šè»½æ¸›ã§ãã‚‹ã‹ã‚‚ã¨ã„ã†è©±ã§ã™ã€‚ ã‚ˆãã‚ã‚‹å®Ÿè£… : Access Tokenã«ä¸€è¦‹ãƒ©
gom68 2014/09/29
oauth
ãƒªãƒ³ã‚¯
omniauth-google-oauth2ã§ãƒãƒžã£ãŸãƒ¡ãƒ¢ - é»’é”æ³•ä½¿ã„ã®å¼Ÿå
gom68 2013/07/23
oauth

google
ãƒªãƒ³ã‚¯
The OAuth 2.0 Authorization Framework
Abstract OAuth 2.0 ã¯, ã‚µãƒ¼ãƒ‰ãƒ‘ãƒ¼ãƒ†ã‚£ãƒ¼ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã«ã‚ˆã‚‹HTTPã‚µãƒ¼ãƒ“ã‚¹ã¸ã®é™å®šçš„ãªã‚¢ã‚¯ã‚»ã‚¹ã‚’å¯èƒ½ã«ã™ã‚‹èªå¯ãƒ•ãƒ¬ãƒ¼ãƒ ãƒ¯ãƒ¼ã‚¯ã§ã‚ã‚‹. ã‚µãƒ¼ãƒ‰ãƒ‘ãƒ¼ãƒ†ã‚£ãƒ¼ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã«ã‚ˆã‚‹ã‚¢ã‚¯ã‚»ã‚¹æ¨©ã®å–å¾—ã«ã¯, ãƒªã‚½ãƒ¼ã‚¹ã‚ªãƒ¼ãƒŠãƒ¼ã¨HTTPã‚µãƒ¼ãƒ“ã‚¹ã®é–“ã§åŒæ„ã®ãŸã‚ã®ã‚¤ãƒ³ã‚¿ãƒ©ã‚¯ã‚·ãƒ§ãƒ³ã‚’ä¼´ã†å ´åˆã‚‚ã‚ã‚‹ãŒ, ã‚µãƒ¼ãƒ‰ãƒ‘ãƒ¼ãƒ†ã‚£ãƒ¼ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³è‡ªèº«ãŒè‡ªã‚‰ã®æ¨©é™ã«ãŠã„ã¦ã‚¢ã‚¯ã‚»ã‚¹ã‚’è¨±å¯ã™ã‚‹å ´åˆã‚‚ã‚ã‚‹. æœ¬ä»•æ§˜æ›¸ã¯RFC 5849ã«è¨˜è¼‰ã•ã‚Œã¦ã„ã‚‹OAuth 1.0 ãƒ—ãƒãƒˆã‚³ãƒ«ã‚’å»ƒæ¢ã—, ãã®ä»£æ›¿ã¨ãªã‚‹ã‚‚ã®ã§ã‚ã‚‹. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It re
gom68 2013/01/22
oauth

rfc
ãƒªãƒ³ã‚¯
ã¡ã‚‡ã£ã¨å‰ã«è©±é¡Œã«ãªã£ãŸOpenID Connectã®ä»•æ§˜ã¨ã¯ï¼Ÿ - r-weblife
OpenID Connectã§ã‚°ã‚°ã£ã¦ã¿ãŸã‚‚ã®ã®ã€ç´¹ä»‹è¨˜äº‹ã°ã‹ã‚Šã§ä¸èº«ã‚’èª¬æ˜Žã—ã¦ã‚‹äººãŒã‚ã‚“ã¾ã‚Šã„ãªã„ã‚ˆã†ã§ã—ãŸã€‚ ä»•æ§˜ãƒ‰ã‚ãƒ¥ãƒ¡ãƒ³ãƒˆï¼Ÿã‹ã©ã†ã‹ã‚ã‹ã‚Šã¾ã›ã‚“ãŒã€ã¾ã¨ã‚‚ãªãƒ‰ã‚ãƒ¥ãƒ¡ãƒ³ãƒˆã¯ http://openidconnect.com/ ã—ã‹ã‚ã‚Šã¾ã›ã‚“ã€‚ è‹±èªžèªã‚ã‚‹ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ãªã‚‰ã“ã‚Œèªã‚“ã§ã ã„ãŸã„ã‚ã‹ã£ã¦ã‚‹ã®ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ãŒã€ã–ã£ã¨ã¾ã¨ã‚ã¦ãŠãã¾ã™ã€‚ 3è¡Œã§èª¬æ˜Ž OAuth 2.0ã‚’ä½¿ã£ã¦ã€URLå½¢å¼ã®User Identifierã‚’è¿”ã™ User Identifierã¯ User Info APIã¨ã—ã¦å±žæ€§æƒ…å ±å–å¾—ã«åˆ©ç”¨ã§ãã‚‹ host-metaã‚’åˆ©ç”¨ã—ãŸç‹¬è‡ªDiscoveryã¨ã€Dynamicã«Clientç™»éŒ²ã®ã—ãã¿ãŒã‚ã‚‹ å‡¦ç†ãƒ•ãƒãƒ¼ OpenID Connect on Web Server Profile ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã¯ã“ã‚“ãªæ„Ÿã˜ã§ã™ãã€‚ ã“ã“ã§ã¯ã€ä¸€ç•ªå‡¦ç†ã®å¤šã„ã‚±ãƒ¼ã‚¹ã‚’è€ƒãˆã¾ã™ã€‚ æ¡ä»¶ã¯
gom68 2012/10/11
openid

oauth
ãƒªãƒ³ã‚¯
Google Launches OAuth 2.0 Playground @ API Evangelist
Google Launches OAuth 2.0 Playground by Kin lane on 11/08/2011 Last March Google started support OAuth 2.0 for all of their APIs, and has been pushing all developers to switch to using OAuth 2.0 in all applications. Today they announced the OAuth 2.0 Playground which allows developers to experiment with APIs using the OAuth 2.0 protocol, and understand how the protocol functions and will make your
gom68 2011/11/09
oauth

google
ãƒªãƒ³ã‚¯
OAuth 2.0ã‹ã‚‰ã®Google+ APIã®ä½¿ã„æ–¹ - r-weblife
è¿½è¨˜ï¼šã“ã®æƒ…å ±ã ã„ã¶å¤ã„ã®ã§æ°—ã‚’ã¤ã‘ã¦ãã ã•ã„ã€‚ ã“ã‚“ã°ã‚“ã¯ã€ritouã§ã™ã€‚ ã‚¿ã‚¤ãƒˆãƒ«ã®é€šã‚Šã€æœ€è¿‘ç™ºè¡¨ã•ã‚ŒãŸã¿ã‚“ãªå¤§å¥½ãGoogle+ã®APIã§ã¯Authorizationéƒ¨åˆ†ã«OAuth 2.0ãŒä½¿ã‚ã‚Œã¦ã„ã¾ã™ã€‚ Getting Started on the Google+ API - Google+ Developers Blog ã•ã£ããå‡ºã¦ããŸå‹•ã‹ã—ã¦ã¿ãŸç³»ã®è¨˜äº‹ã¯API keyã‚’ä½¿ã†æ–¹æ³•ãŒè¼‰ã£ã¦ã„ã¾ã™ã€‚ã¾ããã‚Œã¯ãã‚Œã§ã„ã„ã¨ã—ã¦ã€‚ OAuth 2.0ã®ä»•æ§˜çŸ¥ã£ã¦ã‚‹äººã¯å¿…è¦ãªScopeã¨Endpointã®ä»•æ§˜ãŒåˆ†ã‹ã‚Œã°ã‚‚ã†ã‚µãƒ³ãƒ—ãƒ«ä½œã£ã¦å‹•ã‹ã›ã‚‹ã¨æ€ã†ã®ã§ã€ãã®éƒ¨åˆ†ã‚’ç´¹ä»‹ã—ã¾ã™ã€‚ ãã†ã„ãˆã°æœ€è¿‘ã€"OAuthèªè¨¼"ã‚„ã‚‰"ãƒ¦ãƒ¼ã‚¶ãƒ¼èªè¨¼ã«OAuth"ã£ã¦è¨€è‘‰ã‚’ã‚ˆãèžãã¾ã™ãŒOAuthã®ã©ã“ã«ãã‚“ãªæ©Ÿèƒ½ãŒ(ry 0. OAuth 2.0ã§Google+ APIä½¿ã†ãŸã‚ã®æº–å‚™ ã“ã®è¾ºã‹ã‚‰ã€‚
gom68 2011/09/19
oauth
ãƒªãƒ³ã‚¯
http://www.machu.jp/posts/20110722/p01/
gom68 2011/07/25
openid

oauth

identity

security
ãƒªãƒ³ã‚¯
OAuthã®Scopeã¯ã©ã†ã‚ã‚‹ã¹ãã‹ï¼Ÿ - r-weblife
ã“ã‚“ã°ã‚“ã¯ã€ritouã§ã™ã€‚ ä»Šæ—¥ã€ç™ºè¡¨ã•ã‚ŒãŸTwitterã®Scopeã«ã¤ã„ã¦ã¯ä»–ã®äººãŒãŸãã•ã‚“ãƒ–ãƒã‚°ãªã©æ›¸ã„ã¦ã„ã‚‹ã®ã§çœç•¥ã—ã¾ã™ã€‚ æ°—ãŒã¤ã‘ã°ã€OAuthã®Scopeã«ã¤ã„ã¦ã¯ãšã£ã¨å‰ã‹ã‚‰è€ƒãˆã•ã›ã‚‰ã‚Œã‚‹ã“ã¨ãŒå¤šã‹ã£ãŸã®ã§ã™ã€‚ Y!ã‚„Gã®Scopeã®è¦æ±‚ã®ä»•æ–¹ãŒæ°—ã«ãªã£ãŸã®ã¯2009å¹´æœ€åˆã®ã‚ãŸã‚Šã ã£ãŸã®ã§ã€ã‚‚ã†2å¹´ä»¥ä¸Šã‚‚å‰ã®ã“ã¨ã§ã™ãã€‚ The Scope for OAuth ( ãƒãƒƒãƒˆã‚µãƒ¼ãƒ“ã‚¹ ) - Web Life!!! - Yahoo!ãƒ–ãƒã‚° å°‘ã—æŒ¯ã‚Šè¿”ã£ã¦ã¿ã¾ã—ã‚‡ã†ã€‚ Scopeã®è¦æ±‚æ–¹æ³• ClientãŒServerã«å¿…è¦ãªScopeã‚’æŒ‡å®šã™ã‚‹æ–¹æ³•ã¨ã—ã¦ã€å¤§ããåˆ†ã‘ã¦ï¼’ç¨®é¡žå˜åœ¨ã—ã¾ã™ã€‚ Client ID(Consumer Key)ã‚’å–å¾—ã™ã‚‹ã‚¿ã‚¤ãƒŸãƒ³ã‚°ã§å¿…è¦ãªScopeã‚’æŒ‡å®š AuthZ Requestã‚’é€ã‚‹ã‚¿ã‚¤ãƒŸãƒ³ã‚°ã§å¿…è¦ãªScopeã‚’æŒ‡å®š å‰è€…ã¯ã€Yahoo!ã‚„ãƒ¤ãƒ•ãƒ¼ã‚„ä»¥
gom68 2011/05/24
oauth
ãƒªãƒ³ã‚¯
Easy Rails OAuth Integration Testing
A long while back I wrote a post about Twitter auth integration testing using Cucumber. Back then OAuth was just beginning to see widespread use, but it was nowhere near as popular as it seems to be today. In my latest side project, all logins are from Twitter or Facebook because thereâ€™s simply no need for local accounts (due to the nature of the app). But that also means that we needed an easy wa
gom68 2011/03/20
rails

oauth

capybara

omniauth

test
ãƒªãƒ³ã‚¯
Rack::OAuth2 Sample Server - OAuth.jp
@novã§ã™ã€‚ OAuth 2.0 draft v.13æº–æ‹ ã®Rack::OAuth2 version 0.3.0ã®ãƒªãƒªãƒ¼ã‚¹ã«ã‚ã‚ã›ã¦ã€Rails3ã§Sample Appã‚’ä½œã‚Šã¾ã—ãŸã€‚ http://rack-oauth2-sample.heroku.com Facebookã‚¢ã‚«ã‚¦ãƒ³ãƒˆã§ãƒã‚°ã‚¤ãƒ³ã—ãŸã‚‰ã€ãªã‚“ã¨ãªãã§ä½¿ã„æ–¹åˆ†ã‹ã‚‹ã¨æ€ã„ã¾ã™ã€‚ Access Token or Authorization Codeã‚’å–å¾—ã—ãŸå¾Œã¯ã€ã“ã¡ã‚‰ã®Client Sampleã¿ãŸã„ãªã®ã§ã‚¢ã‚¯ã‚»ã‚¹ã—ã¦ãã ã•ã„ã€‚ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 re
gom68 2011/03/07
rack

oauth

library
ãƒªãƒ³ã‚¯
OAuthãƒ—ãƒãƒˆã‚³ãƒ«ã®ä¸èº«ã‚’ã–ã£ãã‚Šè§£èª¬ã—ã¦ã¿ã‚‹ã‚ˆ - ( ê’ªâŒ“ê’ª) ã‚†ã‚‹ã‚ˆã‚æ—¥è¨˜
ã€ŒãŠãƒ¼ãŠãƒ¼ã£ã™ã£!ã€ ã¦ãªã“ã£ã¦ã€Twitterã®APIã®BASICèªè¨¼ã‚‚6æœˆæœ«ã«çµ‚äº†ã—ã¦OAuth/xAuthã«ç§»è¡Œã™ã‚‹ã¨ã„ã†ã“ã®æ™‚æœŸã«ã€ã‚ã‚‰ãŸã‚ã¦OAuthã«ã¤ã„ã¦å‹‰å¼·ã—ã¦ã¿ãŸã‚“ã§ã™ã®ã‚ˆ? OAuthèªè¨¼ã‚’åˆ©ç”¨ã™ã‚‹ãƒ©ã‚¤ãƒ–ãƒ©ãƒªã¯å„è¨€èªžã§å‡ºãã‚ã£ã¦ãã¦ã‚‹ã®ã§ãã‚Œã‚’ä½¿ãˆã°ã„ã‚“ã˜ã‚ƒã¾ã„ã‹? ã¨ã„ã†ã¨è©±ãŒçµ‚ã‚ã‚‹ã®ã§ã€ã˜ã‚ƒã‚ãã®ãƒ©ã‚¤ãƒ–ãƒ©ãƒªã®ä¸èº«ã¯ãªã«ã‚„ã£ã¦ã‚“ã®ã‚ˆã£ã¦ã“ã¨ã‚’ã€OAuthã™ã‚‹Scalaã®ãƒ©ã‚¤ãƒ–ãƒ©ãƒªä½œã‚ŠãªãŒã‚‰èª¿ã¹ãŸã“ã¨ã‚’ã¾ã¨ã‚ã¦ã¿ã¾ã—ãŸã€‚ é–“é•ã£ã¦ã„ã‚‹ã¨ã“ã‚ã‚‚ã‚ã‚‹ã¨æ€ã†ã®ã§ãƒ„ãƒƒã‚³ãƒŸæ“è¿Žã§ã™ï¼žï¼œ OAuthã£ã¦ãã‚‚ãã‚‚ãªã‚“ãªã®? ã‚‚ã®ã™ã”ãã–ã£ãã‚Šã¨ã„ã†ã¨ã€ŒAPIåˆ©ç”¨å´ãŒã€ãƒ¦ãƒ¼ã‚¶èªè¨¼ã‚’APIæä¾›ã‚µãƒ¼ãƒ“ã‚¹å´ã«ã‚„ã£ã¦ã‚‚ã‚‰ã†ãŸã‚ã®ä»•æ§˜ã€ã£ã¦æ„Ÿã˜ã§ã—ã‚‡ã†ã‹? BASICèªè¨¼ã®å ´åˆã€APIåˆ©ç”¨å´ãŒèªè¨¼ã«å¿…è¦ãªã‚¢ã‚«ã‚¦ãƒ³ãƒˆã‚„ãƒ‘ã‚¹ãƒ¯ãƒ¼ãƒ‰ã‚’é ã‹ã‚‹å¿…è¦ãŒã‚ã‚‹ã‚ã‘ã§ã™ã€‚æ‚ªæ„ã®ã‚ã‚‹APIåˆ©ç”¨å´ãŒã€Œãªã‚“ã¨ã‹ãƒ¡ãƒ¼ã‚«ãƒ¼
gom68 2010/12/10
oauth
ãƒªãƒ³ã‚¯
OAuthã¨å‘¨è¾ºæŠ€è¡“ã®å‹‰å¼·ä¼š â€” ã‚ã‚Šãˆã‚‹ãˆã‚Šã‚
OAuthã®å…¸åž‹çš„ã‚·ãƒŠãƒªã‚ª userãŒconsumer(Webä¸Šã®ã‚µãƒ¼ãƒ“ã‚¹)ã‚’åˆ©ç”¨ userã¯SP(åˆ¥ã®Webä¸Šã®ã‚µãƒ¼ãƒ“ã‚¹)ã«ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã‚’æŒã£ã¦ã„ã‚‹ SPã¯ä¸€èˆ¬ã«SNSã§ã€userãŒSPä¸Šã«è“„ç©ã—ãŸæƒ…å ±(å€‹äººãƒ—ãƒãƒ•ã‚¡ã‚¤ãƒ«ã‚„å‹é”ãƒªã‚¹ãƒˆãªã©)ã¯åŽŸå‰‡çš„ã«SPã®å¤–éƒ¨ã«éžå…¬é–‹ consumerã¯ã€userã«è¨±å¯ã‚’å¾—ã¦ã€SPä¸Šã®æƒ…å ±ã‚’å–å¾—ã™ã‚‹ ãŸã ã—ã€userã¯consumerã«SPã®ãƒ‘ã‚¹ãƒ¯ãƒ¼ãƒ‰ã¯æ•™ãˆãªã„ OAuth 1.0aã®å‹•ä½œã‚·ãƒ¼ã‚±ãƒ³ã‚¹ è¡¨è¨˜æ³• ãƒªã‚¯ã‚¨ã‚¹ãƒˆã¨ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã®åŒºåˆ¥ã¯è‡ªæ˜Žã§ã™ãŒã€ã²ã¨ã‚ã§åˆ†ã‹ã‚‹ã‚ˆã†ã«ãƒªã‚¯ã‚¨ã‚¹ãƒˆã¯ --> ã€ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã¯ ==> ã«ã—ã¦ã„ã¾ã™ã€‚ ãƒªã‚¯ã‚¨ã‚¹ãƒˆã‚„ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒšã‚¢ã®ä¸Šã«æ›¸ã„ã¦ã‚ã‚‹æ•°å—ã¯OAuth1.0aã‚¹ãƒšãƒƒã‚¯ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ç•ªå·ã§ã™ã€‚ãƒªã‚¯ã‚¨ã‚¹ãƒˆãƒ‘ãƒ©ãƒ¡ãƒ¼ã‚¿ã‚„ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã®å†…å®¹ã¯ã‚¹ãƒšãƒƒã‚¯ã®è©²å½“ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã‚’å‚ç…§ã—ã¦ãã ã•ã„ã€‚ ãƒªã‚¯ã‚¨ã‚¹ãƒˆã‚„ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒšã‚¢ã®ä¸‹ã«æ›¸ã„ã¦ã‚ã‚‹æ–‡å—åˆ—ã¯
gom68 2010/11/16
oauth
ãƒªãƒ³ã‚¯
2-legged OAuth for the OpenSocial REST API - Internet Identity Research
With version .8 of the OpenSocial standard, support was added for REST APIs.Â The authentication mechanism chosen for those APIs was OAuth.Â However, there are two flavors of OAuth, and this document attempts to explain the different use cases that they support in OpenSocial, as well as why the "2-legged" variant of OAuth is likely to be more important for most OpenSocial containers to support fir
gom68 2010/11/10
oauth

opensocial
ãƒªãƒ³ã‚¯
The OAuth 1.0 Protocol
The OAuth 1.0 Protocol draft-hammer-oauth-10 Abstract OAuth ã¯ã€ãƒªã‚½ãƒ¼ã‚¹ã‚ªãƒ¼ãƒŠãƒ¼ (åˆ¥ã®ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚„ã‚¨ãƒ³ãƒ‰ãƒ¦ãƒ¼ã‚¶ãƒ¼) ã«ä»£ã‚ã£ã¦ã€ã‚µãƒ¼ãƒãƒ¼ãƒªã‚½ãƒ¼ã‚¹ã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ãŸã‚ã®æ–¹æ³•ã‚’ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«æä¾›ã™ã‚‹ã‚‚ã®ã§ã‚ã‚‹ã€‚ã¾ãŸã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’åˆ©ç”¨ã™ã‚‹ã“ã¨ã§ã€ã‚¨ãƒ³ãƒ‰ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«ãƒ¦ãƒ¼ã‚¶åã‚„ãƒ‘ã‚¹ãƒ¯ãƒ¼ãƒ‰ã‚’å…±æœ‰ã™ã‚‹ã“ã¨ãªãã€ã‚µãƒ¼ãƒãƒ¼ãƒªã‚½ãƒ¼ã‚¹ã¸ã®ç¬¬ä¸‰è€…ã‚¢ã‚¯ã‚»ã‚¹ã‚’èªå¯ã™ã‚‹ã“ã¨ãŒã§ãã‚‹ã€‚ Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCPÂ 78 and BCPÂ 79. Internet-Drafts are working documents of the Internet Engineering T
gom68 2010/11/10
OAuth1.0ä»•æ§˜æ›¸æ—¥æœ¬èªžè¨³

oauth
ãƒªãƒ³ã‚¯
OAuth Core 1.0
ï»¿ This specification was obsoleted by OAuth Core 1.0 Revision A on June 24th, 2009 to address a session fixation attack. The OAuth Core 1.0 Revision A specification is being obsoleted by the proposed IETF draft draft-hammer-oauth. The draft is currently pending IESG approval before publication as an RFC. Implementers should use RFC 6749: The OAuth 2.0 Authorization Framework instead of this specif
gom68 2010/11/09
oauth
ãƒªãƒ³ã‚¯
RFC 5849: The OAuth 1.0 Protocol
Internet Engineering Task Force (IETF) E. Hammer-Lahav, Ed. Request for Comments: 5849 April 2010 Category: Informational ISSN: 2070-1721 The OAuth 1.0 Protocol Abstract OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end- user). It also provides a process for end-users to authorize third- party access to their server r
gom68 2010/11/09
oauth

rfc
ãƒªãƒ³ã‚¯
1 2 æ¬¡ã®ãƒšãƒ¼ã‚¸