Compatibility Update for SMA version 12.0

[4oo4]

Starting with KACE SMA 12.0, the headers x-dell-api-version becomes x-kace-api-version, and x-dell-csrf-token becomes x-kace-csrf-token

https://support.quest.com/kb/276970/verifying-api-connection-with-postman

I'm guessing that some logic should also be added that can support the old and new version of the headers at the same time, if it's possible to query the SMA version and use the correct headers, or have the user supply this when they are calling the Connect-SMAServer cmdlet?

[ArtisanByteCrafter]

Hmm, there's several ways to handle something like this. I'm hesitant to simply replace the old header with the new as that would break existing installs. Perhaps a better approach would be to simply append both headers to the login request, that way the correct one is always present and the other harmless.

Unfortunately I no longer work where I had my SMA, so I have no access to test anything.

[4oo4]

Agreed, since Quest supports those older versions it should work for that. That's a great idea to use both headers, I didn't think about that. I just tested with sending both of them to our 12.0 appliance and it worked, so I updated my commit. So I think it could be merged once someone tests with an older version appliance.

Cheers