The size of the sync button was changed to match the refresh button of access requests (https://github.com/gravitational/webapps.e/pull/396#discussion_r982842537). The change was reverted in #1269.
Instead of making the sync button to be of custom height, I think we should just change the size of the search input.
It also has the added bonus of making the sync and refresh button be on a matching height on both tabs, so they don't shift when switching between access requests and cluster resources.
* Add comment to resolveNetworkAddress
* Log errors during boot of React app
* Connect: Accommodate for making gRPC server creds in shared process
* Adjust timeout for resolveNetworkAddress
Some of the timeouts in preload.ts, the shared process and tshd are set
to 10s. If the timeout to resolve the network address is lower or equal
to that, those timeout won't have the chance kick in.
Hence setting the timeout to a slightly larger value.
* makeCert: Add subjectAltName to certs
Without this, the cert generated by makeCert was failing when loaded
in Go as the gRPC server cert. The error message was:
x509: certificate relies on legacy Common Name field, use SANs instead
See:
* https://stackoverflow.com/a/31143907/742872
* Search for "subjectAltName" https://github.com/digitalbazaar/forge/blob/2bb97afb5058285ef09bcf1d04d6bd6b87cffd58/README.md
* Fix lint issues
* Reword comment
Co-authored-by: Michael <michael.myers@goteleport.com>
* Remove unused imports
Co-authored-by: Michael <michael.myers@goteleport.com>
* Now that clipboard.readText() requires transient user activation
(see https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/readText#security),
our system of syncing the local clipboard to remote onfocus and onmouseenter
no longer works, since those events don't necessarily imply a transient event.
With this change, we instead sendLocalClipboardToRemote onMouseDown and onKeyDown,
which should guarantee that the sync is always within a transient event.
Because the user must preform at least one of these actions in order to
initiate a paste, the clipboard should appear to always be in sync from
their perspective.
* eliminates the entire useClipboard hook and its surrounding state, which
was a big rube goldberg machine ensuring that
1. If a user had clipboard sharing enabled by RBAC
2. they were on chrome and
3. they had clipboard permissions allowed
If 1 was true, but either of 2 or 3 wasn’t, we blocked the UI and forced
them to correct it. That was also the mechanism that caused the clipboard
permissions dialog to pop up at the beginning of the session if clipboard
access wasn’t "granted".
Now the UX is much simpler: if a user has clipboard sharing allowed by RBAC,
and they’re on Chrome, clipboard sharing is enabled. If either of those is false,
clipboard sharing is disabled. If a user’s clipboard permissions are in
"prompt" state (aka neither "granted" nor "denied"), the first time they
try to copy/cut something on the remote, or have something in their clipboard
locally and click a mouse button or press a key, the browser prompt asking
for clipboard permissions will show up.
* Refactor CatchError component
- add retry and providing custom fallback funcs
* Make existing discover work resusable elsewhere
- Pull out reusable files to Share/*
- Add custom timeout messages and margin top styles for Timeout
- Allow fetching/pinging for services based on type of service for PingTeleportContext
- JoinTokenContext
- allow fetching for tokens based on type of service
- fix a bug that uses cached token, when coming back to the flow
* Remove deprecated use of exec for copying to clipboard
* Rename existing Tabs to TabIcon
* Add and use @react/user-event library for testing clipboard
* Add events for create, update and delete `kube_clusters`
Add support for `kube_cluster` audit events:
- `kube.create`
- `kube.update`
- `kube.delete`
From gravitational/teleport#16276
* Don't show prompt when clicking to go to discover when already there
* Remove sidenav titles for unfinished flows
* Copy change and show example rules and logins as YAML editor
* Update diagnostic json field values
* Fix bugs
- React bug about requiring unique keys (TestConnection traces)
- Regression bug in LoginTrait where if you have a login name "root"
it does not render the checkbox. Solved by making the "id" more
unique by appending the index number to login names.
* Apply backend field name change for updating user traits with renewing
session
* Gracefully handle network error which allows user to refetch failure points
* Update styling to match figma (though button stays top of traces
to avoid moving of button when re-testing)
Grzegorz Zdunek