From b9a55f45102040b6d7783693742e357c68c2af60 Mon Sep 17 00:00:00 2001
From: Om Shivaprasad Wanere <omwanere593@gmail.com>
Date: Tue, 30 Dec 2025 14:48:48 +0530
Subject: [PATCH 1/2] Update OAuth proxy documentation to remove deprecated
 Heroku service

---
 README.md | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index d4a5f743..e9ca0bb0 100644
--- a/README.md
+++ b/README.md
@@ -891,19 +891,29 @@ A list of the service providers OAuth* mechanisms is available at <a href="http:
 For providers which support only OAuth1 or OAuth2 with Explicit Grant, the authentication flow needs to be signed with a secret key that may not be exposed in the browser. HelloJS gets round this problem by the use of an intermediary webservice defined by `oauth_proxy`. This service looks up the secret from a database and performs the handshake required to provision an `access_token`. In the case of OAuth1, the webservice also signs subsequent API requests.
 
 
-**Quick start:** Register your Client ID and secret at the OAuth Proxy service, [Register your App](https://auth-server.herokuapp.com/)
+**Quick start:**  
+The previously used OAuth Proxy service hosted on Heroku is no longer available,
+as Heroku free hosting has been discontinued.
 
+To get started, you can run an OAuth proxy locally using
+[node-oauth-shim](https://npmjs.org/package/oauth-shim).
+
+Once running, override the default `oauth_proxy` in the HelloJS client script
+using `hello.init`, like so:
 
-The default proxy service is [https://auth-server.herokuapp.com/](https://auth-server.herokuapp.com/). Developers may add their own network registration Client ID and secret to this service in order to get up and running.
-Alternatively recreate this service with [node-oauth-shim](https://npmjs.org/package/oauth-shim). Then override the default `oauth_proxy` in HelloJS client script in `hello.init`, like so...
 
 ```javascript
 hello.init(
 	CLIENT_IDS,
 	{
-		oauth_proxy: 'https://auth-server.herokuapp.com/proxy'
+		oauth_proxy: 'http://localhost:5500/proxy'
 	}
 )
+⚠️ Note:
+Make sure the OAuth proxy is running locally before initializing HelloJS.
+You can customize the proxy URL if hosting the service elsewhere.
+
+
 ```
 
 ### Enforce Explicit Grant

From 322a0c16651415f228e40e9cab0167cab9717010 Mon Sep 17 00:00:00 2001
From: Om Shivaprasad Wanere <omwanere593@gmail.com>
Date: Tue, 30 Dec 2025 14:55:19 +0530
Subject: [PATCH 2/2] Remove deprecated Heroku OAuth proxy fallback

---
 src/hello.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/hello.js b/src/hello.js
index 754ab912..b2eb6940 100644
--- a/src/hello.js
+++ b/src/hello.js
@@ -64,7 +64,7 @@ hello.utils.extend(hello, {
 		// OAuth1 shim
 		// The path to the OAuth1 server for signing user requests
 		// Want to recreate your own? Checkout https://github.com/MrSwitch/node-oauth-shim
-		oauth_proxy: 'https://auth-server.herokuapp.com/proxy',
+		oauth_proxy: 'https://localhost:5500/proxy',
 
 		// API timeout in milliseconds
 		timeout: 20000,