Apologies I completely forgotten about this thread not till yesterday I was meddling with some similar settings. I’m actually using WebDAV with Nginx and till now I’m still using the old v4 firmware
What I’ve done was I created a so-called patch to allow manual drive mapping (do we still need that java applet thingy?), using the existing user/group which must be running in SSL due to the base64 hash authentication. I’ve tried MD5 digest but base64 seems to work way faster and more efficiently. Also initially I tried using PAM but that was too slow for deep paths, MyCloud is not that fast.
From my end it works as I expected, just need to tweak a few here and there then finally build the package. It seamlessly integrates beneath the WD Dashboard where you can add/remove users/shares and all will be visible in the drive mapping using the existing accounts (not the MD5 hashed accounts from the orion.db, which according to @Bennor from a previous post, is now empty). You could map locally or externally using the existing WD DDNS or even browse from the browser i.e. locally https://internal-hostname-or-internal-IP/internal-hostname or externally https://internal-hostname.device#######.wd2go.com[:SSL]/internal-hostname.
But I’m not sure the outcome in OS3 as my dev environment is staged. Below are some of my concerns:
Has WD completely removed drive mapping from the OS3 firmware? What happens after you login to mycloud.com? Can you see your files, upload/download/edit them from the portal? Or are we left using the WD desktop/mobile apps? I can’t proceed anything after login to the portal, there’s a line asking to upgrade IIRC. Though, I could still login remotely using the android app.
It would help me quickly revise the changes needed if someone could go through with me the differences, or possibly let me hands-on the OS3.