Skip to content

Commit ec40b77

Browse files
committed
2924984
1 parent 3de82ca commit ec40b77

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

powerapps-docs/maker/portals/important-changes-deprecations.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sandhangitmsft
55

66
ms.topic: conceptual
77
ms.custom:
8-
ms.date: 09/09/2022
8+
ms.date: 09/16/2022
99
ms.subservice: portals
1010
ms.author: sandhan
1111
ms.reviewer: ndoelman
@@ -37,10 +37,12 @@ At launch, users with the system administrator role along with [service admins](
3737
3838
## OAuth 2.0 implicit grant flow within your portal
3939

40-
Starting June 2022, [authorize endpoint](oauth-implicit-grant-flow.md#authorize-endpoint-details), [token endpoint](oauth-implicit-grant-flow.md#token-endpoint-details) using GET request, and using the default certificate for OAuth 2.0 implicit grant flow will be deprecated. No action is needed for newly created portals or for existing portals that don't use this feature. If you're already using this feature, you need to use the token endpoint POST request to get a secure access token to authorize the external APIs.
40+
The [authorize endpoint](oauth-implicit-grant-flow.md#authorize-endpoint-details), [token endpoint](oauth-implicit-grant-flow.md#token-endpoint-details) using GET request, and using the default certificate for OAuth 2.0 implicit grant flow is deprecated. No action is needed for newly created portals or for existing portals that don't use this feature. If you're already using this feature, you need to use the token endpoint POST request to get a secure access token to authorize the external APIs.
4141

4242
> [!NOTE]
43-
> All existing customers who are using this deprecated feature need to migrate to the supported method by October 2022.
43+
> - All existing customers who are using this deprecated feature need to migrate to the supported method by October 2022.
44+
> - For more information on using a custom certificate, go to [using a custom certificate](oauth-implicit-grant-flow.md#custom-certificates).
45+
> - For sample code on using POST calls on the Token endpoint, go to [](oauth-implicit-grant-flow.md#token-endpoint-sample).
4446
4547
## List OData feed
4648

powerapps-docs/maker/portals/oauth-implicit-grant-flow.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: gitanjalisingh33msft
55

66
ms.topic: conceptual
77
ms.custom:
8-
ms.date: 05/11/2022
8+
ms.date: 09/16/2022
99
ms.subservice: portals
1010
ms.author: gisingh
1111
ms.reviewer: ndoelman
@@ -25,7 +25,7 @@ OAuth 2.0 implicit grant flow supports [token](#token-endpoint-details) endpoint
2525

2626
## Custom certificates
2727

28-
Custom certificates provide another layer of security while using the OAuth 2.0 end point. Use the [Power Platform admin center](/admin/manage-custom-certificates) to upload the custom certificate. After uploading the custom certificate, you need to update site settings as below
28+
Using the default certificate for OAuth 2.0 implicit grant flow is [deprecated](important-changes-deprecations.md#oauth-20-implicit-grant-flow-within-your-portal). You will need to use a custom certificates while using the OAuth 2.0 end point. Use the [Power Platform admin center](/admin/manage-custom-certificates) to upload the custom certificate. After uploading the custom certificate, you need to update site settings as below:
2929

3030
1. Go to [portal settings](manage-existing-portals.md#settings) and select **Site Settings**.
3131

0 commit comments

Comments
 (0)