Use the correct oauth2 instructions

supertokens · Feb 6, 2025 · 11f47cd · 11f47cd
1 parent 5e686ef
commit 11f47cd
Show file tree

Hide file tree

Showing 7 changed files with 10 additions and 10 deletions.
diff --git a/v2/microservice_auth/client-credentials.mdx b/v2/microservice_auth/client-credentials.mdx
@@ -63,7 +63,7 @@ This can be done by directly calling the **SuperTokens Core** API.
 ```bash
 # You will have to run this for each one of your applications
 # Adjust the attributes based on that
-curl -X POST ^{coreInjector_uri_without_quotes}/recipe/oauth2/admin/clients \
+curl -X POST ^{coreInjector_uri_without_quotes}/recipe/oauth/clients \
   -H "Content-Type: application/json" \
   -H "api-key: ^{coreInjector_api_key_without_quotes}" \
   -d '{

diff --git a/v2/unified-login/multiple-frontends-with-separate-backends.mdx b/v2/unified-login/multiple-frontends-with-separate-backends.mdx
@@ -84,7 +84,7 @@ This can be done by directly calling the **SuperTokens Core** API.
 ```bash
 # You will have to run this for each one of your applications
 # Adjust the client_name and redirect_uri based on that
-curl -X POST ^{coreInjector_uri_without_quotes}/recipe/oauth2/admin/clients \
+curl -X POST ^{coreInjector_uri_without_quotes}/recipe/oauth/clients \
   -H "Content-Type: application/json" \
   -H "api-key: ^{coreInjector_api_key_without_quotes}" \
   -d '{

diff --git a/v2/unified-login/reuse-website-login.mdx b/v2/unified-login/reuse-website-login.mdx
@@ -76,7 +76,7 @@ This can be done by directly calling the **SuperTokens Core** API.
 ```bash
 # You will have to run this for each one of your applications
 # Adjust the client_name and redirect_uri based on that
-curl -X POST ^{coreInjector_uri_without_quotes}/recipe/oauth2/admin/clients \
+curl -X POST ^{coreInjector_uri_without_quotes}/recipe/oauth/clients \
   -H "Content-Type: application/json" \
   -H "api-key: ^{coreInjector_api_key_without_quotes}" \
   -d '{

diff --git a/v3/docs/authentication/m2m/client-credentials.mdx b/v3/docs/authentication/m2m/client-credentials.mdx
@@ -34,7 +34,7 @@ You will first have to enable the **OAuth2** features from the **SuperTokens.com
 1. Open the **SuperTokens.com Dashboard**
 2. Click on the **Enabled Paid Features** button
 3. Click on **Managed Service**
-4. Check the **OAuth 2.0** option
+4. Check the **Unified Login / M2M** option
 5. Click *Save* 
 
 Now you should be able to use the OAuth2 recipes in your applications.
@@ -47,7 +47,7 @@ This can be done by directly calling the **SuperTokens Core** API.
 ```bash
 # You will have to run this for each one of your applications
 # Adjust the attributes based on that
-curl -X POST ^{coreInfo.uri}/recipe/oauth2/admin/clients \
+curl -X POST ^{coreInfo.uri}/recipe/oauth/clients \
   -H "Content-Type: application/json" \
   -H "api-key: ^{coreInfo.key}" \
   -d '{

diff --git a/...entication/unified-login/use-cases/multiple-frontends-with-a-single-backend.mdx b/...entication/unified-login/use-cases/multiple-frontends-with-a-single-backend.mdx
@@ -51,7 +51,7 @@ You will first have to enable the **OAuth2** features from the **SuperTokens.com
 1. Open the **SuperTokens.com Dashboard**
 2. Click on the **Enabled Paid Features** button
 3. Click on **Managed Service**
-4. Check the **OAuth 2.0** option
+4. Check the **Unified Login / M2M** option
 5. Click *Save* 
 
 Now you should be able to use the OAuth2 recipes in your applications.

diff --git a/...ntication/unified-login/use-cases/multiple-frontends-with-separate-backends.mdx b/...ntication/unified-login/use-cases/multiple-frontends-with-separate-backends.mdx
@@ -56,7 +56,7 @@ You will first have to enable the **OAuth2** features from the **SuperTokens.com
 1. Open the **SuperTokens.com Dashboard**
 2. Click on the **Enabled Paid Features** button
 3. Click on **Managed Service**
-4. Check the **OAuth 2.0** option
+4. Check the **Unified Login / M2M** option
 5. Click *Save* 
 
 Now you should be able to use the OAuth2 recipes in your applications.
@@ -71,7 +71,7 @@ This can be done by directly calling the **SuperTokens Core** API.
 ```bash
 # You will have to run this for each one of your applications
 # Adjust the client_name and redirect_uri based on that
-curl -X POST ^{coreInfo.uri}/recipe/oauth2/admin/clients \
+curl -X POST ^{coreInfo.uri}/recipe/oauth/clients \
   -H "Content-Type: application/json" \
   -H "api-key: ^{coreInfo.key}" \
   -d '{

diff --git a/v3/docs/authentication/unified-login/use-cases/reuse-website-login.mdx b/v3/docs/authentication/unified-login/use-cases/reuse-website-login.mdx
@@ -45,7 +45,7 @@ You will first have to enable the **OAuth2** features from the **SuperTokens.com
 1. Open the **SuperTokens.com Dashboard**
 2. Click on the **Enabled Paid Features** button
 3. Click on **Managed Service**
-4. Check the **OAuth 2.0** option
+4. Check the **Unified Login / M2M** option
 5. Click *Save* 
 
 Now you should be able to use the OAuth2 recipes in your applications.
@@ -60,7 +60,7 @@ This can be done by directly calling the **SuperTokens Core** API.
 ```bash
 # You will have to run this for each one of your applications
 # Adjust the client_name and redirect_uri based on that
-curl -X POST ^{coreInfo.uri}/recipe/oauth2/admin/clients \
+curl -X POST ^{coreInfo.uri}/recipe/oauth/clients \
   -H "Content-Type: application/json" \
   -H "api-key: ^{coreInfo.key}" \
   -d '{