The example host application that we will show you in this video is designed to demonstrate user authentication upstream of Exago. Followed by configuration of the subsequent Exago session based on those authentication values. It further demonstrates options for direct report or Dashboard execution and navigation to the full Exago user interface. We will begin by running the application to visualize the options. To authenticate, we will provide a user ID and a company. If the user ID provided is anything other than the string admin a-d-m-i-n an end-user Role will be activated. That Role will lock all folders in the full UI for the user as well as removing all report designer access, except for ExpressView. If we click the Report button in the host application, we will specific reports execute in to separate <div>s on the page. If we click Full UI, we will be brought to the Exago user interface. At this point, we will go back to Visual Studio to look at the code and explain how this integration works.
This example application is written in C#. We will walk through it together. If you would like a copy of the test application, submit a ticket to our Service or Support teams.
Outside of Visual Studio, we configured two Roles in the existing Exago configuration, as this code expects them. The configuration of these Roles does not need to adhere to specific guidelines, though the Roles for this example must be named Admin and End User.
The session modifications are structured using a batch REST call here. Developers can utilize the batch REST endpoint to group together multiple sequential calls into a single network request. For environments which make a number of programmatic alterations to the session configuration, batch REST can significantly reduce the network load and time to create the session. This feature is used purely for performance gain in session instantiation and the process of steps here mimics that of a session being configured four separate REST calls. We first create a batch REST object, then each element of that object represents a separate action. In this case, the first element includes the keyword Sessions and the method POST to instantiate the session. The second element will PATCH the value for the user ID parameter. The third element assigns Storage Management identity values. The fourth element activates a Role.
Congratulations! You’ve now integrated Exago with a very basic host application! This video concludes the Exago Technical Training Series. Thank you for watching, and congratulations on configuring your Exago environment!