tech note

1. Checking of Management Portal credentials should happen through API or direct in the existing application.

1. If the account was not found, ? ( where to check this)

1. then the browser should POST the same username/password over to the Management Portal via a JS POST. ( Which Api )

1. This page will likely be a modified version of the existing page to be easier to integrate to the login html application,

2. and ideally should accept JSON payload posts and respond with JSON.

3. If we can use the exact same login page control and simply check the payload before doing the normal load to know what “mode” it’s being requested to operate in.

4. So if the content type is application/json, then we know to check the body as JSON to get the username and password to validate against DNN.

2. The existing DNN/Management Portal authentication process will be used, if successful then then user will be authenticated, and the back end code will migrate the users by posting a registration request to the API, which will add the new user account and respond back with a JWT

1. Note: If authentication fails at the management portal during this step, we’ll need to be able to pass back the login failure messages back to the new HTML Login application. See above for a possible strategy of modifying the existing page to operate as a JSON endpoint.

3. The JWT will be sent back into the browser and stored in session storage. 

4. The browser will continue onto the DNN site as usual.

1. Are we going to use the same encryption format in the postgres database that is being used in the Management Portal?

1. In every case we should be using the standard .NET Core 6/Standard Identity setup

2. . So for the encryption/password hash we will need to take the clear text password that was passed and during registration the Identity library will take care of the password encryption/hashing for us.

2. Should we block the user from accessing after 3 wrong attempts.

1. We should look into how to configure that to work with .NET Identity if it’s possible to have that library handle it for us. So if the user is “already migrated” then the ASP.NET Identity system will handle that for us, but if they are not yet migrated then whatever exists in the Management Portal will have to be relied upon.

2. This option simply needs to be researched but not yet implemented.

3. While migrating the user information from the management portal . We need to migrate their Roles and list of Schools they can access. How are we planning to do that as the Role Id and school Id may differ ? (are we going to do directly or through nightly job)

1. We need to figure out how we will migrate that information as well. The schools will be stored in the Business API and can be accessed by GUID (or other query params). We would likely then need to add a table to the Users API tables that would be a user to schools relationship table.

2. During migration then, the process will pull in the list of schools and insert them into a Users API table for that user

3. When we build the drop down in the new login system to allow them to select a school, we would need to post to the Business API the guids of the schools that are joined to the user, the response then we use for a drop down to allow them to select the school.

1. Example POST of school_uuids
   POST: /api/schools/query
   {
   “id”: [
   “8765edc6-b480-41af-9c96-c6a0ffd8e1ee”,
   “98a67538-6bc8-4278-834c-5a4c794c475a”,
   “5b58f804-17f0-4ec4-812e-00a00bd038f3”
   ]
   }

4. The alternative is that we have the Users to Schools table in the Business API. In that case we simply need to get the list of schools by user - however that probably inverts the responsibilities of the service (where now the Business API is responsible for storing user authorization data).

5. As for the modification of a user we have two options

1. Add support for API calls on the User edit pages in the DNN module. If any user details are changed, then post those changes over to the Users API to update (password, roles, personal information)

2. Develop a basic User Management tool in the Pay Management Web App. If a user is migrated, then the new tool would need to be used. We would be able iframe the new tool in the same way we do other Pay Services tools.

 

---------------------------

@page

@model IndexModel

@{

    Layout = "_Layout";

}

    <script src="~/lib/jquery/dist/jquery.min.js"></script>

<script>

 

function SubmitFilter()

{

    var transactionNumb = $("#transactionNumber").val();

    var cardHolderName = $("#cardHolder").val();

    $.ajax({

    type: "GET",

    url: "https://localhost:7197/Transactions?transaction_number="+transactionNumb+"&cardholder="+cardHolderName,

   

    contentType: "application/json; charset=utf-8",

    dataType: "html",

    success: function (data)

    {

      alert(data);

    }

    });

}

</script>

--------------------------------------------------------------------

namespace PayManagementWebApp.Areas.Transactions.Pages;

[Authorize]

public class IndexModel : PageModel

{

    private readonly ILogger<IndexModel> _logger;

   

    public string Title { get; private set; }

   

    public int CurrentPage { get; set; } = 1;

    public int Count { get; set; }

    public int PageSize { get; set; } = 25;

    public int TotalPages => (int)Math.Ceiling(decimal.Divide(Count, PageSize));

    public bool EnablePrevious => CurrentPage > 1;

    // public bool EnableNext => CurrentPage < (int)TotalResults;

    public dynamic TotalResults;

    public JArray Transactions { get; set; }

    public string BaseApiUrl;

    public string Authorize;

    public IndexModel(ILogger<IndexModel> logger, IConfiguration configuration)

    {

        _logger = logger;

        Title = "Transactions";

        BaseApiUrl = configuration.GetSection("AppSettings")["PayServicesApiBase"];

    }

    public void OnGet(int CurrentPage,int transaction_number, string cardholder)

    {

            this.Authorize = HttpContext.Session.GetString("Roles");

            this.CurrentPage = CurrentPage;

            if(CurrentPage==0)

            {

               this.CurrentPage = 1;        

            }

            ViewData["Title"] = "Transactions List";

         

            Transactions =  GetTransactions(this.CurrentPage,transaction_number,cardholder);  

           

    }

    public JArray GetTransactions(int currentPage,int transaction_number , string cardholder)

    {

        using (var client = new HttpClient())

        {

            client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("bearer", HttpContext.Session.GetString("JwtToken"));            

            var url = $"{BaseApiUrl}/transactions?page={currentPage}&limit={PageSize}";    

            var filters ="";

            if(transaction_number!=0)

            {

            url += $"&filter_by=transaction_number[contains]:{transaction_number}";            

            }

            if(cardholder!="" && cardholder!=null)

            {

                url += $",card_holder_name[contains]:{cardholder}";            

            }

            var requestUri = new Uri(url);

            var responseTask = client.GetAsync(requestUri);

            responseTask.Wait();

            var result = responseTask.Result;

           

            // this.TotalResults = result.Headers.GetValues("X-Paging-Pages");

            this.TotalResults = "5";

            if (result.IsSuccessStatusCode)

            {

                var reportResults = Task.Run(async() => await result.Content.ReadAsAsync<JArray>()).Result;                  

                return reportResults;

            }

        }

        return JArray.Parse("[]");

    }

}