Legacy driver conversion needs means to identify process sending I

[John Bond]

I am still converting a massive and old WDM driver. We found where the old
driver copies the Irp->Tail.Overlay.OriginalFileObject in order to identify
which process sent the WDFREQUEST. While inspecting MSDN's docs on the IRP
struct, we noted that the OriginalFileObject member of Tail.Overlay is not
recommended for driver usage. So here is my question:

What is the ideal way for a KMDF driver to determine which instance of our
DLL (which user mode app) sent the WDFREQUEST?

What our driver must do is enforce that one and only one app open certain
items like channels on our boards.

OriginalFileObject was chosen many moons ago by another engineer for unknown
reasons with unknown guidance. I need to have a means to positively and
uniquely identify which HANDLE was used in the call to
DeviceIoControl(hDevice, ...) ---OR--- uniquely identify the process by its
process ID.

As always, all input is appreciated. John Bond