Well, we would have if it was only a configuration change, but it’s not. Not a single Java OAuth 1.0 library has HMAC-SHA256 built-in that we found, and our long-used Jersey client makes it especially hard to add HMAC-SHA256 support (requires a dozen custom classes worth of code). Additionally, I was hoping that Netsuite would give us a way to create an endpoint that explicitly would not accept HMAC-SHA1, so we could test that our new code was working. For all we know, it could still be creating the signature using HMAC-SHA1, but since that still works, the calls are working, and giving us a false sense of security. In other words, we have no way of knowing, with any certainty, that it works at all prior to pushing the code to production and just praying that it works. It is that fact, not the required switch to HAMC-SHA256, that I have an issue with. Why doesn’t Netsuite give us the tools to control this, or at least test it appropriately?