Many fixes - enums, secret creds scan, sample key

Author: FaithOmbongi

api-reference/beta/api/identitycontainer-post-identityproviders.md

@@ -135,7 +135,7 @@ Content-type: application/json
   "displayName": "Login with Amazon",
   "identityProviderType": "Amazon",
   "clientId": "00001111-aaaa-2222-bbbb-3333cccc4444",
-  "clientSecret": "4294967296"
+  "clientSecret": "42*****96"
 }
 ```
 
@@ -195,7 +195,7 @@ Content-type: application/json
     "displayName": "Login with Amazon",
     "identityProviderType": "Amazon",
     "clientId": "00001111-aaaa-2222-bbbb-3333cccc4444",
-    "clientSecret": "4294967296"
+    "clientSecret": "42*****96"
 }
 ```
 
@@ -424,7 +424,7 @@ Content-type: application/json
   "responseType": "code",
   "scope": "openid profile email offline_access",
   "clientAuthentication": {
-    "@odata.type": "#microsoft.graph.OIDCClientSecretAuthentication",
+    "@odata.type": "#microsoft.graph.oidcClientSecretAuthentication",
     "clientSecret": "4294967296"
   },
   "inboundClaimMapping": {

api-reference/beta/api/identityproviderbase-get.md

@@ -297,7 +297,7 @@ The following example shows a request.
 <!-- {
   "blockType": "request",
   "name": "get_openidconnectidentityprovider_from_identityproviderbase",
-  "sampleKeys": ["OIDC-V1-test-icm-4470de58-86c2-4a3f-a22c-63c9366cd000"]
+  "sampleKeys": ["Contoso-00001111-aaaa-2222-bbbb-3333cccc4444"]
 }
 -->
 

api-reference/beta/api/identityproviderbase-update.md

@@ -267,7 +267,7 @@ The following example shows a request.
 <!-- {
   "blockType": "request",
   "name": "update_openidconnectprovider_forAzure_AD_B2C",
-  "sampleKeys": ["OIDC-V1-Nam_AD_Test-00001111-aaaa-2222-bbbb-3333cccc4444"]
+  "sampleKeys": ["Contoso-OIDC-00001111-aaaa-2222-bbbb-3333cccc4444"]
 }
 -->
 

api-reference/beta/resources/enums.md

@@ -21,6 +21,15 @@ Namespace: microsoft.graph
 | provisioningCompleted |
 | unknownFutureValue |
 
+### oidcResponseType values 
+
+|Member|
+|:---|
+|code|
+|id_token|
+|token|
+|unknownFutureValue|
+
 ### approvalOperationStatus values
 
 | Member |

api-reference/beta/resources/oidcinboundclaimmappingoverride.md

@@ -21,8 +21,8 @@ You can configure the following standard OpenID Connect (OIDC) claims with the c
 
 |Property|Type|Description|
 |:---|:---|:---|
-|address|[oidcAddressInboundClaims](../resources/oidcaddressinboundclaims.md)|End-user's preferred postal address. The value of the address member is a JSON [RFC8259] structure containing some or all of the members defined in the resource type|
-|email|String|End-user's preferred e-mail address. Its value MUST conform to the RFC 5322 [RFC5322] addr-spec syntax.|
+|address|[oidcAddressInboundClaims](../resources/oidcaddressinboundclaims.md)|End-user's preferred postal address. The value of the address member is a JSON RFC8259 structure containing some or all of the members defined in the resource type|
+|email|String|End-user's preferred e-mail address. Its value MUST conform to the RFC 5322 addr-spec syntax.|
 |email_verified|String|True if the end-user's e-mail address has been verified by the identity provider; otherwise, false. When this claim value is true, this means that your identity provider took affirmative steps to ensure that this e-mail address was controlled by the end-user at the time the verification was performed. If this claim value is false, or not mapped with any claim of the identity provider, the user is asked to verify email during sign-up if email is required in the user flow.|
 |family_name|String|Surname(s) or family name of the end-user.|
 |given_name|String|Given name(s) or first name(s) of the end-user.|