[Authorisation] Woes after OS reinstall

Tadvi Kunik

Subject: Feedback: Please add a manual deauthorization button to the Member Center
Message:
To the StreamFab Development Team,
As a lifetime license holder, I would like to provide some feedback regarding the device authorization process.
Recently, I was unable to log into the software because my account reached its device limit (due to a glitch showing “2/1” devices used). The most frustrating part of this experience was discovering that there is no way for users to manually manage or remove old devices directly from the Member Center on your website.

When a computer breaks, or an OS is reinstalled, we are locked out and forced to contact customer support just to reset the license.

My suggestion: Please add a “Deauthorize” or “Remove Device” button next to the physical MAC addresses listed in the License Authorizations section of the web dashboard. Giving users the ability to manage their own active devices would provide a much better user experience and save your customer support team a lot of time handling simple reset requests.
Thank you for your time and consideration.
Best regards,
Tadvi Kunik

Germania

Tadvi Kunik Please add a “Deauthorize” or “Remove Device” button next to the
physical MAC addresses listed in the License Authorizations section of the web dashboard

It exist for years:

Perhaps you used the wrong url (dvdfab instead streamfab) - see here

0xFeedBeef

I’ve renamed the thread to better reflect the nature of the complaint.

Stan001

~~I can use https://dvdfab.cn/member.htm#license_managemen~~
After checking on one device, there is no option to deauthorize any product in the member center. Maybe it’s the device?
So I can’t deauthorize any DVDFab product on this device using the member center.
In fact, my whole order history is blank with DVDFab products via the DVDFab member center.

Or use https://streamfab.com/member.htm#license_management
Although after checking there, I can only deauthorize StreamFab from the StreamFab member center site.
No DVDFab products are listed there.

Or if you stll have access to the old devive, you can deauthirsize right from SF itself:
See here > https://forum.dvdfab.cn/d/470541-how-to-use-streamfab-7-and-more-details/3

Stan001

In fact now I went through standard PC browser , Chrome and Edge, and I get NO deauthorization option through https://dvdfab.cn/member.htm

As I said in my other post, we should still be able to deactivate via SF as shown below, but I am not trying.
If you still have access to the old device, you can deauthorize it right from SF itself:
See here > https://forum.dvdfab.cn/d/470541-how-to-use-streamfab-7-and-more-details/3

ADDED: I now have also reported this to feedback. I still see no option to deaturize in dvdfab member center, not for any of their software listed there.

Stan001

I feel this NEEDS to be ADDED.
I had a long talk with DVDFAB support; they removed the ability to deauthorize via the member center.

READ TERMS:
https://www.dvdfab.cn/terms-of-license-authorization.htm
#2

Authorization Management & Deauthorization
You can manage your device authorizations through the software client or, with limitations, through the online User Center.

Client-Side Deauthorization (Recommended): You may deauthorize a computer directly within the software client at any time. There is no limit to the number of times you can deauthorize and re-authorize devices using the client interface, provided you do not exceed your total concurrent device limit.
User Center Deauthorization (Web-Based): To prevent abuse, strictly limited deauthorization options are available via the online User Center (for situations where you cannot access the computer, e.g., hardware failure or loss):
1-PC License: You may deauthorize your current device via the User Center only once per year.
Multi-Computer License: Deauthorization via the User Center is not supported for multi-computer licenses. You must manage authorizations directly on the client devices.

0xFeedBeef

Stan001 The whole issue could, of course, be easily avoided altogether if the back-end checked MACs first and then decided whether to reject the authorisation. That way, if you had a active authorisation with the same MACs, you’d still be authorised.

I’m still not certain what abuse on a functional level they try to prevent- it’s not like you get a separate allocation of tokens per authorisation… The only use-case for multiple instances that I had ever found is as a work-around the deficiency of SF in that SF can’t do concurrent downloads from different providers 🤷‍♂️