Connect Chrome DevTools to ECA
Give ECA governed access to Chrome DevTools’s 26 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Chrome DevTools to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Chrome DevTools in Runlayer
Add Chrome DevTools from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Install the Runlayer CLI so ECA can reach Chrome DevTools, which runs on the user’s machine.
ECA setup guide - 3
Sign in to Chrome DevTools
Sign in the way Chrome DevTools requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Chrome DevTools from ECA
Chrome DevTools’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
26 Chrome DevTools tools in ECA
Runlayer policy decides which of these ECA users can call. 10 read data only.
Click
Clicks on the provided element
Close page
Closes the page by its index.
Drag
Drag an element onto another element
Emulate
Emulates various features on the selected page.
Evaluate script
Evaluate a JavaScript function inside the currently selected page.
Fill
Type text into a input, text area or select an option from a element.
Fill form
Fill out multiple form elements at once
Get console message
Gets a console message by its ID.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Chrome DevTools call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more