branch: externals/url-http-oauth-demo
commit 8ba62b2072e1d884dcf4a1fb22d0c8aaf3c2376b
Author: Thomas Fitzsimmons <fitz...@fitzsim.org>
Commit: Thomas Fitzsimmons <fitz...@fitzsim.org>
Update a comment
* url-http-oauth-demo.el: Update a comment.
---
url-http-oauth-demo.el | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/url-http-oauth-demo.el b/url-http-oauth-demo.el
index d0a0125282..56697b5138 100644
--- a/url-http-oauth-demo.el
+++ b/url-http-oauth-demo.el
@@ -101,23 +101,24 @@
;;; Code:
(require 'url-http-oauth)
-;;; Tell Emacs that "https://meta.sr.ht/query"; uses OAuth 2.0 for
-;;; authentication and authorization.
+;;; Tell Emacs that the URL "https://meta.sr.ht/query";, with
+;;; client-identifier "107ba4a9-2a96-4420-8818-84ec1f112405", uses
+;;; OAuth 2.0 for authentication and authorization.
;;;###autoload
(url-http-oauth-interpose
+ '(;; This is the client identifier, which can be generated by the
+ ;; user, or by the Emacs library developer, at
+ ;; "https://meta.sr.ht/oauth2/client-registration";.
+ ("client-identifier" "107ba4a9-2a96-4420-8818-84ec1f112405")
;; This is the URL at which the `url-http-oauth-demo' package will
;; access resources. Everything that follows is for authentication
;; and authorization to satisfy OAuth 2.0 requirements.
- '(("url" "https://meta.sr.ht/query";)
+ ("url" "https://meta.sr.ht/query";)
;; These are the authorization and token endpoints, published in
;; "https://man.sr.ht/meta.sr.ht/oauth.md";. There is no way to
;; autodiscover them from "https://meta.sr.ht/query";.
("authorization-endpoint" "https://meta.sr.ht/oauth2/authorize";)
("access-token-endpoint" "https://meta.sr.ht/oauth2/access-token";)
- ;; This is the client identifier, which can be generated by the user,
- ;; or by the Emacs library developer, at
- ;; "https://meta.sr.ht/oauth2/client-registration";.
- ("client-identifier" "107ba4a9-2a96-4420-8818-84ec1f112405")
;; This is the list of features to which Emacs is requesting the
;; server grant it access.
("scope" "meta.sr.ht/PROFILE:RO")
@@ -126,9 +127,9 @@
;; "https://meta.sr.ht/oauth2/client-registration";. If the user
;; generates the client secret, they should note it down. If the
;; Emacs library developer generates it, they should make it
- ;; available to the users of their library somehow. In either case,
- ;; Emacs will prompt for it, and store it, ideally GPG-encrypted,
- ;; using `auth-source'. An example, no-longer-active client secret
+ ;; available to the users of their library somehow. In either
+ ;; case, Emacs will prompt for it, and store it, ideally
+ ;; GPG-encrypted, using `auth-source'. An example client secret
;; string is "CeuivTBzZbqJ4iTc+VEdPZJODkBHhuCj4bIqQQAONYaOUGubNM0yG
;; ZU3P7ant959W1RkzgvXSeNf2mdxuk5EfA==". The user would paste this
;; 88 character client secret string into the minibuffer when
