locked
Dashboard REST API for driver signing submission RRS feed

  • Question

  • I'm trying to implement Windows 10 driver signing using the dashboard REST API. I'm using the following pages as reference:

    https://msdn.microsoft.com/en-us/library/windows/hardware/dn800660(v=vs.85).aspx

    https://msdn.microsoft.com/en-us/library/windows/hardware/dn800654(v=vs.85).aspx

    However, when I finally managed to make it work it created not a driver signing submission but a hardware compatibility submission which is not what I want. It may be that I simply formatted an incorrect JSON object, but the API documentation is very vague about specific field values and their meaning.

    Is there any better documentation I might have missed? Does this REST API implements driver signing at all? I've read a 1-year-old interview that it had not been available, but now that Win10 AR is almost there, we need a tool to sign drivers for it in automated way.

    Monday, July 11, 2016 2:32 PM

Answers

  • I just recently discovered that the REST API for Attestation and HLK signing appers to have been updated to support the new dashboard.  If you're still interested, I'd start here for details:

    https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/dashboard-api

    It seems to be working for us although I do see intermittent failures (HTTP 502/503 errors, occasional complaints about my submission not being the "initial submission")

    Wednesday, February 20, 2019 8:10 PM

All replies

  • I just recently discovered that the REST API for Attestation and HLK signing appers to have been updated to support the new dashboard.  If you're still interested, I'd start here for details:

    https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/dashboard-api

    It seems to be working for us although I do see intermittent failures (HTTP 502/503 errors, occasional complaints about my submission not being the "initial submission")

    Wednesday, February 20, 2019 8:10 PM
  • Indeed, thank you for the reply.

    As it happens, I've found out about this new API quite a while ago and have already implemented automatic signing with it (although I've never seen those failures you are talking about...).

    But I've completely forgot about this long abandoned thread, or I'd post here that the problem has been solved. It's good to have an aswer with a link here, so that other people might find it useful if they get here from searching for the same question.



    Wednesday, February 20, 2019 8:27 PM
  • Yes, it's helpful, indeed. :)

    moolwalk

    Wednesday, April 17, 2019 4:27 AM