Skip to content
This repository has been archived by the owner on Jul 3, 2023. It is now read-only.

Importing 4096 bit KeyPair wrongly recognized as 2048 bit key size #68

Closed
mosersil opened this issue Apr 13, 2021 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@mosersil
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.14.10

Affected Resource(s)

  • pingfederate_keypair_signing

Terraform Configuration Files

/* note mykey.p12 is a 4096 bit lentgh RSA key */
resource "pingfederate_keypair_signing" "mosi_key" {
 file_data = filebase64("/path/to/mykey.p12")
 password = "whatever"
}

Debug Output

Panic Output

Expected Behavior

When running terraform plan, I would expect TF will try to create a new KeyPair with key size 4096 bit.

Actual Behavior

Terraform recognized the loaded key with key size 2048bit.

Steps to Reproduce

  1. Generate 4096 bit keypair and configure resource as described above
  2. terraform plan
  3. check output of TF plan - note key_size is 2048

Important Factoids

References

@mosersil mosersil added the bug Something isn't working label Apr 13, 2021
iwarapter added a commit that referenced this issue Apr 13, 2021
mosersil pushed a commit to mosersil/terraform-provider-pingfederate that referenced this issue Jan 21, 2022
…github.com/hashicorp/terraform-plugin-mux-0.1.1

Bump github.com/hashicorp/terraform-plugin-mux from 0.1.0 to 0.1.1
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant