The Azure Method

Best Binary Options Brokers 2020:
  • BINARIUM
    BINARIUM

    Best Binary Options Broker 2020!
    Ideal for beginners!
    Free Demo Account + Free Trading Education!
    Get a Sign-up Bonus:

  • BINOMO
    BINOMO

    2nd place in the ranking!

Examining Cisco AAA Security Technology

Chapter Information

Contents

  1. Securing Network Access by Using AAA
  2. Authentication Methods
  3. Authorization Methods
  4. Accounting Methods
  5. AAA Security Servers
  6. Summary
  7. Review Questions
  8. References

Chapter Description

From the Book

Authentication Methods

The main authentication methods considered are username and password, S/Key, token card and server, Password Authentication Protocol (PAP), and Challenge Handshake Authentication Protocol (CHAP) authentication. Each is covered in the following sections.

Username and Password Authentication

The most common user authentication method is the use of usernames and passwords. Username/password combination methods range from weak to strong in authentication power. Simple authentication methods use a database of usernames and passwords, whereas more complex methods use one-time passwords. Consider each of the methods shown in Figure 4-2, from the weakest at the bottom of the figure to the strongest at the top. Stronger authentication methods are better able to resist attempts to gain unauthorized access. Weaker methods are often easier to use and administer, and stronger methods are often harder to use and administer. Simple authentication methods use a database of usernames and passwords, and more complex methods use one-time passwords.

Figure 4-2 Authentication Methods and Ease of Use

The authentication methods outlined in Figure 4-2 are as follows:

No username or password—Some system administrators and users opt to not use the username/password capabilities of their network access systems. This is obviously the least-secure option. A network intruder only has to discover the access method to gain access to the networked system.

Username/password (static)—Stays the same until changed by the system administrator or user. Susceptible to playback attacks and password-cracking programs.

Username/password (aging)—Expires after a set time (usually 30 to 60 days) and must be reset, usually by the user, before network access is granted. Susceptible to playback attacks and password cracking but to a lesser degree than static username/password pairs.

S/Key one-time passwords (OTP)—An OTP method generating multiple passwords typically used for terminal logins. In S/Key, a secret passphrase is used to generate the first password, and each successive password is generated from the previous one by encrypting it. A list of accessible passwords is generated by S/Key server software and is distributed to users.

Best Binary Options Brokers 2020:
  • BINARIUM
    BINARIUM

    Best Binary Options Broker 2020!
    Ideal for beginners!
    Free Demo Account + Free Trading Education!
    Get a Sign-up Bonus:

  • BINOMO
    BINOMO

    2nd place in the ranking!

One-time passwords (OTP)—A stronger method, providing the most secure username/password method. Most OTP systems are based on a secret passphrase, which is used to generate a list of passwords. These passphrases are good for only one login and therefore are not useful to anyone who manages to eavesdrop and capture the passphrase. S/Key is an OTP method typically used for terminal logins.

Token cards/soft tokens—Based on something you have (for example, a token card) and something you know (for example, a token card personal identification number [PIN]). Token cards are typically small electronic devices about the size and complexity of a credit card-size calculator. There are many token card vendors, and each has its own token card server. The PIN is entered into the card, which generates a secure password. A token server receives and validates the password. The password interplay usually consists of a remote client computer, a network access server, and a security server running token security software.

You should choose and implement an authentication method based on the guidelines established in your network security policy. The policy should specify the desired balance between strength of security and ease of use.

Figure 4-3 shows an example of dialup access using usernames and password authentication. On the client end, Windows NT Dialup Networking prompts the dialup user for a username and password (as shown in Figure 4-4), which is sent over communication lines using TCP/IP and PPP to a remote network access server or a security server for authentication. Windows 95, Windows 98, and Windows 2000 operating systems have a similar authentication window.

Figure 4-3 A Remote Client Sending a Username and Password to a Network Access Server for Authentication

Figure 4-4 The Windows NT Dialup Access Username and Password Authentication Dialog Box

The remote user enters a username and password in the User name and Password fields and clicks the OK button to initiate a dialup connection.

After the user enters the username and password and clicks the OK button, Windows NT Dialup Networking transmits the username and password, over communication lines using TCP/IP and PPP, to a remote network access server or a security server for authentication, as shown in Figure 4-3.

Authentication of usernames and passwords is commonly used with secure Internet applications. For example, some Cisco Connection Online (CCO) applications require a user to be registered and to possess a username and password assigned by CCO. When the user accesses a secure CCO application using a Web browser, the application causes the Web browser to display a window requesting a username and password similar to that shown in Figure 4-4. The username and password may be validated using a AAA security server.

S/Key Authentication

Remote logins are vulnerable to network intruders using eavesdropping techniques to obtain the usernames and passwords. Intruders can use captured information in a replay attack to gain unauthorized access to the target system. The S/Key one-time password system was designed by Bellcore and others as a way to create passwords that can be safely sent over remote connections, thereby countering eavesdropping and replay attacks. With S/Key, only the one-time password crosses the network. The one-time password is a hash of the user’s secret password, so the secret password never crosses the network, and the hashed one-time password is never used again.

Where S/Key Got Its Name

After searching available RFCs and publications to find the meaning of the name S/Key with no success, I decided to ask Neil Haller, one of the original developers of S/Key and coauthor of several S/Key RFCs. Here is his reply: “I made up the name. It was originally called something else, but we discovered that name was trademarked. Then came a lengthy search for a name that we could trademark. S/Key came from desperation, trying many alternatives. I suppose the words ‘secure’ and ‘key’ were in my mind.”

A strong advantage of S/Key is that it protects against eavesdroppers without modification of remote client software, and it imposes little inconvenience on the users. Because S/Key is easy to integrate, many security-sensitive networks use it as their password security system. The S/Key client and host do not store any secret information. If either element is compromised, a network intruder cannot obtain secret passwords.

The S/Key system consists of three main parts, as shown in Figure 4-5: the remote client system that the user is using to gain remote access, S/Key client software installed on the remote client system that generates one-time passwords for the remote user, and S/Key host software running on the remote security server.

Figure 4-5 S/Key Authentication System Components: Remote Client, S/Key Client Software, and S/Key Host

S/Key Client Software

The S/Key client software that is usually installed on the remote system (also known as a password generator) generates a one-time password. When a one-time password is needed, the user enters a secret password into the S/Key client user interface. The S/Key client runs a one-way hashing algorithm using the secret password entered by the user and a seed value sent by the S/Key host to create the one-time password. S/Key uses either MD4 or MD5, which are one-way hashing algorithms, to create the one-time passwords. Each one-time password generated by S/Key consists of six short words. S/Key clients can have a command-line interface or a graphical user interface. An example of an S/Key password generated via a command-line interface is BONE YANK ROW RING WHOA TRUE. Figure 4-6 shows an example of the user interface of an S/Key password generator, the keyapp.exe program for Windows 95 systems.

Figure 4-6 The S/Key Client keyapp.exe User Interface

keyapp.exe has a graphical user interface that allows the user to enter the secret password, compute a one-time password, copy the password to the clipboard, and then paste the password into an authentication screen (such as Windows Dialup Networking) for the remote login. The authentication software on the remote client sends the one-time password in cleartext over the network to the S/Key host, which validates the one-time password. After the one-time password has been used, it is no longer useful to an eavesdropper. Some S/Key password generators create a list of one-time passwords that can be printed and manually entered into the authentication screen when needed.

S/Key Hosts

The S/Key host receives an authentication request from the S/Key client and sends a challenge/response with S/Key parameters that include a sequence number and a seed value used by the client hash algorithm. The S/Key client then sends the one-time password to the S/Key host. The S/Key host receives the one-time password and validates it by running the hash algorithm against it and comparing the hashed output with the previously received one-time password. If the values match, the user request is approved, and the received one-time password is stored in a file. The S/Key client and server keep track of the number of one-time passwords generated by decrementing a sequence number so that the user must reinitialize the S/Key calculator with a new secret password when the sequence number reaches 0. The CiscoSecure ACS for UNIX security server supports S/Key authentication.

An S/Key User Example

Consider an example of how a user named Sally uses S/Key from a remote UNIX system (with a command-line interface), through a network access server, to CiscoSecure ACS:

Sally identifies herself to the network access server in response to a standard prompt for authentication:

CiscoSecure ACS issues a challenge that includes a sequence number of 98 for the one-time password expected and a seed value of agst2359. The values are displayed to Sally by the network access server.

Sally enters 98 and agst2359 into her S/Key calculator program, called key, at the UNIX prompt. The secret password is any string of at least 10 alphanumeric characters generated by Sally, for Sally, and known only by Sally, as follows:

Sally now returns to her interaction with the network access server. She enters the S/Key password and is authenticated, as follows:

The next time Sally attempts network access, she will be prompted for the one-time password sequence number 97. The sequence number is one less than what was used for the previous authentication. When the sequence number reaches 0, Sally will not be able to log on without reinitializing the S/Key calculator with a new secret password.

Token Cards and Servers

Another one-time password authentication method that adds a new layer of security is accomplished with a token card and a token server. Each token card, about the size of a credit card, is programmed to a specific user, and each user has a unique PIN that can generate a password keyed strictly to the corresponding card. The password is then entered into the password field during a remote authentication.

The use of the token card requires the user to possess a token card or soft token software and to know a password to enable the token. This is called “something you have and something you know.” This represents one of the highest commercially available security methods of authentication. One-time password authentication takes place between the specified token server with a token card database and the remote client’s authentication software.

Token Card and Server Operation

Token card and server systems consist of a remote client PC, a token card, a network access server, and a token server. Token cards and servers generally work as follows:

The user generates a one-time password with the token card, using a security algorithm.

The user enters the one-time password into the authentication screen generated by the remote client (in this example, the Windows Dialup Networking screen).

The remote client sends the one-time password to the token server via the network and a remote access server.

The token server uses the same algorithm to verify that the password is correct and authenticates the remote user.

Token Card and Server Methods

Two token card and server methods are commonly used:

Time-based—In this system, the token card contains a cryptographic key and generates a password (or token) through the use of a PIN entered by the user. The password is entered into the remote client, which sends it to the token server. The password is loosely synchronized in time to the token server. The server compares the token received to a token generated internally. If they match, the user is authenticated and allowed access.

Challenge/response—In this system, the token card stores a cryptographic key. The token server generates a random string of digits and sends it to the remote client that is trying to access the network. The remote user enters the random string, and the token card computes a cryptographic function using the stored key and random string. The result is sent back to the token server, which has also computed the function. If the results match, the user is authenticated.

Token cards are now implemented in software for installation on the remote client. SofToken, which generates single-use passwords without the associated cost of a hardware token, is one example of software token cards.

Cisco Token Card and Server Support

Cisco supports authentication from the following four token-card servers within CiscoSecure ACS software:

CRYPTOCard RB-1 from CRYPTOCard Corporation

SecurID ACE/Server from RSA Security, Inc.

SafeWord from Secure Computing Corporation, which uses the DES Gold Card token card and the SafeWord SofToken software token card

Axent Technologies token server in CiscoSecure ACS 2.4 for Windows NT

See the “References” section of this chapter for more information about these servers.

PAP and CHAP Authentication

An important component of dialup access security is support for authentication accomplished with PAP and CHAP. The following sections look at the relative strengths of PAP and CHAP. We will examine how PAP and CHAP authentication operates. We will also consider Microsoft Challenge Handshake Authentication Protocol (MS-CHAP), an extension to CHAP.

PPP is a standard encapsulation protocol for the transport of different network layer protocols (including, but not limited to, IP) across serial, point-to-point links such as the PSTN or ISDN. PPP enables authentication between remote clients and servers using either PAP or CHAP.

PPP was designed to overcome the limitations of SLIP and to meet the need for an encapsulation protocol for serial lines based on Internet standards. PPP enhancements include encryption, error control, dynamic IP addressing, multiple protocol support, and connection negotiation and authentication.

Cisco network access servers are configured to perform authentication using the aaa authentication commands, which are covered in Chapters 5 and 6.

PAP Authentication Over PPP

PAP authentication, which uses PPP, provides a simple way for the remote client to establish its identity: a two-way handshake (see Figure 4-7). The handshake is done only after initial PPP link establishment. After the link establishment phase is complete, a username/password pair is repeatedly sent by the peer to the authenticator until authentication is acknowledged or the connection is terminated. Here are the messages exchanged during PAP authentication:

The remote client establishes the dialup link.

The remote client tells the network access server that it is running PPP.

The network access server, configured to use PAP, notifies the remote client to use PAP in this session.

The remote client sends the username and password in PAP format.

The network access server compares the username and password to that stored in its database and accepts or rejects the username and password entered.

Figure 4-7 The Steps in PAP Authentication Over PPP

PAP is not a strong authentication method. The username and password are sent in cleartext across the link. A protocol analyzer could be used to easily capture the password in an eavesdropping attack. PAP offers no protection from playback or repeated trial-and-error attacks. The peer is in control of the frequency and timing of the attempts. PAP provides a level of security similar to the usual user login at the remote host.

Usually PAP is used if it is the only authentication method supported by the client, when a plaintext password must be available to simulate a login at a remote host, or where the communication links are secure. CHAP is the preferred authentication method. Most vendor equipment and software support PAP, enabling greater interoperability between them.

CHAP Authentication Over PPP

CHAP is a stronger authentication method than PAP because the user’s actual password never crosses the communications channel. CHAP uses a three-way handshake to verify the identity of the peer. The handshake is done upon initial link establishment, and it may be repeated periodically thereafter to ensure the identity of the peer. The CHAP initiation sequence and three-way handshake occur as follows and as illustrated in Figure 4-8:

The PPP link is established after dialup. The network access server is configured to support PPP and CHAP.

The network access server tells the remote client to use CHAP.

The remote client responds with an OK.

The three-way handshake occurs as follows:

The network access server sends a challenge message to the remote client.

The remote client replies with a one-way hash value.

The network access server processes the received hash value. If it matches the station’s own calculation, authentication is acknowledged. Passwords are not sent over the link.

CHAP periodically verifies the identity of the remote client by using a three-way handshake. The network access server sends a challenge message to the remote node. The remote node responds with a value calculated using a one-way hash function (typically MD5). The network access server checks the response against its own calculation of the expected hash value. If the values match, the authentication is acknowledged. Otherwise, the connection is terminated immediately.

Figure 4-8 CHAP Authentication Steps Over PPP

CHAP provides protection against playback attack through the use of a variable challenge value that is unique and unpredictable. The use of repeated challenges is intended to limit the time of exposure to any single attack. The network access server (or a security server such as CiscoSecure TACACS+) is in control of the frequency and timing of the challenges. A major advantage of the constantly changing challenge string is that eavesdropping cannot be used to capture the challenge value and replay it back later in order to gain unauthorized access to the network because the value constantly changes. CHAP is preferable to PAP for authentication. One problem with CHAP has been that it was not supported in Windows NT authentication systems. Windows NT now supports the Microsoft version of CHAP, MS-CHAP.

CHAP authentication depends on a “secret” known only to the authenticator and the remote client. The secret is not sent over the link. Although the authentication is only one-way, by negotiating CHAP in both directions, the same secret set may easily be used for mutual authentication.

CHAP requires that the secret be available in plaintext form. Irreversibly encrypted password databases that are commonly available (such as the Windows NT SAM hive, the NT password database) cannot be used.

Most vendor efforts have been focused on enabling and improving authentication methods, particularly password access technologies. Improvements to authorization and accounting methods are being made more slowly.

MS-CHAP is the Microsoft version of CHAP, an extension of CHAP described in RFC 1994. MS-CHAP enables PPP authentication between a PC using Microsoft Windows 95, Windows 98, Windows NT, or Windows 2000 and a network access server. PPP authentication using MS-CHAP can be used with or without AAA security services.

MS-CHAP differs from standard CHAP in the following ways:

MS-CHAP is enabled while the remote client and the network access server negotiate PPP parameters after link establishment.

The MS-CHAP Response packet is in a format designed for compatibility with Microsoft’s Windows NT 3.5, 3.51, and 4.0 and Windows 95 networking products.

MS-CHAP lets the network security server (authenticator) control retry and password-changing mechanisms. MS-CHAP allows the remote client to change the MS-CHAP password.

MS-CHAP defines a set of reason-for-failure codes returned to the remote client by the network access server.

Cisco routers support MS-CHAP in Cisco IOS Release 11.3 and later releases with the ppp authentication ms-chap command.

Cisco routers support double authentication for PPP in Cisco IOS Release 11.3 and later. With double authentication, the remote host is authenticated with PAP or CHAP, and then the user is authenticated for remote access, potentially with one-time passwords such as token card passwords, which are not supported by CHAP. See the “Enabling Double Authentication” section in the Cisco IOS Security Configuration Guide, Release 12.0, for more information about double authentication.

What is Microsoft Azure Multi-Factor Authentication, and How does it Work?

Why is Multi-Factor Authentication Important?

There are a number of reasons to consider using multi-factor authentication (MFA). You most likely are increasingly more connected. Like most of us, you’re using smart phones, tablets, laptops and PCs. You have several options to access your accounts on multiple devices and from a range of network resources.

Compromising multiple authentication factors presents a significant challenge to attackers. Even if an attacker learns your password, it’s useless without also having possession of your trusted device.

MFA proves an easy-to-use, scalable, and reliable solution to gain a second method for authenticating users. You can manage your own devices quickly, it provides strong authentication using the highest industry standards, and Microsoft guarantees 99.9% availability.

What is Multi-Factor Authentication?

Azure Multi-Factor Authentication is a two-step verification method that provides a second critical layer of security to user sign-ins and transactions. It works by requiring any two or more verification methods such as:

  • Passwords or phrases
  • A trusted device that is not easily duplicated (such as your phone)
  • Biometric (i.e. finger print, voice, your image, retinal scan)

Azure MFA is Microsoft’s solution to two-step verification. It helps safeguard access to your data and applications while meeting user demand for a simple sign-in process. Strong authentication is had through a range of verification methods including phone calls, mobile applications or text messaging.

The Azure Method

Authentication is very important when you use dynamic IP addressing (DHCP) for computers on the trusted or optional network. It is also important if you must identify your users before you let them connect to resources on the external network. Because the Firebox® associates a user name to an IP address, we do not recommend that you use authentication features in a network with multi-user computers such as Unix servers, terminal servers or Citrix servers. The Firebox authenticates one user per computer.

With WatchGuard® System Manager, you can configure authentication on a per policy basis. For example, you can force some users to authenticate before they connect to an FTP server although they can browse the Internet without authentication.

To get access to services such as HTTP or FTP the user types a domain along with their login name and password. For the duration of authentication, the user name is associated with connections coming from the IP address from which the user authenticated. This makes it possible to monitor not only the computers from which connections originate, but also the users who start the connection. While the user is authenticated, all the connections that the user starts from the IP address include the session name.

Copyright © 1996 – 2005 WatchGuard Technologies, Inc. All rights reserved.
Legal Notice/Terms of Use

7 Binary Options

As a dynamic industry, the online financial trading industry is constantly undergoing market innovations. For example in the last 2 years, it has been flooded with numerous automated trading systems that claim to simplify the entire trading process while increasing the profitability of traders. But with so many trading systems inundating the market, it has made the task of verifying the so-called claims of these trading systems practically impossible for beginner traders.

As such we have taken upon ourselves the task of verifying the legitimacy of this automated trading software to help prevent our readers from being scammed by fake systems. For this review, we will try to verify some of the things that the Azure method claims to be able to do for its users. So can the Azure method truly provide traders with the best trading opportunities or it is just marketing hype? Read our in-depth review to find out.

Basic information:

Cost: Free
Software: 100% Automated
Max Returns: Up to 90%
Minimum Deposit: $200
Countries: All nations

  • Free software
  • Reasonable winning ratio
  • No conclusive evidence of the workability of the Azure method
  • Having to sign up with an unregulated broker
  • Lack of technical details
  • No Technical Support provided
  • Fake Testimonials

7BO Verdict:

Not Reliable Service

What is Azure Method?

The Azure method is actually said to be an automated binary options trading system that was developed by an individual by the name of Anthony Azure. While the system claims a reasonably high success rate of 65% to 85%, actual details on the system remain fact quite sketchy. The promotional video about the Azure method fails to provide any detailed information on how the trading system actually works.

In addition, our research on the internet yielded virtually no information about the developer leading us to believe that Anthony Azure is just a figment of someone’s imagination.

Screenshot

How Does It Work?

As mentioned earlier, the Azure method is a fully automated binary options trading system which takes over the task of trading the markets from the trader. All that the trader has to do is to sit back and watch the profits rolling in. The Azure method also claims to be able to help beginner traders shorten their learning curve. With a reasonably high winning rate of an average of 70%, this means traders should, in fact, be able to win 7 trades out of 10 trades made. All a trader has to do in order to gain access to this software is to complete a few simple steps such as:

  1. Visit their website
  2. Enter all the requested details in the form provided on the website
  3. Once directed to the account creation page, set up a trading account
  4. Deposit the minimum initial deposit required to open an account

Once you have completed the 4 steps above, you will be linked to a binary options broker recommended by the trading system. And after you have been linked to the recommended broker, you will be able to start trading immediately with the Azure method.

Take note that although the Azure method claims a success rate of an average of 70%, the developer had not provided any conclusive trading data to support that claim. Instead, what we found was numerous fake testimonials using stock pictures extolling the trading benefits of the Azure method.

Final Conclusion

While everything about the Azure method seems straightforward initially, upon closer inspection, we noted that the software has actually been portrayed in a misleading manner. First of all, the testimonials provided on their website uses stock images leading us to think that all the testimonials are probably fake as well.

Second of all, although the developer claims to provide technical support for his trading system, the live chat feature on the website is not manned by any technical support staff.

All these red flags lead us to conclude that the Azure method is nothing more than a scam designed to get unsuspecting traders to sign up with an unregulated broker. As such, we highly recommend that our readers stay away from the Azure method.

Use the Azure portal to access blob or queue data

When you access blob or queue data using the Azure portal, the portal makes requests to Azure Storage under the covers. A request to Azure Storage can be authorized using either your Azure AD account or the storage account access key. The portal indicates which method you are using, and enables you to switch between the two if you have the appropriate permissions.

Permissions needed to access blob or queue data

Depending on how you want to authorize access to blob or queue data in the Azure portal, you’ll need specific permissions. In most cases, these permissions are provided via role-based access control (RBAC). For more information about RBAC, see What is role-based access control (RBAC)?.

Account access key

To access blob and queue data with the account access key, you must have an RBAC role assigned to you that includes the RBAC action Microsoft.Storage/storageAccounts/listkeys/action. This RBAC role may be a built-in or a custom role. Built-in roles that support Microsoft.Storage/storageAccounts/listkeys/action include:

  • The Azure Resource Manager Owner role
  • The Azure Resource Manager Contributor role
  • The Storage Account Contributor role

When you attempt to access blob or queue data in the Azure portal, the portal first checks whether you have been assigned a role with Microsoft.Storage/storageAccounts/listkeys/action. If you have been assigned a role with this action, then the portal uses the account key for accessing blob and queue data. If you have not been assigned a role with this action, then the portal attempts to access data using your Azure AD account.

The classic subscription administrator roles Service Administrator and Co-Administrator include the equivalent of the Azure Resource Manager Owner role. The Owner role includes all actions, including the Microsoft.Storage/storageAccounts/listkeys/action, so a user with one of these administrative roles can also access blob and queue data with the account key. For more information, see Classic subscription administrator roles.

Azure AD account

To access blob or queue data from the Azure portal using your Azure AD account, both of the following statements must be true for you:

  • You have been assigned the Azure Resource Manager Reader role, at a minimum, scoped to the level of the storage account or higher. The Reader role grants the most restricted permissions, but another Azure Resource Manager role that grants access to storage account management resources is also acceptable.
  • You have been assigned either a built-in or custom role that provides access to blob or queue data.

The Reader role assignment or another Azure Resource Manager role assignment is necessary so that the user can view and navigate storage account management resources in the Azure portal. The RBAC roles that grant access to blob or queue data do not grant access to storage account management resources. To access blob or queue data in the portal, the user needs permissions to navigate storage account resources. For more information about this requirement, see Assign the Reader role for portal access.

The built-in roles that support access to your blob or queue data include:

  • Storage Blob Data Owner: For POSIX access control for Azure Data Lake Storage Gen2.
  • Storage Blob Data Contributor: Read/write/delete permissions for blobs.
  • Storage Blob Data Reader: Read-only permissions for blobs.
  • Storage Queue Data Contributor: Read/write/delete permissions for queues.
  • Storage Queue Data Reader: Read-only permissions for queues.

Custom roles can support different combinations of the same permissions provided by the built-in roles. For more information about creating custom RBAC roles, see Custom roles for Azure resources and Understand role definitions for Azure resources.

Listing queues with a classic subscription administrator role is not supported. To list queues, a user must have assigned to them the Azure Resource Manager Reader role, the Storage Queue Data Reader role, or the Storage Queue Data Contributor role.

The preview version of Storage Explorer in the Azure portal does not support using Azure AD credentials to view and modify blob or queue data. Storage Explorer in the Azure portal always uses the account keys to access data. To use Storage Explorer in the Azure portal, you must be assigned a role that includes Microsoft.Storage/storageAccounts/listkeys/action.

To view blob or queue data in the portal, navigate to the Overview for your storage account, and click on the links for Blobs or Queues. Alternatively you can navigate to the Blob service and Queue service sections in the menu.

Determine the current authentication method

When you navigate to a container or a queue, the Azure portal indicates whether you are currently using the account access key or your Azure AD account to authenticate.

The examples in this section show accessing a container and its blobs, but the portal displays the same message when you are accessing a queue and its messages, or listing queues.

Account access key

If you are authenticating using the account access key, you’ll see Access Key specified as the authentication method in the portal:

To switch to using Azure AD account, click the link highlighted in the image. If you have the appropriate permissions via the RBAC roles that are assigned to you, you’ll be able to proceed. However, if you lack the right permissions, you’ll see an error message like the following one:

Notice that no blobs appear in the list if your Azure AD account lacks permissions to view them. Click on the Switch to access key link to use the access key for authentication again.

Azure AD account

If you are authenticating using your Azure AD account, you’ll see Azure AD User Account specified as the authentication method in the portal:

To switch to using the account access key, click the link highlighted in the image. If you have access to the account key, then you’ll be able to proceed. However, if you lack access to the account key, you’ll see an error message like the following one:

Notice that no blobs appear in the list if you do not have access to the account keys. Click on the Switch to Azure AD User Account link to use your Azure AD account for authentication again.

Best Binary Options Brokers 2020:
  • BINARIUM
    BINARIUM

    Best Binary Options Broker 2020!
    Ideal for beginners!
    Free Demo Account + Free Trading Education!
    Get a Sign-up Bonus:

  • BINOMO
    BINOMO

    2nd place in the ranking!

Like this post? Please share to your friends:
All About Binary Options Trading
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: