Firebase adapter
Introduction
Adapter plug-in for NextAuth.js to use custom token method authentication. It is currently intended for Firestore Database, and will add a Realtime Database adapter later. Firebase can handle the database in the client, but there is not enough providers for authentication provided by Firebase. This package allows you to create rules in Firebase using credentials from various OAuth providers in NextAuth, and allows you to use Firebase in the client while the database is protected. Examples of use can be found here.
How to start
Installation
This module is built for NextAuth.js v4. And, the Firebase admin SDK is used for storing NextAuth.js data, and the Firebase SDK is also required to access it from the client. Install NextAuth.js and Firebase Admin SDK as required, and install Firebase SDK depending on whether the client uses Firebase.
npm i @lowfront/firebase-adapter
Register NextAuth.js
The server uses the Firebase admin SDK. Initialize the app and db as follows:
import { FirestoreAdapter } from "@lowfront/firebase-adapter";
import admin from 'firebase-admin';
import { getFirestore } from 'firebase-admin/firestore';
const app = admin.initializeApp({
credential: admin.credential.cert({...} as ServiceAccount),
});
const db = getFirestore(app);
export default NextAuth({
providers: [
GoogleProvider({
clientId: process.env.GOOGLE_ID,
clientSecret: process.env.GOOGLE_SECRET,
}),
],
adapter: FirestoreAdapter(db),
})
Register custom token API entry point
Endpoint for requesting the client to issue a cutomToken. You must use /api/auth/firebase-cutom-token
as the endpoint.
import { createFirebaseCustomTokenHandler } from "@lowfront/firebase-adapter";
export default createFirebaseCustomTokenHandler({
db,
});
Set Firestore Database Rule
Set a rule in the client that allows users to access only their own data. If you do not set a rule, all data in the database can be accessed by the client, so it must be set.
rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
match /{document=**} {
allow read, write: if false;
}
match /store/{userId}/{document=**} {
allow read, write: if request.auth.uid == userId
// This line adds a read cost, but disables customToken issued after sign out.
&& exists(/databases/$(database)/documents/_next_auth_firebase_adapter_/store/customToken/$(request.auth.token.sessionToken));
}
}
}
Example of using the client
Unlike servers, the client uses the Firebase SDK to access the database. So, initialize the app with Firebase config and pass the db object to the function provided by the package for use it. The CRUD function (setDoc, addDoc, getDoc, updateDoc, removeDoc...) in Firebase v9 must use the functions wrapped in the package. The wrapper functions have the same signature as Firebase SDK v9.
import { getUserDoc, getDoc, addDoc, getDoc, getDocs, setDoc, updateDoc, deleteDoc } from '@lowfront/firebase-adapter';
const firebaseConfig = { ... } as FirebaseOptions;
const app = initializeApp(firebaseConfig);
const db = getFirestore(app);
const testDoc = getUserDoc(db, session?.user?.email, 'store', 'test');
const App: FC<{}> = () => {
const { data: session } = useSession();
const loadData = async () => {
await getDoc(testDoc);
alert('success load data');
};
return <div>
<button onClick={loadData}>Load data</button>
</div>
};