Merge pull request #290943 from MicrosoftDocs/main

11/22/2024 AM Publish

Author: Taojunshen

articles/active-directory-b2c/add-api-connector-token-enrichment.md

@@ -78,10 +78,10 @@ Content-type: application/json
      }
  ],
  "displayName": "John Smith",
- "objectId": "ab3ec3b2-a435-45e4-b93a-56a005e88bb7",
+ "objectId": "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",
  "extension_<extensions-app-id>_CustomAttribute1": "custom attribute value",
  "extension_<extensions-app-id>_CustomAttribute2": "custom attribute value",
- "client_id": "231c70e8-8424-48ac-9b5d-5623b9e4ccf3",
+ "client_id": "00001111-aaaa-2222-bbbb-3333cccc4444",
  "step": "PreTokenIssuance",
  "ui_locales":"en-US"
 }
@@ -280,8 +280,8 @@ Save the files you changed: *TrustFrameworkBase.xml*, and *TrustFrameworkExtensi
   "exp": 1584961516,
   "nbf": 1584957916,
   "ver": "1.0",
-  "iss": "https://contoso.b2clogin.com/f06c2fe8-709f-4030-85dc-38a4bfd9e82d/v2.0/",
-  "aud": "e1d2612f-c2bc-4599-8e7b-d874eaca1ee1",
+  "iss": "https://contoso.b2clogin.com/aaaabbbb-0000-cccc-1111-dddd2222eeee/v2.0/",
+  "aud": "11112222-bbbb-3333-cccc-4444dddd5555",
   "acr": "b2c_1a_signup_signin",
   "nonce": "defaultNonce",
   "iat": 1584957916,

articles/active-directory-b2c/add-api-connector.md

@@ -76,7 +76,7 @@ Content-type: application/json
      }
  ],
  "displayName": "John Smith",
- "objectId": "11111111-0000-0000-0000-000000000000",
+ "objectId": "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",
  "givenName":"John",
  "surname":"Smith",
  "jobTitle":"Supplier",
@@ -88,7 +88,7 @@ Content-type: application/json
  "extension_<extensions-app-id>_CustomAttribute1": "custom attribute value",
  "extension_<extensions-app-id>_CustomAttribute2": "custom attribute value",
  "step": "<step-name>",
- "client_id":"93fd07aa-333c-409d-955d-96008fd08dd9",
+ "client_id":"00001111-aaaa-2222-bbbb-3333cccc4444",
  "ui_locales":"en-US"
 }
 ```
@@ -211,7 +211,7 @@ Content-type: application/json
  "extension_<extensions-app-id>_CustomAttribute1": "custom attribute value",
  "extension_<extensions-app-id>_CustomAttribute2": "custom attribute value",
  "step": "PostAttributeCollection",
- "client_id":"93fd07aa-333c-409d-955d-96008fd08dd9",
+ "client_id":"00001111-aaaa-2222-bbbb-3333cccc4444",
  "ui_locales":"en-US"
 }
 ```
@@ -262,7 +262,7 @@ POST <API-endpoint>
 Content-type: application/json
 
 {
- "clientId": "231c70e8-8424-48ac-9b5d-5623b9e4ccf3",
+ "clientId": "11112222-bbbb-3333-cccc-4444dddd5555",
  "step": "PreTokenApplicationClaims",
  "ui_locales":"en-US",
  "email": "[email protected]",
@@ -597,8 +597,8 @@ To return the promo code claim back to the relying party application, add an out
   "exp": 1584295703,
   "nbf": 1584292103,
   "ver": "1.0",
-  "iss": "https://contoso.b2clogin.com/f06c2fe8-709f-4030-85dc-38a4bfd9e82d/v2.0/",
-  "aud": "e1d2612f-c2bc-4599-8e7b-d874eaca1ee1",
+  "iss": "https://contoso.b2clogin.com/aaaabbbb-0000-cccc-1111-dddd2222eeee/v2.0/",
+  "aud": "22223333-cccc-4444-dddd-5555eeee6666",
   "acr": "b2c_1a_signup_signin",
   "nonce": "defaultNonce",
   "iat": 1584292103,

articles/active-directory-b2c/add-ropc-policy.md

@@ -316,7 +316,7 @@ POST /<tenant-name>.onmicrosoft.com/B2C_1A_ROPC_Auth/oauth2/v2.0/token HTTP/1.1
 Host: <tenant-name>.b2clogin.com
 Content-Type: application/x-www-form-urlencoded
 
-username=contosouser.outlook.com.ws&password=Passxword1&grant_type=password&scope=openid+bef22d56-552f-4a5b-b90a-1988a7d634ce+offline_access&client_id=bef22d56-552f-4a5b-b90a-1988a7d634ce&response_type=token+id_token
+username=contosouser.outlook.com.ws&password=Passxword1&grant_type=password&scope=openid+00001111-aaaa-2222-bbbb-3333cccc4444+offline_access&client_id=00001111-aaaa-2222-bbbb-3333cccc4444&response_type=token+id_token
 ```
 
 A successful response with offline-access looks like the following example:
@@ -379,4 +379,4 @@ A successful response looks like the following example:
 
 ## Use a native SDK or App-Auth
 
-Azure AD B2C meets OAuth 2.0 standards for public client resource owner password credentials and should be compatible with most client SDKs. For the latest information, see [Native App SDK for OAuth 2.0 and OpenID Connect implementing modern best practices](https://appauth.io/).
+Azure AD B2C meets OAuth 2.0 standards for public client resource owner password credentials and should be compatible with most client SDKs. For the latest information, see [Native App SDK for OAuth 2.0 and OpenID Connect implementing modern best practices](https://appauth.io/).

articles/active-directory-b2c/application-types.md

@@ -47,7 +47,7 @@ eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6ImtyaU1QZG1Cd...
 {
     "name": "John Smith",
     "email": "[email protected]",
-    "oid": "d9674823-dffc-4e3f-a6eb-62fe4bd48a58"
+    "oid": "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb"
     ...
 }
 ```

articles/active-directory-b2c/authorization-code-flow.md

@@ -31,7 +31,7 @@ Azure AD B2C extends the standard OAuth 2.0 flows to do more than simple authent
 To try the HTTP requests in this article:
 
 1. Replace `{tenant}` with the name of your Azure AD B2C tenant.
-1. Replace `90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6` with the app ID of an application you've previously registered in your Azure AD B2C tenant.
+1. Replace `00001111-aaaa-2222-bbbb-3333cccc4444` with the app ID of an application you've previously registered in your Azure AD B2C tenant.
 1. Replace `{policy}` with the name of a policy you've created in your tenant, for example `b2c_1_sign_in`.
 
 ## Redirect URI setup required for single-page apps
@@ -46,11 +46,11 @@ The authorization code flow begins with the client directing the user to the `/a
 
 ```http
 GET https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/{policy}/oauth2/v2.0/authorize?
-client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6
+client_id=00001111-aaaa-2222-bbbb-3333cccc4444
 &response_type=code
 &redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob
 &response_mode=query
-&scope=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6%20offline_access%20https://{tenant-name}/{app-id-uri}/{scope}
+&scope=00001111-aaaa-2222-bbbb-3333cccc4444%20offline_access%20https://{tenant-name}/{app-id-uri}/{scope}
 &state=arbitrary_data_you_can_receive_in_the_response
 &code_challenge=YTFjNjI1OWYzMzA3MTI4ZDY2Njg5M2RkNmVjNDE5YmEyZGRhOGYyM2IzNjdmZWFhMTQ1ODg3NDcxY2Nl
 &code_challenge_method=S256
@@ -116,8 +116,8 @@ POST https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/{policy}/oauth2/v2.0
 Content-Type: application/x-www-form-urlencoded
 
 grant_type=authorization_code
-&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6
-&scope=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6 offline_access
+&client_id=00001111-aaaa-2222-bbbb-3333cccc4444
+&scope=00001111-aaaa-2222-bbbb-3333cccc4444 offline_access
 &code=AwABAAAAvPM1KaPlrEqdFSBzjqfTGBCmLdgfSTLEMPGYuNHSUYBrq...
 &redirect_uri=urn:ietf:wg:oauth:2.0:oob
 &code_verifier=ThisIsntRandomButItNeedsToBe43CharactersLong 
@@ -144,7 +144,7 @@ A successful token response looks like this:
     "not_before": "1442340812",
     "token_type": "Bearer",
     "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ik5HVEZ2ZEstZnl0aEV1Q...",
-    "scope": "90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6 offline_access",
+    "scope": "00001111-aaaa-2222-bbbb-3333cccc4444 offline_access",
     "expires_in": "3600",
     "refresh_token": "AAQfQmvuDy8WtUv-sd0TBwWVQs1rC-Lfxa_NDkLqpg50Cxp5Dxj0VPF1mx2Z...",
 }
@@ -195,8 +195,8 @@ POST https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/{policy}/oauth2/v2.0
 Content-Type: application/x-www-form-urlencoded
 
 grant_type=refresh_token
-&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6
-&scope=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6 offline_access
+&client_id=00001111-aaaa-2222-bbbb-3333cccc4444
+&scope=00001111-aaaa-2222-bbbb-3333cccc4444 offline_access
 &refresh_token=AwABAAAAvPM1KaPlrEqdFSBzjqfTGBCmLdgfSTLEMPGYuNHSUYBrq...
 &redirect_uri=urn:ietf:wg:oauth:2.0:oob
 ```
@@ -219,7 +219,7 @@ A successful token response looks like this:
     "not_before": "1442340812",
     "token_type": "Bearer",
     "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ik5HVEZ2ZEstZnl0aEV1Q...",
-    "scope": "90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6 offline_access",
+    "scope": "00001111-aaaa-2222-bbbb-3333cccc4444 offline_access",
     "expires_in": "3600",
     "refresh_token": "AAQfQmvuDy8WtUv-sd0TBwWVQs1rC-Lfxa_NDkLqpg50Cxp5Dxj0VPF1mx2Z...",
 }

articles/active-directory-b2c/b2c-global-identity-proof-of-concept-funnel.md

@@ -119,7 +119,7 @@ The following block diagram shows the proof of concept. The guidance will show h
           <Item Key="AllowInsecureAuthInProduction">true</Item>
         </Metadata>
         <InputClaims>
-          <InputClaim ClaimTypeReferenceId="apac_client_id" PartnerClaimType="client_id" DefaultValue="cf3f6898-9a79-426a-ba16-10e1a377c843" />
+          <InputClaim ClaimTypeReferenceId="apac_client_id" PartnerClaimType="client_id" DefaultValue="00001111-aaaa-2222-bbbb-3333cccc4444" />
           <InputClaim ClaimTypeReferenceId="ropc_grant_type" PartnerClaimType="grant_type" DefaultValue="password" />
           <InputClaim ClaimTypeReferenceId="signInName" PartnerClaimType="username" />
           <InputClaim ClaimTypeReferenceId="password" />

articles/active-directory-b2c/b2c-global-identity-proof-of-concept-regional.md

@@ -128,7 +128,7 @@ The response should be an HTTP 200 with the users registered region and objectId
 
 ```json
 {
-  "objectId": "460f9ffb-8b6b-458d-a5a4-b8f3a6816fc2",
+  "objectId": "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",
   "region": "APAC"  
 }
 ```
@@ -149,7 +149,7 @@ Authorization Bearer: <token>
 Content-Type: application/json
 
 {
-  "objectId": "460f9ffb-8b6b-458d-a5a4-b8f3a6816fc2",
+  "objectId": "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",
   "password": "some!strong123STRING"
 }
 
@@ -335,7 +335,7 @@ The **ValidationTechnicalProfiles** will perform the following logic when the us
             <Item Key="AllowInsecureAuthInProduction">true</Item>
           </Metadata>
           <InputClaims>
-            <InputClaim ClaimTypeReferenceId="apac_client_id" PartnerClaimType="client_id" DefaultValue="cf3f6898-9a79-426a-ba16-10e1a377c843" />
+            <InputClaim ClaimTypeReferenceId="apac_client_id" PartnerClaimType="client_id" DefaultValue="00001111-aaaa-2222-bbbb-3333cccc4444" />
             <InputClaim ClaimTypeReferenceId="ropc_grant_type" PartnerClaimType="grant_type" DefaultValue="password" />
             <InputClaim ClaimTypeReferenceId="signInName" PartnerClaimType="username" />
             <InputClaim ClaimTypeReferenceId="password" />

articles/active-directory-b2c/claim-resolver-overview.md

@@ -97,7 +97,7 @@ The following table lists the claim resolvers with information about the OpenID
 | Claim | Description | Example |
 | ----- | ----------- | --------|
 | {OIDC:AuthenticationContextReferences} |The `acr_values` query string parameter. | N/A |
-| {OIDC:ClientId} |The `client_id`  query string parameter. | 00000000-0000-0000-0000-000000000000 |
+| {OIDC:ClientId} |The `client_id`  query string parameter. | 00001111-aaaa-2222-bbbb-3333cccc4444 |
 | {OIDC:DomainHint} |The `domain_hint`  query string parameter. | facebook.com |
 | {OIDC:LoginHint} |  The `login_hint` query string parameter. | [email protected] |
 | {OIDC:MaxAge} | The `max_age`. | N/A |

articles/active-directory-b2c/claimsschema.md

@@ -114,7 +114,7 @@ As a result, the JWT token issued by Azure AD B2C, emits the `family_name` inste
 
 ```json
 {
-  "sub": "6fbbd70d-262b-4b50-804c-257ae1706ef2",
+  "sub": "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",
   "auth_time": 1535013501,
   "given_name": "David",
   "family_name": "Williams",

articles/active-directory-b2c/client-credentials-grant-flow.md

@@ -150,7 +150,7 @@ There are no specific actions to enable the client credentials for user flows or
 | grant_type | `client_credentials` |
 | client_id | The **Client ID** from the [Step 2 Register an application](#step-2-register-an-application). |
 | client_secret | The **Client secret** value from [Step 2.1 Create a client secret](#step-21-create-a-client-secret). |
-| scope | The **Application ID URI** from [Step 1.1 Define web API roles (scopes)](#step-11-define-web-api-roles-scopes) and `.default`. For example `https://contoso.onmicrosoft.com/api/.default`, or `https://contoso.onmicrosoft.com/12345678-0000-0000-0000-000000000000/.default`.|
+| scope | The **Application ID URI** from [Step 1.1 Define web API roles (scopes)](#step-11-define-web-api-roles-scopes) and `.default`. For example `https://contoso.onmicrosoft.com/api/.default`, or `https://contoso.onmicrosoft.com/00001111-aaaa-2222-bbbb-3333cccc4444/.default`.|
 
 The actual POST request looks like the following example:
 
@@ -161,7 +161,7 @@ Host: <tenant-name>.b2clogin.com
 Content-Type: application/x-www-form-urlencoded
 
 grant_type=client_credentials
-&client_id=33333333-0000-0000-0000-000000000000
+&client_id=11112222-bbbb-3333-cccc-4444dddd5555
 &client_secret=FyX7Q~DuPJ...
 &scope=https%3A%2F%2Fcontoso.onmicrosoft.com%2Fapi%2F.default
 ```
@@ -175,7 +175,7 @@ grant_type=client_credentials
     "not_before": 1645172292,
     "expires_in": 3600,
     "expires_on": 1645175892,
-    "resource": "33333333-0000-0000-0000-000000000000"
+    "resource": "11112222-bbbb-3333-cccc-4444dddd5555"
 }
 ```
 
@@ -263,4 +263,4 @@ The following example shows a client credentials user journey. The first and the
 ```
 
 
-::: zone-end
+::: zone-end