docs: update doc

adrien2p · Nov 28, 2023 · bdb8275 · bdb8275 · vercel · Nov 28, 2023
1 parent 5f5f269
commit bdb8275
Show file tree

Hide file tree

Showing 7 changed files with 7 additions and 7 deletions.
diff --git a/docs/pages/authentication/auth0.mdx b/docs/pages/authentication/auth0.mdx
@@ -101,7 +101,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is
           - If none are found, then the customer gets authenticated and can proceed and the metadata gets updated.
           - In the case another external authentication method have been used in the past, then an unauthorized
           will be returned.
-   - if the customer trying to authenticate does not exist, a new customer will be created and the authentication
+   - if the customer trying to authenticate does not exist, a new customer will be created with a randomly generated password and the authentication
      flow follow the previous point
 
 ### Request only access token in a JSON response

diff --git a/docs/pages/authentication/azureoidc.mdx b/docs/pages/authentication/azureoidc.mdx
@@ -132,7 +132,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is
           - If none are found, then the customer gets authenticated and can proceed and the metadata gets updated.
           - In the case another external authentication method have been used in the past, then an unauthorized
           will be returned.
-   - if the customer trying to authenticate does not exist, a new customer will be created and the authentication
+   - if the customer trying to authenticate does not exist, a new customer will be created with a randomly generated password and the authentication
      flow follow the previous point
 
 ### Request only access token in a JSON response

diff --git a/docs/pages/authentication/facebook.mdx b/docs/pages/authentication/facebook.mdx
@@ -107,7 +107,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is
           - If none are found, then the customer gets authenticated and can proceed and the metadata gets updated.
           - In the case another external authentication method have been used in the past, then an unauthorized
           will be returned.
-   - if the customer trying to authenticate does not exist, a new customer will be created and the authentication
+   - if the customer trying to authenticate does not exist, a new customer will be created with a randomly generated password and the authentication
      flow follow the previous point
 
 ### Request only access token in a JSON response

diff --git a/docs/pages/authentication/firebase.mdx b/docs/pages/authentication/firebase.mdx
@@ -93,5 +93,5 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is
           - If none are found, then the customer gets authenticated and can proceed and the metadata gets updated.
           - In the case another external authentication method have been used in the past, then an unauthorized
           will be returned.
-   - if the customer trying to authenticate does not exist, a new customer will be created and the authentication
+   - if the customer trying to authenticate does not exist, a new customer will be created with a randomly generated password and the authentication
      flow follow the previous point
diff --git a/docs/pages/authentication/google.mdx b/docs/pages/authentication/google.mdx
@@ -107,7 +107,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is
           - If none are found, then the customer gets authenticated and can proceed and the metadata gets updated.
           - In the case another external authentication method have been used in the past, then an unauthorized
           will be returned.
-   - if the customer trying to authenticate does not exist, a new customer will be created and the authentication
+   - if the customer trying to authenticate does not exist, a new customer will be created with a randomly generated password and the authentication
      flow follow the previous point
 
 ### Request only access token in a JSON response

diff --git a/docs/pages/authentication/linkedin.mdx b/docs/pages/authentication/linkedin.mdx
@@ -107,7 +107,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is
           - If none are found, then the customer gets authenticated and can proceed and the metadata gets updated.
           - In the case another external authentication method have been used in the past, then an unauthorized
           will be returned.
-   - if the customer trying to authenticate does not exist, a new customer will be created and the authentication
+   - if the customer trying to authenticate does not exist, a new customer will be created with a randomly generated password and the authentication
      flow follow the previous point
 
 ### Request only access token in a JSON response

diff --git a/packages/medusa-plugin-auth/src/auth-strategies/auth0/admin.ts b/packages/medusa-plugin-auth/src/auth-strategies/auth0/admin.ts
@@ -80,4 +80,4 @@ export function getAuth0AdminAuthRouter(auth0: Auth0Options, configModule: Confi
 		},
 		expiresIn: auth0.admin.expiresIn,
 	});
-}
+}
-Original file line number
+Diff line change
@@ Expand Up @@
     		},
     		expiresIn: auth0.admin.expiresIn,
     	});
-    }
+    }