![require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages](https://cdn.sanity.io/images/cgdhsj6q/production/be8ab80c8efa5907bc341c6fefe9aa20d239d890-1600x1097.png?w=400&fit=max&auto=format)
Security News
require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
@simonhaenisch/koa-shopify-auth
Advanced tools
Middleware to authenticate a [Koa](http://koajs.com/) application with [Shopify](https://www.shopify.ca/).
Middleware to authenticate a Koa application with Shopify.
Same as @shopify/koa-shopify-auth
but with some fixes and improvements so that it kind of works. Sadly it seems the Shopify team doesn't care much about community contributions, often not even leaving a comment (see #791, #1099, #1148, #1359 or #1407). They also don't seem to follow semver so well (see #1498 (comment)).
Important: the verifyToken
cookie fix requires a secure context for the cookies to work (see https://github.com/pillarjs/cookies#secure-cookies), which means that you'll have to set koa.proxy = true
(see koa docs); that will make koa trust proxy-related headers, which is needed so that koa makes the context secure for requests to relative paths like /api/auth
. For development you'll have to use a tool like cloudflared
or ngrok
to proxy a secure connection to http://localhost
.
Fixes:
prefix
works for all routes (08f2c56)verifyToken
properly redirects to auth if the token has expired (43b51a6)shop
query param everywhere (bb860f0)verifyToken
also sets same-site cookie options for Chrome (5079bee)StorageAccessHelper
from prematurely redirecting to the appTargetUrl
instead of authentication (b311479)Features:
appTargetUrl
option and join paths more safely (43aee2f)$ npm install @simonhaenisch/koa-shopify-auth
This package exposes shopifyAuth
by default, and verifyRequest
as a named export.
import shopifyAuth, {verifyRequest} from '@shopify/koa-shopify-auth';
Returns an authentication middleware taking up (by default) the routes /auth
and /auth/callback
.
app.use(
shopifyAuth({
// if specified, mounts the routes off of the given path
// eg. /shopify/auth, /shopify/auth/callback
// defaults to ''
prefix: '/shopify',
// your shopify app api key
apiKey: SHOPIFY_API_KEY,
// your shopify app secret
secret: SHOPIFY_SECRET,
// scopes to request on the merchants store
scopes: ['write_orders, write_products'],
// set access mode, default is 'online'
accessMode: 'offline',
// callback for when auth is completed
afterAuth(ctx) {
const {shop, accessToken} = ctx.session;
console.log('We did it!', accessToken);
ctx.redirect('/');
},
}),
);
/auth
This route starts the oauth process. It expects a ?shop
parameter and will error out if one is not present. To install it in a store just go to /auth?shop=myStoreSubdomain
.
/auth/callback
You should never have to manually go here. This route is purely for shopify to send data back during the oauth process.
Returns a middleware to verify requests before letting them further in the chain.
app.use(
verifyRequest({
// path to redirect to if verification fails
// defaults to '/auth'
authRoute: '/foo/auth',
// path to redirect to if verification fails and there is no shop on the query
// defaults to '/auth'
fallbackRoute: '/install',
}),
);
import 'isomorphic-fetch';
import Koa from 'koa';
import session from 'koa-session';
import shopifyAuth, {verifyRequest} from '@shopify/koa-shopify-auth';
const {SHOPIFY_API_KEY, SHOPIFY_SECRET} = process.env;
const app = new Koa();
app.keys = [SHOPIFY_SECRET];
app
// sets up secure session data on each request
.use(session({ secure: true, sameSite: 'none' }, app))
// sets up shopify auth
.use(
shopifyAuth({
apiKey: SHOPIFY_API_KEY,
secret: SHOPIFY_SECRET,
scopes: ['write_orders, write_products'],
afterAuth(ctx) {
const {shop, accessToken} = ctx.session;
console.log('We did it!', accessToken);
ctx.redirect('/');
},
}),
)
// everything after this point will require authentication
.use(verifyRequest())
// application code
.use(ctx => {
ctx.body = '🎉';
});
This app uses fetch
to make requests against shopify, and expects you to have it polyfilled. The example app code above includes a call to import it.
Though you can use shopifyAuth
without a session middleware configured, verifyRequest
expects you to have one. If you don't want to use one and have some other solution to persist your credentials, you'll need to build your own verifiction function.
By default this app requires that you use a myshopify.com
host in the shop
parameter. You can modify this to test against a local/staging environment via the myShopifyDomain
option to shopifyAuth
(e.g. myshopify.io
).
FAQs
Middleware to authenticate a [Koa](http://koajs.com/) application with [Shopify](https://www.shopify.ca/).
We found that @simonhaenisch/koa-shopify-auth demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.