AWS cognito medium security documentation change
Summary
Updated OIDC claims specification link from HTTP to HTTPS
Security assessment
Migrating to HTTPS prevents man-in-the-middle attacks when accessing OIDC specifications. This addresses transport layer security vulnerability in documentation references.
Diff
diff --git a/cognito/latest/developerguide/amazon-cognito-user-pools-using-the-id-token.md b/cognito/latest/developerguide/amazon-cognito-user-pools-using-the-id-token.md index 46926ffcf..11c7d6399 100644 --- a//cognito/latest/developerguide/amazon-cognito-user-pools-using-the-id-token.md +++ b//cognito/latest/developerguide/amazon-cognito-user-pools-using-the-id-token.md @@ -161 +161 @@ The unique identifier of the JWT. -The ID token can contain OIDC standard claims that are defined in [OIDC standard claims](http://openid.net/specs/openid-connect-core-1_0.html#Claims). The ID token can also contain custom attributes that you define in your user pool. Amazon Cognito writes custom attribute values to the ID token as strings regardless of attribute type. +The ID token can contain OIDC standard claims that are defined in [OIDC standard claims](https://openid.net/specs/openid-connect-core-1_0.html#Claims). The ID token can also contain custom attributes that you define in your user pool. Amazon Cognito writes custom attribute values to the ID token as strings regardless of attribute type.