Add support for max_page_size in the vault_ldap_auth_backend - #1878
Conversation
|
Tests fail on |
|
@laugmanuel , @vinay-gopalan , @raymonstah please take a look, if anything needs changing please let me know. |
| }, | ||
| "max_page_size": { | ||
| Type: schema.TypeInt, | ||
| Default: -1, |
There was a problem hiding this comment.
If the Vault API returns a default for this field then we should not set a Default in the provider. We can instead set this field to Computed: true.
There was a problem hiding this comment.
The issue is that currently Vault API returns the wrong value (0) instead of (-1), which breaks most LDAP implementations, as it causes no results to be sent. They have their own PR with a fix being made, but this change makes it backwards compatible.
https://developer.hashicorp.com/vault/api-docs/auth/ldap#max_page_size
There was a problem hiding this comment.
ok, thanks for the explanation. I think in this case we can set the Default then.
|
@benashz Hi, would it be possible to merge this? |
Community Note
Relates OR Closes #1862
Release note for CHANGELOG:
Output from acceptance testing: