PA Review: Signature creation about signdocs HOT 4 CLOSED

Running into error after pushing to Heroku, working to resolve: Aws::KMS::Errors::AccessDeniedException: An error occurred (AccessDeniedException) when calling the CreateKey operation: You don't have the kms:TagResource permission that is required to add tags during key creation. from /app/vendor/bundle/ruby/2.5.0/gems/aws-sdk-core-3.104.3/lib/seahorse/client/plugins/raise_response_errors.rb

from signdocs.

Running into error after pushing to Heroku, working to resolve: Aws::KMS::Errors::AccessDeniedException: An error occurred (AccessDeniedException) when calling the CreateKey operation: You don't have the kms:TagResource permission that is required to add tags during key creation. from /app/vendor/bundle/ruby/2.5.0/gems/aws-sdk-core-3.104.3/lib/seahorse/client/plugins/raise_response_errors.rb

RESOLVED
I ended up not having to change any permissions for my AWS user. Must have been related to something else that was otherwise resolved.

from signdocs.

• wow this is so cool! Had so much fun creating my signature. Re: Signature "seals" bear the fingerprint of the user's unique cryptographic key, I'm assuming this is under the hood for the signature I created.

from signdocs.

Thanks Vanessa!

Re: Signature "seals" bear the fingerprint of the user's unique cryptographic key, I'm assuming this is under the hood for the signature I created.

Correct...when a user is initialized, an AWS public key is created for them and sits on AWS servers. I haven't implemented much with that yet, but the "fingerprint" is an MD5 hash of the public key. So eventually the idea is that the fingerprint verifies the authenticity of a user's seal :)

from signdocs.