Gitbook
developer.gitbook.com › visitor-authentication › guides › custom-backend › implement-visitor-authentication-using-node
Implement Visitor Authentication using Node | GitBook Developer Documentation
May 23, 2024 - Your authentication server can now check the value of this field, and handle it accordingly: ... app.get('/', (req, res) => { const customerInfo = req.query.space === 'customer-a' ? CUSTOMER_A : CUSTOMER_B; const token = jwt.sign({}, customerInfo.jwtSigningKey, { expiresIn: '1h' }); const redirectURL = `${customerInfo.url}/${req.query.location || ''}?jwt_token=${token}`; res.redirect(redirectURL); }); Visitor Authentication works well with custom domains.
Gitbook
developer.gitbook.com › getting-started › guides › implement-visitor-authentication-using-node
Implement Visitor Authentication using Node - GitBook Integration Platform
Once you've created the key, you need to include it as the value of a query parameter named jwt_token the URL of the GitBook content you wish the user to have access to (see redirectURL) Here's a very simple Express application for signing keys and redirecting users: ... Finally, within link and domain settings in the visibility menu, you can configure a fallback URL. When someone directly accesses your space without the necessary token, GitBook uses the fallback URL to redirect the visitor to a custom URL so that you can authenticate them.
Forked by 2 users
Languages: TypeScript 75.7% | CSS 14.1% | JavaScript 10.2%
Starred by 10 users
Forked by 3 users
Languages: JavaScript 100.0% | JavaScript 100.0%
GitBook
gitbook.com › docs › guides › docs-personalization-and-authentication › how-to-personalize-your-gitbook-site-using-auth0-and-adaptive-content
How to personalize your GitBook site using Auth0 and adaptive content | Guides | GitBook Documentation
December 17, 2025 - Back in GitBook, enable the toggle labeled Include claims in JWT token, then click Save. Finally, head to the Audience tab in your site settings. Under Access, choose Authenticated Access, and select Auth0 from the dropdown.
GitBook
gitbook.com › docs › developers › gitbook-api › authentication
Authentication | Developers | GitBook Documentation
March 20, 2025 - You can view and manage your access tokens in the Developer settings of your GitBook user account. API requests are authenticated using the Bearer Auth scheme.
GitBook
gitbook.com › docs › publishing-documentation › visitor-authentication › setting-up-oidc
Setting up OIDC | GitBook Documentation
March 25, 2025 - So, entering the least permissive scope is the best security recommendation. ... Now, in GitBook, close the integrations modal and click on the Manage site button. Navigate to Audience, select Visitor Authentication, and choose OIDC as the backend.
GitBook
gitbook.com › docs › guides › docs-personalization-and-authentication › setting-up-adaptive-content
How to personalize your GitBook site using cookies and adaptive content | Guides | GitBook Documentation
December 17, 2025 - In order to pass data securely through a cookie, you’ll need to send the data as a JSON Web Token from your application in a cookie named gitbook-visitor-token tied to your domain.
GitBook
gitbook.com › docs › site-access › authenticated-access
Authenticated access | GitBook Documentation
April 23, 2026 - Authenticated access allows you to publish your content while requiring authentication from any visitors who want to view it.