JMX Auth UX

[andrewazores]

Fixes #117

Based on top of #110

[andrewazores]

To test: use a recent (now relies on changes in cryostatio/cryostat-legacy#242) ContainerJFR backend and run it like CONTAINER_JFR_RJMX_USER=someuser CONTAINER_JFR_RJMX_PASS=somepass CONTAINER_JFR_CORS_ORIGIN=http://localhost:9000 sh run.sh. Run a local development server for this -web branch with npm run start:dev and open http://localhost:9000 in your browser. Select ContainerJFR itself as a target and go to the Recordings or Events views. A modal dialog should appear, requiring you to enter your JMX credentials before the recordings/events can be loaded.

[ebaron]

Works fine for me. I'm a bit confused about how the delete button is supposed to work. Is it to delete saved credentials for the target? If so, will the user have an opportunity to do this once they've been saved?

[andrewazores]

Yea, I think we will probably want to have some kind of UX for managing credentials, but I don't really know how to go about it. Right now the Delete button is only potentially useful if you first enter some invalid credentials and are re-prompted for credentials, and then decide you don't want the web-client to store those credentials after all. Pretty narrow and meaningless use-case currently. Once you've entered valid credentials for a target then there is no way to delete those credentials - although they only persist so long as the browser tab/window is open anyway, and are cleared as soon as you close/reopen or refresh the page.

I could just remove the Delete button for now since it doesn't really provide any meaningful functionality.

[ebaron]

I'm fine with leaving it and changing it later. Up to you