fbpx
  • Another way of doing consulting.

Start » Test Users D365FO

Test Users D365FO

During the development cycle of a D365FO functionality, it is necessary for a third party (a functional consultant or a key user, for example) to test said functionality before considering it valid, with a set of data and permissions that are as realistic as possible. An interesting option, and one that speeds up this process, is that the user who is testing the functionality does so in the same development virtual machine.

Many times it is enough to start the D365FO web client from Visual Studio, simply by marking a startup project «startup project«:

Inside it, a startup object «startup object«:

And click on «Start«:

But other times this is not enough. For example, if what we want to test is the effectiveness of certain functionality under certain access permissions, we must create an independent user and assign the corresponding roles: If we do it with the administrator user (which is the one that starts from VisualStudio) we will not be able to test it, since these security restrictions do not apply to it.

To do this, you need, in this order:

  1. If we are working with Visual Studio, we will already have it. But if not, we must first assign the administrator user (which will be the effective user when we start the client from Visual Studio). For this, we use the utility «Admin User Provisioning» that comes in the virtual machine.Note: it is necessary that the email of the administrator user belongs to some AAD domain.

    From this moment, we can start the web browser to connect to D365FO using the indicated email and password. When we enter, we will do it as an administrator user, as we can see in the upper right corner.

     

  2. Now, you have to register the new user. To do this, we go to the menu «System Administration>users>users“, and we click on “New«:
    In this new version, the authentication mechanism has changed from Active Directory to Active Directory Federation Services (ADFS), which also requires you to specify the URL of the authentication provider.
  3. The virtual machine is isolated and does not belong to any Windows domain, so we will use an email to identify the user. We'll put it in "user name" and in "e-mail«. For the authentication provider we will have to use:
      1. If the AAD domain has its own authentication provider, we will use its URL (eg, https://auth.adfs.mycompany.com). If we do not have this information, it may be necessary to contact the Systems Department to obtain it.

    If the domain does not have its own authentication provider, then:

    1. If the user's email belongs to the same AAD domain as the admin user: https://sts.windows.net
    2. If the user's email belongs to another Azure Active Directory domain, the AAD generic should be used: https://sts.windows.net/XXXXX.XXX, where XXXXX.XXX is the email domain (eg, https:/ /sts.windows.net/emiralfg.com)

    There is a fourth very interesting option, which is to link it to a Microsoft account: It is the one used, for example, to enter Skype. The authentication provider follows the pattern of a user belonging to another AAD domain, that is, https://sts.windows.net/XXXXX.XXX, where XXXXX.XXX is the domain of the email address.

    In this example we have used an outlook.com account (which is a Microsoft account). We will then have to assign https://sts.windows.net/outlook.com as the authentication provider. If you have an outlook.com account, or still have an old hotmail.com account, you can use them:

    Theoretically, this should work with any email linked to a Microsoft account. In our tests, for example, we have managed to use a yahoo.com email account, after linking it to a Microsoft account. Keep in mind that the password, in the general case, IS NOT the one for the email, but for the Microsoft account (which in the case of outlook.com and hotmail.com is the same).

    Now, we can assign roles. At a minimum, you will need the “System user” role.

From this moment on, the user with the indicated email should already be able to enter the development machine to do their tests.

Enjoy it 🙂

Jose Miguel Guisado

Latest related posts