HMAC algorithms supported by azure API connection

Giovanni Canarecci 20 Reputation points
2024-09-05T13:32:00.3666667+00:00

Hello,

I have an azure API connection which returns "Server HMAC algorithm not found" for a connection to an AWS SFTP folder.

The folder follows AWS TransferSecurityPolicy-2023-05 meaning that it allows for:

"SshMacs": [
"@openssh.com",
"
@openssh.com"
],

https://docs.aws.amazon.com/transfer/latest/userguide/security-policies.html#security-policy-transfer-2023-05

Does azure API connection support those algorithms? Or maybe "only" hmac-sha2-512 and hmac-sha2-256?

If those "etm" algorithms are supported, I am not sure what the issue may be.

Any help would be appreciated! :-)

Best,

Giovanni

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
{count} votes

2 answers

Sort by: Most helpful
  1. Giovanni Canarecci 20 Reputation points
    2024-09-09T09:05:00.52+00:00

    Hello @Anonymous , thank you for the link! :-)

    If I read it correctly, clicking on "Encryption algorithms: Review Encryption Method - SSH.NET", the relevant information should be Message Authentication code (screenshot):
    User's image

    That sounds like the same algorithms are available. The SFTP folder follows AWS TransferSecurityPolicy-2023-05 meaning that it allows for:
    "SshMacs": [
    "@openssh.com",
    "
    @openssh.com"
    ].

    Could it be I am misreading something? Azure does not give any more details than that and I am otherwise able to connect to the SFTP folder using WinSCP manually. Since "******@openssh.com" is mentioned on both sides, I am not sure what the issue may be. :-D

    Best,

    Giovanni


  2. Anonymous
    2024-09-23T11:03:45.0633333+00:00

    Hi - To close the loop here too

    We have reported the issue to the Product Owners who have triaged and acknowledged the current limitation; the managed SFTP-SSH connector implementation does not yet support the HMAC algorithms called out here

    They have created a task item for the backlog. But, there is no date to share for delivering a fix at this time.

    The interim workaround would be to use the built-in connector equivalent but I appreciate this would require moving to Logic Apps Standard which may or may not be possible .

    The other obvious workaround is to “offload” the integration step to code, to an Azure function, whereby you would have full control (should you choose to provide the integration yourself as an interim solution)

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.