@eventcatalog/core 3.35.0 → 3.36.1

package/dist/docs/development/authentication/01-introduction.md

@@ -0,0 +1,78 @@
+---
+sidebar_position: 1
+keywords:
+- EventCatalog components
+sidebar_label: Introduction
+title: Introduction
+description: Introduction to EventCatalog Authentication
+---
+
+import AddedIn from '@site/src/components/MDX/AddedIn';
+import EventCatalogPro from '@site/src/components/MDX/EventCatalogPro';
+
+# Authentication Guide
+
+<EventCatalogPro />
+<AddedIn version="2.43.0" />
+
+
+EventCatalog provides secure authentication to control access to your event-driven architecture documentation. Whether you're a small team getting started or a large enterprise with complex identity requirements, EventCatalog's flexible authentication system grows with your needs.
+
+<iframe width="100%" height="455" src="https://www.youtube.com/embed/OVbXNP0Ns_U?si=TagMKL49ZD_G_HYE" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+
+
+
+
+## How it works
+
+EventCatalog uses industry-standard **OpenID Connect (OIDC)** and **OAuth 2.0** protocols to integrate with your identity provider. Here's the authentication flow:
+
+1. **User visits EventCatalog** and attempts to access protected documentation
+2. **Redirected to your identity provider** (GitHub, Google, Auth0, etc.)
+3. **User authenticates** with their existing credentials
+4. **Provider confirms identity** and sends user back to EventCatalog
+5. **User gains access** to your documentation and architecture
+
+![Authentication](./img/auth.png)
+
+EventCatalog runs in **SSR mode** to handle authentication sessions and uses [Auth.js](https://authjs.dev/) to manage the authentication flow securely.
+
+## Authentication by Plan
+
+EventCatalog Authentication is a **paid feature** available in Scale and Enterprise plans.
+
+#### Scale Plan
+Perfect for growing teams that need secure collaboration with popular business providers:
+
+- **GitHub** - Ideal for development teams already using GitHub
+<!-- - **Google** - For teams using Gmail and Google Workspace -->
+
+#### Enterprise Plan
+Designed for large organizations with dedicated identity management systems:
+
+- **Microsoft Azure AD (Entra ID)** - For organizations using Office 365 and Azure
+- **Auth0** - Developer-friendly identity platform with advanced features
+- **Okta** - Popular enterprise identity platform with custom claims
+- **Custom OIDC** - Contact us to add your provider at [hello@eventcatalog.cloud](mailto:hello@eventcatalog.cloud)
+
+## Why EventCatalog Authentication?
+
+- ✅ **No new passwords** - Users authenticate with accounts they already have
+- ✅ **Secure by default** - Leverage enterprise-grade security from major providers
+- ✅ **Single sign-on experience** - Seamless access across your tools
+- ✅ **Centralized management** - Control access through your existing identity systems
+- ✅ **Team collaboration** - Secure access for distributed teams
+
+## Getting Started
+
+Ready to secure your EventCatalog with authentication?
+
+**New to EventCatalog?** Start your **14-day free trial** at [EventCatalog.cloud](https://eventcatalog.cloud) to explore all authentication features.
+
+## Next steps
+
+Ready to get started? Let's enable authentication in your EventCatalog project:
+
+→ [Enabling Authentication](/docs/development/authentication/enabling-authentication)
+
+**Questions?** Join our [Discord community](https://discord.gg/eventcatalog) for support and guidance.

package/dist/docs/development/authentication/02-enabling-authentication.md

@@ -0,0 +1,152 @@
+---
+sidebar_position: 1
+keywords:
+- EventCatalog authentication
+sidebar_label: Enabling authentication
+title: Enabling authentication
+description: Enabling authentication for EventCatalog
+---
+
+import AddedIn from '@site/src/components/MDX/AddedIn';
+import PlanBanner from '@site/src/components/MDX/PlanBanner';
+import { Card, CardGrid, GitHubIcon, OktaIcon, AzureIcon, GoogleIcon, Auth0Icon, GitLabIcon } from '@site/src/components/MDX/Card';
+
+<AddedIn version="2.43.0" />
+<PlanBanner plan="Scale" />
+
+To enable authentication for your site, you will need to do three things:
+
+1. [Setup Environment](#setup-environment)
+1. [Enable EventCatalog Server Side Rendering (SSR)](#enable-eventcatalog-server-side-rendering-ssr)
+1. [Create your `eventcatalog.auth.js` file](#create-your-eventcatalogauthjs-file)
+
+:::info Authentication is a paid feature
+Authentication is a paid feature, and is available on EventCatalog Scale and Enterprise plans.
+
+You can get a 14 day free trial of EventCatalog Scale and Enterprise [here](https://www.eventcatalog.dev/pricing).
+
+You will need to set your license key in your `.env` file.
+
+```env title=".env"
+EVENTCATALOG_LICENSE_KEY=your-license-key
+```
+:::
+
+### Setup Environment
+
+EventCatalog uses [Auth.js](https://authjs.dev/) to handle the authentication flow.
+
+Auth.js libraries require you to set an `AUTH_SECRET` environment variable. This is used to encrypt cookies and tokens. It should be a cryptographically secure random string of at least 32 characters:
+
+This is the only strictly required environment variable. It is the secret used to encode the JWT and encrypt things in transit. We recommend at least a 32 character random string. This can be generated via openssl with `openssl rand -base64 33`.
+
+```env title=".env"
+AUTH_SECRET=your-secret
+```
+
+#### AUTH_TRUST_HOST
+
+When running EventCatalog behind a reverse proxy (Kubernetes/AKS, Nginx, Cloudflare, AWS ALB, etc.), you must set `AUTH_TRUST_HOST=true`. Without it, Auth.js falls back to the internal container URL (e.g. `http://localhost:3000`) instead of the real domain, which causes login and sign-out to fail with CSRF/cross-site errors such as "Cross-site POST form submissions are forbidden".
+
+```env title=".env"
+AUTH_TRUST_HOST=true
+```
+
+Setting this tells Auth.js to trust the `x-forwarded-host` and `x-forwarded-proto` headers forwarded by your proxy so it can resolve the correct callback URL.
+
+:::tip Vercel and Cloudflare Pages
+You do not need to set `AUTH_TRUST_HOST` when deploying to Vercel or Cloudflare Pages - it is inferred automatically. It is also not required in local development.
+:::
+
+To learn more, refer to the [Auth.js deployment documentation](https://authjs.dev/getting-started/deployment#auth_trust_host).
+
+
+### Enable EventCatalog Server Side Rendering (SSR)
+
+Authentication requires EventCatalog to be SSR enabled. This is because EventCatalog needs to be able to access the user's session to determine if they are authenticated.
+
+To enable SSR, you will need to add the following to your `eventcatalog.config.js` file:
+
+```js title="eventcatalog.config.js"
+module.exports = {
+  // ... other config options
+  output: 'server',
+};
+```
+
+This will ensure that EventCatalog is rendered on the server side, and that the user's session is available to the client.
+
+:::info Deploying EventCatalog in SSR mode
+You will be running EventCatalog in SSR mode when you deploy your site. This means the output of your site will require a server to be running. You can use EventCatalog Docker file to deploy your site or read our [deployment guide](https://www.eventcatalog.dev/docs/deployment/overview) for more information.
+:::
+
+### Create your `eventcatalog.auth.js` file
+
+The `eventcatalog.auth.js` file is used to configure the authentication for your site, and is created in the root of your EventCatalog project.
+
+```js title="eventcatalog.auth.js"
+module.exports = {
+  // Enable debug mode for development
+  debug: false,
+  // List of providers you want to enable
+  providers: {
+    github: {
+      clientId: process.env.GITHUB_CLIENT_ID,
+      clientSecret: process.env.GITHUB_CLIENT_SECRET,
+    },
+  },
+  // Optional session configuration
+  session?: {
+    // 30 days default
+    maxAge?: number;
+  };
+};
+```
+
+Once you have these three things, you can start setting up your authentication providers.
+
+### Setting up your authentication providers
+
+EventCatalog supports a range of authentication providers, and you can find the documentation for each provider below.
+
+<CardGrid columns={2}>
+  <Card
+    title="Setting up GitHub"
+    icon={<GitHubIcon />}
+    badge="Scale"
+    href="/docs/development/authentication/providers/setting-up-github"
+  />
+  <Card
+    title="Setting up Google"
+    icon={<GoogleIcon />}
+    badge="Scale"
+    href="/docs/development/authentication/providers/setting-up-google"
+  />
+  <Card
+    title="Setting up Azure AD"
+    icon={<AzureIcon />}
+    badge="Enterprise"
+    href="/docs/development/authentication/providers/setting-up-azure-ad"
+  />
+  <!-- <Card
+    title="Setting up Google"
+    icon={<GoogleIcon />}
+    href="/docs/auth/google"
+  /> -->
+  
+  <Card
+    title="Setting up Okta"
+    icon={<OktaIcon />}
+    href="/docs/development/authentication/providers/setting-up-okta"
+    badge="Enterprise"
+  />
+  <Card
+    title="Setting up Auth0"
+    icon={<Auth0Icon />}
+    href="/docs/development/authentication/providers/setting-up-auth0"
+    badge="Enterprise"
+  />
+</CardGrid>
+
+Missing a provider? [Let us know](https://github.com/event-catalog/eventcatalog/issues/new) and we'll add it to the list.
+

package/dist/docs/development/authentication/07-rbac-middleware.md

@@ -0,0 +1,269 @@
+---
+sidebar_position: 7
+keywords:
+- EventCatalog RBAC
+- Role-based access control
+- Middleware
+- Custom authentication
+- Access control
+sidebar_label: Role-Based Access Control
+title: RBAC Middleware
+description: Implementing role-based access control with custom middleware in EventCatalog
+---
+
+import AddedIn from '@site/src/components/MDX/AddedIn';
+import PlanBanner from '@site/src/components/MDX/PlanBanner';
+
+<AddedIn version="2.44.0" />
+<PlanBanner plan="Enterprise" />
+
+# Role-Based Access Control (RBAC) Middleware
+
+EventCatalog supports **Role-Based Access Control (RBAC)** through custom middleware, allowing you to control user access to specific pages and sections based on their roles and groups.
+
+## How it works
+
+The RBAC middleware integrates with EventCatalog's authentication system to provide fine-grained access control:
+
+1. **User authenticates** through your configured identity provider
+2. **Middleware evaluates** the user's roles and groups against defined access rules
+3. **Access is granted or denied** based on the matching rules for the requested path
+4. **User sees appropriate content** or receives a 403 Forbidden response
+
+## Prerequisites
+
+Before setting up RBAC middleware, ensure you have:
+
+- ✅ [Authentication enabled](/docs/development/authentication/enabling-authentication) in your EventCatalog
+- ✅ An authentication provider configured (GitHub, Google, Azure AD, etc.)
+- ✅ User roles and groups configured in your identity provider
+
+## Setting up RBAC Middleware
+
+### 1. Create the middleware file
+
+Create a `middleware.ts` file in the root of your EventCatalog project:
+
+```typescript title="middleware.ts"
+import type { MiddlewareHandler } from 'astro';
+
+interface Locals {
+  hasRole: (role: string) => boolean;
+  hasGroup: (group: string) => boolean;
+  findMatchingRule: (rules: Record<string, () => boolean>, pathname: string) => (() => boolean) | null;
+}
+
+export const rbacMiddleware: MiddlewareHandler = async (context, next) => {
+  const { locals, url } = context;
+  const pathname = url.pathname;
+
+  // Utility functions are available in the locals object
+  const { hasRole, hasGroup, findMatchingRule } = locals as Locals;
+
+  // Define your access rules
+  // Maps page routes to a function that returns true if the user has access, false otherwise
+  // You can use wildcards to match multiple paths
+  const accessRules = {
+    '/docs/domains/E-Commerce/*': () => !hasGroup('Viewer'),
+    '/visualiser/domains/E-Commerce/*': () => !hasGroup('Viewer'),
+    '/docs/services/payment/*': () => hasRole('Developer') || hasRole('Admin'),
+    '/admin/*': () => hasRole('Admin'),
+  };
+
+  if (findMatchingRule) {
+    // Find matching rule for the current path
+    const rule = findMatchingRule(accessRules, pathname);
+
+    if (rule && !rule()) {
+      return new Response('Forbidden', { status: 403 });
+    }
+  }
+
+  return next();
+};
+```
+
+### 2. Configure your access rules
+
+The `accessRules` object defines path-based access control:
+
+```typescript
+const accessRules = {
+  // Block 'Viewer' group from E-Commerce domain docs
+  '/docs/domains/E-Commerce/*': () => !hasGroup('Viewer'),
+  
+  // Require 'Developer' or 'Admin' role for payment services
+  '/docs/services/payment/*': () => hasRole('Developer') || hasRole('Admin'),
+  
+  // Admin-only sections
+  '/admin/*': () => hasRole('Admin'),
+  
+  // Multiple conditions
+  '/docs/sensitive/*': () => hasRole('Admin') && !hasGroup('External'),
+};
+```
+
+### 3. Available helper functions
+
+The middleware provides several helper functions through `locals`:
+
+#### `hasRole(role: string)`
+Checks if the user has a specific role:
+```typescript
+hasRole('Admin')        // Returns true if user has Admin role
+hasRole('Developer')    // Returns true if user has Developer role
+```
+
+#### `hasGroup(group: string)`
+Checks if the user belongs to a specific group:
+```typescript
+hasGroup('Viewer')      // Returns true if user is in Viewer group
+hasGroup('External')    // Returns true if user is in External group
+```
+
+#### `findMatchingRule(rules, pathname)`
+Finds the first matching rule for a given pathname using glob patterns:
+```typescript
+// Matches paths like:
+// - /docs/domains/E-Commerce/orders
+// - /docs/domains/E-Commerce/products/catalog
+'/docs/domains/E-Commerce/*': () => hasRole('Developer')
+```
+
+## Access Rule Patterns
+
+### Path-based rules
+Control access to specific pages or sections using exact paths or wildcard patterns.
+```typescript
+const accessRules = {
+  // Exact path match
+  '/admin/settings': () => hasRole('Admin'),
+  
+  // Wildcard matching
+  '/docs/domains/Banking/*': () => hasGroup('Banking-Team'),
+  
+  // Multiple level wildcards
+  '/api/*/internal/*': () => hasRole('Internal-Developer'),
+};
+```
+
+### Role-based rules
+Define access permissions based on user roles with single or multiple role requirements.
+```typescript
+const accessRules = {
+  // Single role requirement
+  '/admin/*': () => hasRole('Admin'),
+  
+  // Multiple role options (OR)
+  '/docs/api/*': () => hasRole('Developer') || hasRole('Architect'),
+  
+  // Multiple role requirements (AND)
+  '/sensitive/*': () => hasRole('Admin') && hasRole('Security-Cleared'),
+};
+```
+
+### Group-based rules
+Manage access using group membership with inclusion, exclusion, or complex group logic.
+```typescript
+const accessRules = {
+  // Exclude specific groups
+  '/public/*': () => !hasGroup('External'),
+  
+  // Include specific groups
+  '/team-docs/*': () => hasGroup('Internal-Team'),
+  
+  // Complex group logic
+  '/project-alpha/*': () => hasGroup('Alpha-Team') || hasGroup('Leadership'),
+};
+```
+
+## Common use cases
+
+### Department-based access
+Organize access control around your organizational structure, ensuring teams only see documentation relevant to their department.
+```typescript
+const accessRules = {
+  '/docs/domains/HR/*': () => hasGroup('HR-Department'),
+  '/docs/domains/Finance/*': () => hasGroup('Finance-Department'),
+  '/docs/domains/Engineering/*': () => hasGroup('Engineering-Department'),
+};
+```
+
+### Hierarchical permissions
+Create layered access levels where higher privilege users can access all lower-level content.
+```typescript
+const accessRules = {
+  '/docs/public/*': () => true, // Everyone can access
+  '/docs/internal/*': () => !hasGroup('External'),
+  '/docs/confidential/*': () => hasRole('Manager') || hasRole('Admin'),
+  '/docs/top-secret/*': () => hasRole('Admin'),
+};
+```
+
+### Feature-based access
+Control access to specific EventCatalog features based on user roles and responsibilities.
+```typescript
+const accessRules = {
+  '/visualiser/*': () => hasRole('Architect') || hasRole('Developer'),
+  '/api-explorer/*': () => hasRole('Developer'),
+  '/admin/*': () => hasRole('Admin'),
+};
+```
+
+## Troubleshooting
+
+### Users getting 403 errors unexpectedly
+
+1. **Check role/group assignment** in your identity provider
+2. **Debug user permissions** by logging the locals to see what roles and groups are available:
+   ```typescript
+   export const rbacMiddleware: MiddlewareHandler = async (context, next) => {
+     const { locals, url } = context;
+     
+     // Log the user's roles and groups for debugging
+     console.log('User locals:', {
+       pathname: url.pathname,
+       locals: locals
+     });
+     
+     // Your existing middleware code...
+   };
+   ```
+3. **Verify rule logic** - ensure your conditions are correct:
+   ```typescript
+   // Wrong: This blocks everyone except Viewers
+   '/docs/*': () => hasGroup('Viewer')
+   
+   // Correct: This blocks only Viewers
+   '/docs/*': () => !hasGroup('Viewer')
+   ```
+
+### Rules not matching expected paths
+
+1. **Test your glob patterns** - ensure wildcards match your URL structure
+2. **Check path casing** - paths are case-sensitive
+3. **Verify rule order** - more specific rules should come before general ones
+
+### Session issues
+
+1. **Ensure user is authenticated** before middleware runs
+2. **Check session expiration** - users may need to re-authenticate
+3. **Verify locals are populated** - `hasRole` and `hasGroup` functions must be available
+
+## Security best practices
+
+- ✅ **Principle of least privilege** - Grant minimum required access
+- ✅ **Regular access reviews** - Audit user roles and permissions
+- ✅ **Test thoroughly** - Verify access rules with different user types
+- ✅ **Monitor access attempts** - Log and review 403 responses
+- ✅ **Use groups over individual users** - Easier to manage and scale
+
+## Next steps
+
+With RBAC middleware configured, you can:
+
+- Set up more complex access patterns based on your organization structure
+- Integrate with external authorization systems
+- Add custom logging for access attempts
+
+Need help? Join our [Discord community](https://eventcatalog.dev/discord) for support and best practices from other EventCatalog users.

package/dist/docs/development/authentication/_category_.json

@@ -0,0 +1,11 @@
+{
+  "label": "Authentication",
+  "position": 10,
+  "collapsible": true,
+  "collapsed": true,
+  "link": {
+    "type": "generated-index",
+    "slug": "/development/guides/auth",
+    "description": "Authentication for EventCatalog"
+  }
+}

package/dist/docs/development/authentication/providers/03-setting-up-github.md

@@ -0,0 +1,83 @@
+---
+sidebar_position: 3
+keywords:
+- EventCatalog GitHub Authentication
+sidebar_label: GitHub
+title: Setting up GitHub
+description: Setting up GitHub authentication for EventCatalog
+---
+
+import AddedIn from '@site/src/components/MDX/AddedIn';
+import EventCatalogPro from '@site/src/components/MDX/EventCatalogPro';
+import PlanBanner from '@site/src/components/MDX/PlanBanner';
+
+<AddedIn version="2.43.0" />
+<PlanBanner plan="Scale" />
+
+:::info
+This guide takes your through setting up a protected sign-in screen for your docs. Before going through this guide, make sure you’ve first gone through [Enabling authentication](/docs/development/authentication/enabling-authentication).
+:::
+
+To setup your EventCatalog site with visitor authentication using [GitHub](https://github.com/), the process looks as follows:
+
+1. Create a new GitHub OAuth app
+2. Configure the OAuth app in EventCatalog
+3. Test the authentication
+
+## Create a new GitHub OAuth app
+
+First, you will need to create a new GitHub OAuth app.
+
+1. Go to [GitHub Developer Settings](https://github.com/settings/developers)
+2. Click on "New OAuth App"
+3. Fill in the details for your app
+    - **Application name:** `EventCatalog`
+    - **Homepage URL:** `{YOUR_EVENTCATALOG_SITE_URL}`
+        - Local development: `http://localhost:3000`
+    - **Authorization callback URL:** `{YOUR_EVENTCATALOG_SITE_URL}/api/auth/callback/github`
+        - Local development: `http://localhost:3000/api/auth/callback/github`
+4. Click on "Register application"
+5. Copy the Client ID and Client Secret
+
+## Configure the OAuth app in EventCatalog
+
+Add your GitHub Client ID and Client Secret to your `.env` file.
+
+```env title=".env"
+AUTH_GITHUB_CLIENT_ID={YOUR_GITHUB_CLIENT_ID}
+AUTH_GITHUB_CLIENT_SECRET={YOUR_GITHUB_CLIENT_SECRET}
+```
+
+In your `eventcatalog.auth.js` file, add the following:
+
+```js title="eventcatalog.auth.js"
+export default {
+  providers: {
+    github: {
+      clientId: process.env.AUTH_GITHUB_CLIENT_ID,
+      clientSecret: process.env.AUTH_GITHUB_CLIENT_SECRET,
+    },
+  },
+};
+```
+
+## Test the authentication
+
+Restart your EventCatalog server and test the authentication.
+
+```bash
+npm run dev
+```
+
+All pages should now be protected and require a GitHub account to access.
+
+![GitHub authentication](./img/github-auth.png)
+
+## Found an issue?
+
+Remember to setup the prerequisites for this guide:
+
+- [Enabling authentication](/docs/development/authentication/enabling-authentication)
+
+If you still have problems, please [let us know](https://github.com/eventcatalog/eventcatalog/issues/new/choose).
+

package/dist/docs/development/authentication/providers/03a-setting-up-google.md

@@ -0,0 +1,92 @@
+---
+sidebar_position: 3
+keywords:
+- EventCatalog Google Authentication
+sidebar_label: Google
+title: Setting up Google
+description: Setting up Google authentication for EventCatalog
+id: setting-up-google
+---
+
+import AddedIn from '@site/src/components/MDX/AddedIn';
+import EventCatalogPro from '@site/src/components/MDX/EventCatalogPro';
+import PlanBanner from '@site/src/components/MDX/PlanBanner';
+
+<AddedIn version="2.43.3" />
+<PlanBanner plan="Scale" />
+
+:::info
+This guide takes your through setting up a protected sign-in screen for your docs. Before going through this guide, make sure you've first gone through [Enabling authentication](/docs/development/authentication/enabling-authentication).
+:::
+
+To setup your EventCatalog site with visitor authentication using [Google](https://accounts.google.com/), the process looks as follows:
+
+1. Create a new Google OAuth app
+2. Configure the OAuth app in EventCatalog
+3. Test the authentication
+
+## Create a new Google OAuth app
+
+First, you will need to create a new Google OAuth app in the Google Cloud Console.
+
+1. Go to [Google Cloud Console](https://console.cloud.google.com/)
+2. Create a new project or select an existing one
+3. Navigate to "APIs & Services" → "Library"
+4. Search for and enable the "Google+ API"
+5. Go to "APIs & Services" → "Credentials"
+6. Click "Create Credentials" → "OAuth client ID"
+7. If prompted, configure the OAuth consent screen:
+  - Choose "External" for testing
+  - Fill in app name: `EventCatalog`
+  - Add your user support email and developer contact email
+  - Save and continue through the remaining screens
+8. Create the OAuth client ID:
+  - **Application type:** Web application
+  - **Name:** `EventCatalog`
+  - **Authorized JavaScript origins:** `{YOUR_EVENTCATALOG_SITE_URL}`
+    - Local development: `http://localhost:3000`
+  - **Authorized redirect URIs:** `{YOUR_EVENTCATALOG_SITE_URL}/api/auth/callback/google`
+    - Local development: `http://localhost:3000/api/auth/callback/google`
+9. Click "Create" and copy the Client ID and Client Secret
+
+## Configure the OAuth app in EventCatalog
+
+Add your Google Client ID and Client Secret to your `.env` file.
+
+```env title=".env"
+AUTH_GOOGLE_CLIENT_ID={YOUR_GOOGLE_CLIENT_ID}
+AUTH_GOOGLE_CLIENT_SECRET={YOUR_GOOGLE_CLIENT_SECRET}
+```
+
+In your eventcatalog.auth.js file, add the following:
+
+```js title="eventcatalog.auth.js"
+export default {
+  enabled: true,
+  google: {
+    clientId: process.env.AUTH_GOOGLE_CLIENT_ID,
+    clientSecret: process.env.AUTH_GOOGLE_CLIENT_SECRET,
+  },
+}
+```
+
+## Test the authentication
+
+Restart your EventCatalog server and test the authentication.
+
+```bash
+npm run dev
+```
+
+All pages should now be protected and require a Google account to access.
+
+![Google authentication](./img/google-auth.png)
+
+## Found an issue?
+
+Remember to setup the prerequisites for this guide:
+
+- [Enabling authentication](/docs/development/authentication/enabling-authentication)
+
+If you still have problems, please [let us know](https://github.com/eventcatalog/eventcatalog/issues/new/choose).
+