Could not list files in the okw container...but our authentication needs to be redone...

[RobertLRead]

After writing some debugging code in the backend, it is clear that we have a configuration problem in our blob containers. We can list the file in the "okh" blob container, but not the "okw". We even created an "okz" to test this. I worked on this for 3 hours; I can find no configuration difference.

I suspect that this is realiity to the complexity of our security/authentication model, which requires us to login with the azure cli. I suggest that we shift to a key-based athentication that is used by the GOSQAS team, which has had no problem with this.

@Jbutler-helpful wanted me to assign this the @devhawk ; but generally I think we should just completely redo our authentication system. I would love to have someone do this, but I think @devhawk is the only logical sorce, except for me. I'm assigning to @Jbutler-helpful for now.

 console.log("list Summaries", serviceName, containerName);

    {
        const { error, errorMessage, data } = await listFilesInContainer(
            serviceName,
            "okz"
        );
        console.log("Returning OKH Summaries",data);
        if (error) {
            return { jsonBody: error };
        }
        console.log("dataReturned", data);
    }
    console.log("ZZZ About to call listFilesInContainer ");

    const { error, errorMessage, data } = await listFilesInContainer(
        serviceName,
        "okh"
    );
    console.log("ZZZZZZZZZZZZZZZ",error);