Open
Description
According to MD5 Hash End of Life & Signature Key Replacement, the MD5 hash in the transHash field is being phased out and will be removed from responses soon.
I see that transHash and transHashSHA2 are referenced a few places in the apicontractsv1.py module:
./authorizenet/apicontractsv1.py:8009: # Element {AnetApi/xml/v1/schema/AnetApiSchema.xsd}transHash uses Python identifier transHash
./authorizenet/apicontractsv1.py:8010: __transHash = pyxb.binding.content.ElementDeclaration(pyxb.namespace.ExpandedName(Namespace, 'transHash'), 'transHash', '__AnetApixmlv1schemaAnetApiSchema_xsd_transactionResponse_AnetApixmlv1schemaAnetApiSchema_xsdtransHash', False, pyxb.utils.utility.Location('https://apitest.authorize.net/xml/v1/schema/AnetApiSchema.xsd', 2542, 6), )
./authorizenet/apicontractsv1.py:8013: transHash = property(__transHash.value, __transHash.set, None, None)
./authorizenet/apicontractsv1.py:8107: # Element {AnetApi/xml/v1/schema/AnetApiSchema.xsd}transHashSha2 uses Python identifier transHashSha2
./authorizenet/apicontractsv1.py:8108: __transHashSha2 = pyxb.binding.content.ElementDeclaration(pyxb.namespace.ExpandedName(Namespace, 'transHashSha2'), 'transHashSha2', '__AnetApixmlv1schemaAnetApiSchema_xsd_transactionResponse_AnetApixmlv1schemaAnetApiSchema_xsdtransHashSha2', False, pyxb.utils.utility.Location('https://apitest.authorize.net/xml/v1/schema/AnetApiSchema.xsd', 2648, 6), )
./authorizenet/apicontractsv1.py:8111: transHashSha2 = property(__transHashSha2.value, __transHashSha2.set, None, None)
./authorizenet/apicontractsv1.py:8137: __transHash.name() : __transHash,
./authorizenet/apicontractsv1.py:8151: __transHashSha2.name() : __transHashSha2,
./authorizenet/apicontractsv1.py:26703:transactionResponse._AddElement(pyxb.binding.basis.element(pyxb.namespace.ExpandedName(Namespace, 'transHash'), pyxb.binding.datatypes.string, scope=transactionResponse, location=pyxb.utils.utility.Location('https://apitest.authorize.net/xml/v1/schema/AnetApiSchema.xsd', 2542, 6)))
./authorizenet/apicontractsv1.py:26731:transactionResponse._AddElement(pyxb.binding.basis.element(pyxb.namespace.ExpandedName(Namespace, 'transHashSha2'), pyxb.binding.datatypes.string, scope=transactionResponse, location=pyxb.utils.utility.Location('https://apitest.authorize.net/xml/v1/schema/AnetApiSchema.xsd', 2648, 6)))
./authorizenet/apicontractsv1.py:26839: symbol = pyxb.binding.content.ElementUse(transactionResponse._UseForTag(pyxb.namespace.ExpandedName(Namespace, 'transHash')), pyxb.utils.utility.Location('https://apitest.authorize.net/xml/v1/schema/AnetApiSchema.xsd', 2542, 6))
./authorizenet/apicontractsv1.py:26909: symbol = pyxb.binding.content.ElementUse(transactionResponse._UseForTag(pyxb.namespace.ExpandedName(Namespace, 'transHashSha2')), pyxb.utils.utility.Location('https://apitest.authorize.net/xml/v1/schema/AnetApiSchema.xsd', 2648, 6))Will the imminent removal of the transHash field from responses cause response parsing to break in the SDK as it stands today? Or will it handle the absence of the transHash gracefully?