@mulverse/mulguard-core 1.0.0

package/providers/gitlab.js

@@ -0,0 +1,75 @@
+/**
+ * Add GitLab login to your page.
+ *
+ * ### Setup
+ *
+ * #### Callback URL
+ * ```
+ * https://example.com/api/auth/callback/gitlab
+ * ```
+ *
+ * #### Configuration
+ *```ts
+ * import { Auth } from "@auth/core"
+ * import GitLab from "@auth/core/providers/gitlab"
+ *
+ * const request = new Request(origin)
+ * const response = await Auth(request, {
+ *   providers: [
+ *     GitLab({ clientId: GITLAB_CLIENT_ID, clientSecret: GITLAB_CLIENT_SECRET }),
+ *   ],
+ * })
+ * ```
+ *
+ * ### Resources
+ *
+ *  - [GitLab OAuth documentation](https://docs.gitlab.com/ee/api/oauth2.html)
+ *
+ * ### Notes
+ *
+ * By default, Auth.js assumes that the GitLab provider is
+ * based on the [OAuth 2](https://www.rfc-editor.org/rfc/rfc6749.html) specification.
+ *
+ * :::tip
+ * Enable the `read_user` option in scope if you want to save the users email address on sign up.
+ * :::
+ *
+ * :::tip
+ *
+ * The GitLab provider comes with a [default configuration](https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/providers/gitlab.ts).
+ * To override the defaults for your use case, check out [customizing a built-in OAuth provider](https://authjs.dev/guides/configuring-oauth-providers).
+ *
+ * :::
+ *
+ * :::info **Disclaimer**
+ *
+ * If you think you found a bug in the default configuration, you can [open an issue](https://authjs.dev/new/provider-issue).
+ *
+ * Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from
+ * the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec,
+ * we might not pursue a resolution. You can ask for more help in [Discussions](https://authjs.dev/new/github-discussions).
+ *
+ * :::
+ */
+export default function GitLab(options) {
+    const baseUrl = options.baseUrl ?? "https://gitlab.com";
+    const url = new URL(baseUrl.toString());
+    return {
+        id: "gitlab",
+        name: "GitLab",
+        type: "oauth",
+        authorization: `${url}oauth/authorize?scope=read_user`,
+        token: `${url}oauth/token`,
+        userinfo: `${url}api/v4/user`,
+        profile(profile) {
+            return {
+                id: profile.sub?.toString() ?? profile.id?.toString(),
+                name: profile.name ?? profile.username,
+                email: profile.email,
+                image: profile.avatar_url,
+            };
+        },
+        style: { bg: "#FC6D26", text: "#fff" },
+        options,
+    };
+}

package/providers/google.d.ts

@@ -0,0 +1,138 @@
+/**
+ * <div class="provider" style={{backgroundColor: "#000", display: "flex", justifyContent: "space-between", color: "#fff", padding: 16}}>
+ * <span>Built-in <b>Google</b> integration.</span>
+ * <a href="https://google.com">
+ *   <img style={{display: "block"}} src="https://authjs.dev/img/providers/google.svg" height="48" width="48"/>
+ * </a>
+ * </div>
+ *
+ * @module providers/google
+ */
+import type { OAuthConfig, OAuthUserConfig } from "./index.js";
+export interface GoogleProfile extends Record<string, any> {
+    aud: string;
+    azp: string;
+    email: string;
+    email_verified: boolean;
+    exp: number;
+    family_name?: string;
+    given_name: string;
+    hd?: string;
+    iat: number;
+    iss: string;
+    jti?: string;
+    locale?: string;
+    name: string;
+    nbf?: number;
+    picture: string;
+    sub: string;
+}
+/**
+ * Add Google login to your page.
+ *
+ * ### Setup
+ *
+ * #### Callback URL
+ * ```
+ * https://example.com/api/auth/callback/google
+ * ```
+ *
+ * #### Configuration
+ *```ts
+ * import { Auth } from "@auth/core"
+ * import Google from "@auth/core/providers/google"
+ *
+ * const request = new Request(origin)
+ * const response = await Auth(request, {
+ *   providers: [
+ *     Google({ clientId: GOOGLE_CLIENT_ID, clientSecret: GOOGLE_CLIENT_SECRET }),
+ *   ],
+ * })
+ * ```
+ *
+ * ### Resources
+ *
+ *  - [Google OAuth documentation](https://developers.google.com/identity/protocols/oauth2)
+ *  - [Google OAuth Configuration](https://console.developers.google.com/apis/credentials)
+ *
+ * ### Notes
+ *
+ * By default, Auth.js assumes that the Google provider is
+ * based on the [Open ID Connect](https://openid.net/specs/openid-connect-core-1_0.html) specification.
+ *
+ *
+ * The "Authorized redirect URIs" used when creating the credentials must include your full domain and end in the callback path. For example;
+ *
+ * - For production: `https://{YOUR_DOMAIN}/api/auth/callback/google`
+ * - For development: `http://localhost:3000/api/auth/callback/google`
+ *
+ * :::warning
+ * Google only provides Refresh Token to an application the first time a user signs in.
+ *
+ * To force Google to re-issue a Refresh Token, the user needs to remove the application from their account and sign in again:
+ * https://myaccount.google.com/permissions
+ *
+ * Alternatively, you can also pass options in the `params` object of `authorization` which will force the Refresh Token to always be provided on sign in, however this will ask all users to confirm if they wish to grant your application access every time they sign in.
+ *
+ * If you need access to the RefreshToken or AccessToken for a Google account and you are not using a database to persist user accounts, this may be something you need to do.
+ *
+ * ```ts
+ * const options = {
+ *   providers: [
+ *     Google({
+ *       clientId: process.env.GOOGLE_ID,
+ *       clientSecret: process.env.GOOGLE_SECRET,
+ *       authorization: {
+ *         params: {
+ *           prompt: "consent",
+ *           access_type: "offline",
+ *           response_type: "code"
+ *         }
+ *       }
+ *     })
+ *   ],
+ * }
+ * ```
+ *
+ * :::
+ *
+ * :::tip
+ * Google also returns a `email_verified` boolean property in the OAuth profile.
+ *
+ * You can use this property to restrict access to people with verified accounts at a particular domain.
+ *
+ * ```ts
+ * const options = {
+ *   ...
+ *   callbacks: {
+ *     async signIn({ account, profile }) {
+ *       if (account.provider === "google") {
+ *         return profile.email_verified && profile.email.endsWith("@example.com")
+ *       }
+ *       return true // Do different verification for other providers that don't have `email_verified`
+ *     },
+ *   }
+ *   ...
+ * }
+ * ```
+ *
+ * :::
+ * :::tip
+ *
+ * The Google provider comes with a [default configuration](https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/providers/google.ts).
+ * To override the defaults for your use case, check out [customizing a built-in OAuth provider](https://authjs.dev/guides/configuring-oauth-providers).
+ *
+ * :::
+ *
+ * :::info **Disclaimer**
+ *
+ * If you think you found a bug in the default configuration, you can [open an issue](https://authjs.dev/new/provider-issue).
+ *
+ * Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from
+ * the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec,
+ * we might not pursue a resolution. You can ask for more help in [Discussions](https://authjs.dev/new/github-discussions).
+ *
+ * :::
+ */
+export default function Google<P extends GoogleProfile>(options: OAuthUserConfig<P>): OAuthConfig<P>;
+//# sourceMappingURL=google.d.ts.map

package/providers/google.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"google.d.ts","sourceRoot":"","sources":["../src/providers/google.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,OAAO,KAAK,EAAE,WAAW,EAAE,eAAe,EAAE,MAAM,YAAY,CAAA;AAE9D,MAAM,WAAW,aAAc,SAAQ,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC;IACxD,GAAG,EAAE,MAAM,CAAA;IACX,GAAG,EAAE,MAAM,CAAA;IACX,KAAK,EAAE,MAAM,CAAA;IACb,cAAc,EAAE,OAAO,CAAA;IACvB,GAAG,EAAE,MAAM,CAAA;IACX,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB,UAAU,EAAE,MAAM,CAAA;IAClB,EAAE,CAAC,EAAE,MAAM,CAAA;IACX,GAAG,EAAE,MAAM,CAAA;IACX,GAAG,EAAE,MAAM,CAAA;IACX,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ,MAAM,CAAC,EAAE,MAAM,CAAA;IACf,IAAI,EAAE,MAAM,CAAA;IACZ,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ,OAAO,EAAE,MAAM,CAAA;IACf,GAAG,EAAE,MAAM,CAAA;CACZ;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0GG;AACH,MAAM,CAAC,OAAO,UAAU,MAAM,CAAC,CAAC,SAAS,aAAa,EACpD,OAAO,EAAE,eAAe,CAAC,CAAC,CAAC,GAC1B,WAAW,CAAC,CAAC,CAAC,CAWhB"}

package/providers/google.js

@@ -0,0 +1,119 @@
+/**
+ * Add Google login to your page.
+ *
+ * ### Setup
+ *
+ * #### Callback URL
+ * ```
+ * https://example.com/api/auth/callback/google
+ * ```
+ *
+ * #### Configuration
+ *```ts
+ * import { Auth } from "@auth/core"
+ * import Google from "@auth/core/providers/google"
+ *
+ * const request = new Request(origin)
+ * const response = await Auth(request, {
+ *   providers: [
+ *     Google({ clientId: GOOGLE_CLIENT_ID, clientSecret: GOOGLE_CLIENT_SECRET }),
+ *   ],
+ * })
+ * ```
+ *
+ * ### Resources
+ *
+ *  - [Google OAuth documentation](https://developers.google.com/identity/protocols/oauth2)
+ *  - [Google OAuth Configuration](https://console.developers.google.com/apis/credentials)
+ *
+ * ### Notes
+ *
+ * By default, Auth.js assumes that the Google provider is
+ * based on the [Open ID Connect](https://openid.net/specs/openid-connect-core-1_0.html) specification.
+ *
+ *
+ * The "Authorized redirect URIs" used when creating the credentials must include your full domain and end in the callback path. For example;
+ *
+ * - For production: `https://{YOUR_DOMAIN}/api/auth/callback/google`
+ * - For development: `http://localhost:3000/api/auth/callback/google`
+ *
+ * :::warning
+ * Google only provides Refresh Token to an application the first time a user signs in.
+ *
+ * To force Google to re-issue a Refresh Token, the user needs to remove the application from their account and sign in again:
+ * https://myaccount.google.com/permissions
+ *
+ * Alternatively, you can also pass options in the `params` object of `authorization` which will force the Refresh Token to always be provided on sign in, however this will ask all users to confirm if they wish to grant your application access every time they sign in.
+ *
+ * If you need access to the RefreshToken or AccessToken for a Google account and you are not using a database to persist user accounts, this may be something you need to do.
+ *
+ * ```ts
+ * const options = {
+ *   providers: [
+ *     Google({
+ *       clientId: process.env.GOOGLE_ID,
+ *       clientSecret: process.env.GOOGLE_SECRET,
+ *       authorization: {
+ *         params: {
+ *           prompt: "consent",
+ *           access_type: "offline",
+ *           response_type: "code"
+ *         }
+ *       }
+ *     })
+ *   ],
+ * }
+ * ```
+ *
+ * :::
+ *
+ * :::tip
+ * Google also returns a `email_verified` boolean property in the OAuth profile.
+ *
+ * You can use this property to restrict access to people with verified accounts at a particular domain.
+ *
+ * ```ts
+ * const options = {
+ *   ...
+ *   callbacks: {
+ *     async signIn({ account, profile }) {
+ *       if (account.provider === "google") {
+ *         return profile.email_verified && profile.email.endsWith("@example.com")
+ *       }
+ *       return true // Do different verification for other providers that don't have `email_verified`
+ *     },
+ *   }
+ *   ...
+ * }
+ * ```
+ *
+ * :::
+ * :::tip
+ *
+ * The Google provider comes with a [default configuration](https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/providers/google.ts).
+ * To override the defaults for your use case, check out [customizing a built-in OAuth provider](https://authjs.dev/guides/configuring-oauth-providers).
+ *
+ * :::
+ *
+ * :::info **Disclaimer**
+ *
+ * If you think you found a bug in the default configuration, you can [open an issue](https://authjs.dev/new/provider-issue).
+ *
+ * Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from
+ * the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec,
+ * we might not pursue a resolution. You can ask for more help in [Discussions](https://authjs.dev/new/github-discussions).
+ *
+ * :::
+ */
+export default function Google(options) {
+    return {
+        id: "google",
+        name: "Google",
+        type: "oidc",
+        issuer: "https://accounts.google.com",
+        style: {
+            brandColor: "#1a73e8",
+        },
+        options,
+    };
+}

package/providers/hubspot.d.ts

@@ -0,0 +1,76 @@
+/**
+ * <div class="provider" style={{backgroundColor: "#000", display: "flex", justifyContent: "space-between", color: "#fff", padding: 16}}>
+ * <span>Built-in <b>HubSpot</b> integration.</span>
+ * <a href="https://hubspot.com">
+ *   <img style={{display: "block"}} src="https://authjs.dev/img/providers/hubspot.svg" height="48" width="48"/>
+ * </a>
+ * </div>
+ *
+ * @module providers/hubspot
+ */
+import type { OAuthConfig, OAuthUserConfig } from "./index.js";
+interface HubSpotProfile extends Record<string, any> {
+    user: string;
+    user_id: string;
+    hub_domain: string;
+    hub_id: string;
+}
+/**
+ * Add HubSpot login to your page.
+ *
+ * ### Setup
+ *
+ * #### Callback URL
+ * ```
+ * https://example.com/api/auth/callback/hubspot
+ * ```
+ *
+ * #### Configuration
+ *```ts
+ * import { Auth } from "@auth/core"
+ * import HubSpot from "@auth/core/providers/hubspot"
+ *
+ * const request = new Request(origin)
+ * const response = await Auth(request, {
+ *   providers: [
+ *     HubSpot({
+ *       clientId: HUBSPOT_CLIENT_ID,
+ *       clientSecret: HUBSPOT_CLIENT_SECRET,
+ *     }),
+ *   ],
+ * })
+ * ```
+ *
+ * ### Resources
+ *
+ *  - [HubSpot OAuth documentation](https://developers.hubspot.com/docs/api/oauth-quickstart-guide)
+ *
+ * ### Notes
+ *
+ * By default, Auth.js assumes that the HubSpot provider is
+ * based on the [OAuth 2](https://www.rfc-editor.org/rfc/rfc6749.html) specification.
+ *
+ * You need to have an APP in your Developer Account as described at https://developers.hubspot.com/docs/api/developer-tools-overview
+ * :::note
+ * HubSpot returns a limited amount of information on the token holder (see [docs](https://legacydocs.hubspot.com/docs/methods/oauth2/get-access-token-information)). One other issue is that the name and profile photo cannot be fetched through API as discussed [here](https://community.hubspot.com/t5/APIs-Integrations/Profile-photo-is-not-retrieved-with-User-API/m-p/325521).
+ * :::
+ * :::tip
+ *
+ * The HubSpot provider comes with a [default configuration](https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/providers/hubspot.ts).
+ * To override the defaults for your use case, check out [customizing a built-in OAuth provider](https://authjs.dev/guides/configuring-oauth-providers).
+ *
+ * :::
+ *
+ * :::info **Disclaimer**
+ *
+ * If you think you found a bug in the default configuration, you can [open an issue](https://authjs.dev/new/provider-issue).
+ *
+ * Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from
+ * the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec,
+ * we might not pursue a resolution. You can ask for more help in [Discussions](https://authjs.dev/new/github-discussions).
+ *
+ * :::
+ */
+export default function HubSpot<P extends HubSpotProfile>(options: OAuthUserConfig<P>): OAuthConfig<P>;
+export {};
+//# sourceMappingURL=hubspot.d.ts.map

package/providers/hubspot.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hubspot.d.ts","sourceRoot":"","sources":["../src/providers/hubspot.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,OAAO,KAAK,EAAE,WAAW,EAAE,eAAe,EAAE,MAAM,YAAY,CAAA;AAE9D,UAAU,cAAe,SAAQ,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC;IAElD,IAAI,EAAE,MAAM,CAAA;IACZ,OAAO,EAAE,MAAM,CAAA;IACf,UAAU,EAAE,MAAM,CAAA;IAClB,MAAM,EAAE,MAAM,CAAA;CACf;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuDG;AACH,MAAM,CAAC,OAAO,UAAU,OAAO,CAAC,CAAC,SAAS,cAAc,EACtD,OAAO,EAAE,eAAe,CAAC,CAAC,CAAC,GAC1B,WAAW,CAAC,CAAC,CAAC,CAsChB"}

package/providers/hubspot.js

@@ -0,0 +1,93 @@
+/**
+ * Add HubSpot login to your page.
+ *
+ * ### Setup
+ *
+ * #### Callback URL
+ * ```
+ * https://example.com/api/auth/callback/hubspot
+ * ```
+ *
+ * #### Configuration
+ *```ts
+ * import { Auth } from "@auth/core"
+ * import HubSpot from "@auth/core/providers/hubspot"
+ *
+ * const request = new Request(origin)
+ * const response = await Auth(request, {
+ *   providers: [
+ *     HubSpot({
+ *       clientId: HUBSPOT_CLIENT_ID,
+ *       clientSecret: HUBSPOT_CLIENT_SECRET,
+ *     }),
+ *   ],
+ * })
+ * ```
+ *
+ * ### Resources
+ *
+ *  - [HubSpot OAuth documentation](https://developers.hubspot.com/docs/api/oauth-quickstart-guide)
+ *
+ * ### Notes
+ *
+ * By default, Auth.js assumes that the HubSpot provider is
+ * based on the [OAuth 2](https://www.rfc-editor.org/rfc/rfc6749.html) specification.
+ *
+ * You need to have an APP in your Developer Account as described at https://developers.hubspot.com/docs/api/developer-tools-overview
+ * :::note
+ * HubSpot returns a limited amount of information on the token holder (see [docs](https://legacydocs.hubspot.com/docs/methods/oauth2/get-access-token-information)). One other issue is that the name and profile photo cannot be fetched through API as discussed [here](https://community.hubspot.com/t5/APIs-Integrations/Profile-photo-is-not-retrieved-with-User-API/m-p/325521).
+ * :::
+ * :::tip
+ *
+ * The HubSpot provider comes with a [default configuration](https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/providers/hubspot.ts).
+ * To override the defaults for your use case, check out [customizing a built-in OAuth provider](https://authjs.dev/guides/configuring-oauth-providers).
+ *
+ * :::
+ *
+ * :::info **Disclaimer**
+ *
+ * If you think you found a bug in the default configuration, you can [open an issue](https://authjs.dev/new/provider-issue).
+ *
+ * Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from
+ * the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec,
+ * we might not pursue a resolution. You can ask for more help in [Discussions](https://authjs.dev/new/github-discussions).
+ *
+ * :::
+ */
+export default function HubSpot(options) {
+    return {
+        id: "hubspot",
+        name: "HubSpot",
+        type: "oauth",
+        authorization: {
+            url: "https://app.hubspot.com/oauth/authorize",
+            params: { scope: "oauth", client_id: options.clientId },
+        },
+        client: {
+            token_endpoint_auth_method: "client_secret_post",
+        },
+        token: "https://api.hubapi.com/oauth/v1/token",
+        userinfo: {
+            url: "https://api.hubapi.com/oauth/v1/access-tokens",
+            async request({ tokens, provider }) {
+                const url = `${provider.userinfo?.url}/${tokens.access_token}`;
+                return await fetch(url, {
+                    headers: { "Content-Type": "application/json" },
+                    method: "GET",
+                }).then(async (res) => await res.json());
+            },
+        },
+        profile(profile) {
+            return {
+                id: profile.user_id,
+                name: profile.user,
+                email: profile.user,
+                // TODO: get image from profile once it's available
+                // Details available https://community.hubspot.com/t5/APIs-Integrations/Profile-photo-is-not-retrieved-with-User-API/m-p/325521
+                image: null,
+            };
+        },
+        style: { bg: "#ff7a59", text: "#fff" },
+        options,
+    };
+}