diff --git a/docs/pages/authentication/auth0.mdx b/docs/pages/authentication/auth0.mdx index e7fb364..a6413c0 100644 --- a/docs/pages/authentication/auth0.mdx +++ b/docs/pages/authentication/auth0.mdx @@ -83,7 +83,7 @@ newly added plugins. To do so here are the steps Update your client to add the authentication action - After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer header to authenticate requests to the backend instead of using a session cookie. + After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer `` header to authenticate requests to the backend instead of using a session cookie. ### Default behaviour @@ -108,7 +108,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is If you are using your Medusa application with a SPA or mobile frontend, you can request opt to receive the access token in a JSON response instead of a redirect. -To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: ${medusa_url}/${authPath}?returnAccessToken=true +To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: `${medusa_url}/${authPath}?returnAccessToken=true` The response will look like this: ```json diff --git a/docs/pages/authentication/azureoidc.mdx b/docs/pages/authentication/azureoidc.mdx index 77765e0..b96f458 100644 --- a/docs/pages/authentication/azureoidc.mdx +++ b/docs/pages/authentication/azureoidc.mdx @@ -108,7 +108,7 @@ newly added plugins. To do so here are the steps - `medusa_url` correspond to your backend server url (e.g `http://localhost:9000`) - `authPath` correspond to `authPath` configuration in your plugin (e.g `admin/auth/azure`) - After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer header to authenticate requests to the backend instead of using a session cookie. + After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer `` header to authenticate requests to the backend instead of using a session cookie. ### Implementation Comments @@ -139,7 +139,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is If you are using your Medusa application with a SPA or mobile frontend, you can request opt to receive the access token in a JSON response instead of a redirect. -To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: ${medusa_url}/${authPath}?returnAccessToken=true +To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: `${medusa_url}/${authPath}?returnAccessToken=true` The response will look like this: ```json diff --git a/docs/pages/authentication/facebook.mdx b/docs/pages/authentication/facebook.mdx index 29dc982..ffd4735 100644 --- a/docs/pages/authentication/facebook.mdx +++ b/docs/pages/authentication/facebook.mdx @@ -89,7 +89,7 @@ newly added plugins. To do so here are the steps - `medusa_url` correspond to your backend server url (e.g `http://localhost:9000`) - `authPath` correspond to `authPath` configuration in your plugin (e.g `admin/auth/facebook`) - After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer header to authenticate requests to the backend instead of using a session cookie. + After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer `` header to authenticate requests to the backend instead of using a session cookie. ### Default behaviour @@ -114,7 +114,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is If you are using your Medusa application with a SPA or mobile frontend, you can request opt to receive the access token in a JSON response instead of a redirect. -To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: ${medusa_url}/${authPath}?returnAccessToken=true +To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: `${medusa_url}/${authPath}?returnAccessToken=true` The response will look like this: ```json diff --git a/docs/pages/authentication/google.mdx b/docs/pages/authentication/google.mdx index e1ffca6..6e7b83a 100644 --- a/docs/pages/authentication/google.mdx +++ b/docs/pages/authentication/google.mdx @@ -89,7 +89,7 @@ newly added plugins. To do so here are the steps - `medusa_url` correspond to your backend server url (e.g `http://localhost:9000`) - `authPath` correspond to `authPath` configuration in your plugin (e.g `admin/auth/google`) - After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer header to authenticate requests to the backend instead of using a session cookie. + After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer ```` header to authenticate requests to the backend instead of using a session cookie. ### Default behaviour @@ -114,7 +114,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is If you are using your Medusa application with a SPA or mobile frontend, you can request opt to receive the access token in a JSON response instead of a redirect. -To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: ${medusa_url}/${authPath}?returnAccessToken=true +To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: `${medusa_url}/${authPath}?returnAccessToken=true` The response will look like this: ```json diff --git a/docs/pages/authentication/linkedin.mdx b/docs/pages/authentication/linkedin.mdx index 34ab545..2271b54 100644 --- a/docs/pages/authentication/linkedin.mdx +++ b/docs/pages/authentication/linkedin.mdx @@ -89,7 +89,7 @@ newly added plugins. To do so here are the steps - `medusa_url` correspond to your backend server url (e.g `http://localhost:9000`) - `authPath` correspond to `authPath` configuration in your plugin (e.g `admin/auth/linkedin`) - After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer header to authenticate requests to the backend instead of using a session cookie. + After authentication is successfull, the user will be redirected to the `successRedirect` url with a `?access_token=your_token` query param and a session cookie will be set. Session will automatically be authenticated. The access token is a JWT that can be used with Authorization: Bearer `` header to authenticate requests to the backend instead of using a session cookie. ### Default behaviour @@ -114,7 +114,7 @@ The default `verifyCallback` flow looks as follow (unless the `strict` option is If you are using your Medusa application with a SPA or mobile frontend, you can request opt to receive the access token in a JSON response instead of a redirect. -To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: ${medusa_url}/${authPath}?returnAccessToken=true +To do this, you have to add ?returnAccessToken=true query parameter to your authentication call. Your authentication URL will then look like this: `${medusa_url}/${authPath}?returnAccessToken=true` The response will look like this: ```json