OIDC Auth Bug

[zofskeez]

Resolves #12436

When using the MetaMask chrome extension it was reported that the OIDC auth login workflow was not working. After investigating the source code it was discovered that the javascript being injected calls window.postMessage which was being handled inadvertently by the auth-jwt component.

To guard against unintended messages from the same origin a source property was added to the message data which is then verified in the event handler. Unit tests were added to verify the functionality.

[zofskeez]

@chelshaw I spent some time debugging these oidc acceptance test failures and wanted to bring them to your attention since you were working on them recently. I threw a pause in and found that a network request was failing with Invalid client ID.

After logging out the clientId return value from the setupOidc method I noticed that it was set to the following on failing runs: Success! Data written to: identity/oidc/client/my-webapp-1636753641317. There are 2 commands that are run to generate the clientId and it appears that the lastLogOutput value is the output from the first command:

await consoleComponent.runCommands([
  `write identity/oidc/client/${webappName} redirect_uris="${redirect}" assignments="my-assignment" key="sigkey" id_token_ttl="30m" access_token_ttl="1h"`,
  `read -field=client_id identity/oidc/client/${webappName}`,
]);

It seems that there is a race condition in the runCommands method where responses are not output in the same order that they are run consistently. Waiting for a settled state before continuing the loop to run the console commands seems to have fixed it in this commit. Since this change will impact all usages of the helper I'm hoping that it doesn't break any other tests but I don't think it should 🤞.

[hashishaw]

Great work, thanks for working on this!