AWS AWSCloudFormation documentation change
Summary
Condensed LDAP server metadata documentation and replaced detailed property descriptions with 'Property description not available.'
Security assessment
The changes remove critical explanations for LDAP configuration properties (e.g., search filters, group attributes), which could lead to misconfigurations. However, there is no explicit evidence of addressing a specific security vulnerability, only a reduction in documentation clarity.
Diff
diff --git a/AWSCloudFormation/latest/TemplateReference/aws-properties-amazonmq-broker-ldapservermetadata.md b/AWSCloudFormation/latest/TemplateReference/aws-properties-amazonmq-broker-ldapservermetadata.md index b2cb3e846..7fd440a12 100644 --- a//AWSCloudFormation/latest/TemplateReference/aws-properties-amazonmq-broker-ldapservermetadata.md +++ b//AWSCloudFormation/latest/TemplateReference/aws-properties-amazonmq-broker-ldapservermetadata.md @@ -9,5 +9 @@ This is the new _AWS CloudFormation Template Reference Guide_. Please update you -Optional. The metadata of the LDAP server used to authenticate and authorize connections to the broker. - -###### Important - -Does not apply to RabbitMQ brokers. +Optional. The metadata of the LDAP server used to authenticate and authorize connections to the broker. Does not apply to RabbitMQ brokers. @@ -59 +55 @@ To declare this entity in your AWS CloudFormation template, use the following sy -Specifies the location of the LDAP server such as AWS Directory Service for Microsoft Active Directory. Optional failover server. +Property description not available. @@ -70 +66 @@ _Required_ : Yes -The distinguished name of the node in the directory information tree (DIT) to search for roles or groups. For example, `ou=group`, `ou=corp`, `dc=corp`, `dc=example`, `dc=com`. +Property description not available. @@ -81 +77 @@ _Required_ : Yes -The group name attribute in a role entry whose value is the name of that role. For example, you can specify `cn` for a group entry's common name. If authentication succeeds, then the user is assigned the the value of the `cn` attribute for each role entry that they are a member of. +Property description not available. @@ -92 +88 @@ _Required_ : No -The LDAP search filter used to find roles within the roleBase. The distinguished name of the user matched by userSearchMatching is substituted into the `{0}` placeholder in the search filter. The client's username is substituted into the `{1}` placeholder. For example, if you set this option to `(member=uid={1})` for the user janedoe, the search filter becomes `(member=uid=janedoe)` after string substitution. It matches all role entries that have a member attribute equal to `uid=janedoe` under the subtree selected by the `RoleBases`. +Property description not available. @@ -103 +99 @@ _Required_ : Yes -The directory search scope for the role. If set to true, scope is to search the entire subtree. +Property description not available. @@ -114 +110 @@ _Required_ : No -Service account password. A service account is an account in your LDAP server that has access to initiate a connection. For example, `cn=admin`,`dc=corp`, `dc=example`, `dc=com`. +Property description not available. @@ -125 +121 @@ _Required_ : No -Service account username. A service account is an account in your LDAP server that has access to initiate a connection. For example, `cn=admin`, `ou=corp`, `dc=corp`, `dc=example`, `dc=com`. +Property description not available. @@ -136 +132 @@ _Required_ : Yes -Select a particular subtree of the directory information tree (DIT) to search for user entries. The subtree is specified by a DN, which specifies the base node of the subtree. For example, by setting this option to `ou=Users`,`ou=corp`, `dc=corp`, `dc=example`, `dc=com`, the search for user entries is restricted to the subtree beneath `ou=Users`,`ou=corp`, `dc=corp`, `dc=example`, `dc=com`. +Property description not available. @@ -147 +143 @@ _Required_ : Yes -The name of the LDAP attribute in the user's directory entry for the user's group membership. In some cases, user roles may be identified by the value of an attribute in the user's directory entry. The `UserRoleName` option allows you to provide the name of this attribute. +Property description not available. @@ -158 +154 @@ _Required_ : No -The LDAP search filter used to find users within the `userBase`. The client's username is substituted into the `{0}` placeholder in the search filter. For example, if this option is set to `(uid={0})` and the received username is `janedoe`, the search filter becomes `(uid=janedoe)` after string substitution. It will result in matching an entry like `uid=janedoe`, `ou=Users`, `ou=corp`, `dc=corp`, `dc=example`, `dc=com`. +Property description not available. @@ -169 +165 @@ _Required_ : Yes -The directory search scope for the user. If set to true, scope is to search the entire subtree. +Property description not available.