What is "Trusted Devices" for your blizz account?

50% helpful (1/2)

Read this article in JapaneseGerman

                                                                                                                                      

This article applies to all blizz users and customers.

 

What is "Trusted devices"?

Trusted Devices is an extra layer of security for your blizz account.

As a preventive measure to ensure your account's security, you need to authorize a new device on which you sign in to your account for the very first time.

Note: You will receive an E-Mail from TeamViewer as blizz is part of the TeamViewer family and the blizz account run through the same high level of security as the TeamViewer servers.

How to authorize a trusted device?

To add your device to your Trusted Devices, please follow these steps:

  • Sign in to the blizz software or the blizz online portal with your blizz account credentials on your device. If you do this the first time, a pop-up appears.Pic 1.png

 

  • At the same time, a device authorization email from TeamViewer Sign In Confirmation is sent to the email address of your blizz account.Pic 2.png

 

  • Open this E-Mail and click the Add to trusted devices link within the device authorization email to authorize the device. Pic 3.png

 

Note: The link in this email is only valid for 24 hours. If the link expires, you will need to sign in to your account once more on your device. A new authorization email will be generated and sent to your account.

  • After clicking the link, you can complete the authorization process by choosing the kind of trust scope you would like to grant. Please note, that the location may not always be 100% exact, as it is given by your Internet Service Provider. Please choose from the dropdown menu whether you would like to trust this specific device or the IP address permanently or whether you would like to trust this device only once

 

Pic 5.PNG

  • Finalize the steps by clicking on the Trust button. A message is displayed informing you that the new device is now a trusted device.device_successfully_added.png

Now you are able to sign in on the new device with your Blizz account credentials.

 

Trust Scope

Trust device

You are setting the trust for the specific device.

Note: Due to technical reasons there is more than one trust per device. You will need to set separate trusts for the blizz software and the blizz online portal.

 The browser trusts will be lost as soon as the cookies are deleted.

Trust IP address

You can decide whether you would like to trust a single device only or if you would like to trust the IP address. That means your account's trust is extended to all other devices in the same local network. You can now login with all devices/instances that log in from the trusted IP address.

When the IP address changes, you will get the trusted device mails only for new devices, that haven't signed in before the IP address has changed.

Trust only once

This trust scope can be used, when you only want to login on the device once (on a device from your customer, in an Internet cafe,... ). It is only valid for one login on the device. 

The trust will be deleted after you logged in from the trusted device. When you try to re-login you will get the trusted device message again.

 

Two Factor Authentication (Alternative to Trusted Devices)

As an alternative to the Trusted Devices authorization process, you can enable two-factor authentication on your account instead. If you are using two-factor authentication, then the Trusted Devices authorization email won’t be required anymore when you sign in to your account on a new device.

You can activate the 2 Factor Authentication once you log in with your blizz account. Click on your name on the upper left side, and then click on the pencil on the upper right side to edit your account. Under Two Factor Authentication, choose Activate. You will then be guided through the process. 

Pic 6.PNG

 

 

Version history
Revision #:
10 of 10
Last update:
2 weeks ago
Updated by:
 
Labels (3)
Contributors