OAuth 2.0 for Browser-Based Apps Abstract This specification details the security considerations and best practices that must be taken into account when developing browser-based applications that use OAuth 2.0.¶ Discussion Venues This note is to be removed before publishing as an RFC.¶ Discussion of this document takes place on the Web Authorization Protocol Working Group mailing list (oauth@ietf.
You probably do not need OAuth2, nor OpenID Connect. This is a controversial opinion, even more so because my biggest professional achievements are two of the most successful open source projects in the OAuth2 and OpenID Connect world: Ory Hydra (started in 2015)Ory Fosite (started in 2016)Those two projects helped spawn a company that raised series A and an open source ecosystem used by millions.
What is XYZ?XYZ is a set of implementations of the Grant Negotiation Authorization Protocol (GNAP), a draft delegation protocol being developed in the spirit of OAuth 2, but designed with the decade of experience that we have now with OAuth 2 and its extensions. XYZ used to be the name of a proposed protocol that was published as an individual draft, but this proposal has been superseded by GNAP.
ãµã¼ãã¼ã¯ãåãåã£ãã¯ã©ã¤ã¢ã³ã証ææ¸ã®ä¸»ä½èå¥æ å ±ãäºåç»é²ããã¦ãããã®ã¨ä¸è´ãããã¨ã確èªãããã£ã¦ã¯ã©ã¤ã¢ã³ãèªè¨¼ã¨ãã¾ãã ãã®ã¯ã©ã¤ã¢ã³ãèªè¨¼æ¹å¼ã«ã¯ tls_client_auth ã¨ããååãä¸ãããã¦ãã¾ãï¼MTLS, 2.1.1. PKI Method Metadata Valueï¼ã ãªããã¯ã©ã¤ã¢ã³ã証ææ¸ã«ã¯ OAuth 2.0 ã®æèã«ãããã¯ã©ã¤ã¢ã³ã ID ã¯å ¥ã£ã¦ããªãã®ã§ãã¯ã©ã¤ã¢ã³ã証ææ¸ã ãã§ã¯ã¯ã©ã¤ã¢ã³ããç¹å®ãããã¨ã¯ã§ãã¾ããããã®ãããã¯ã©ã¤ã¢ã³ã証ææ¸ãç¨ããã¯ã©ã¤ã¢ã³ãèªè¨¼ããããªãéã¯ãå¥éã¯ã©ã¤ã¢ã³ã ID ããªã¯ã¨ã¹ãã«å«ããå¿ è¦ãããã¾ããé常㯠client_id ãªã¯ã¨ã¹ããã©ã¡ã¼ã¿ã¼ã使ç¨ããã¾ãã 1.8. self_signed_tls_client_auth ã¯ã©ã¤ã¢ã³ã証ææ¸ãç¨ããã¯ã©ã¤ã¢ã³ãèªè¨¼ã«ããã¦ãPKI
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}