You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Filter Fiddler Traffic Using Domain Names and Client Processes
3
+
description: Introduces how to filter traffic that's captured by Fiddler using domain/host names owned by Microsoft Entra and client processes.
4
+
ms.service: entra-id
5
+
ms.topic: how-to
6
+
ms.date: 04/08/2025
7
+
ms.reviewer: bachoang, v-weizhu
8
+
ms.custom: sap:Enterprise Applications
9
+
---
10
+
# Filter Fiddler traffic using domain names and client processes
11
+
12
+
This article explains how to filter traffic that's captured by Fiddler using domain/host names owned by Microsoft Entra and client processes.
13
+
14
+
## Prerequisites
15
+
16
+
Before filtering, ensure that Fiddler is configured to capture traffic for all processes. In the lower-left corner of the Fiddler window, you can select **All processes** to change the selection.
17
+
18
+
:::image type="content" source="media/filter-fiddler-traffic-using-domain-name-client-process/all-processes.png" alt-text="Screenshot that shows the 'All processes' button.":::
19
+
20
+
## Filter traffic using Fiddler's built-in filter feature
21
+
22
+
To filter traffic using Fiddler's built-in filter feature, follow these steps:
23
+
24
+
1. Open Fiddler and navigate to the right panel.
25
+
2. Select the **Filters** tab, and then select the **Use Filters** checkbox.
26
+
3. Under the **Hosts** section, select **Show only the following Hosts**.
27
+
4. In the text box, enter the host name list you want to filter on, separated by semicolons, for example, `localhost;login.microsoftonline.com;graph.microsoft.com`.
28
+
29
+
> [!NOTE]
30
+
> This text box will display a yellow background while editing the list, indicating unsaved changes.
31
+
5. Select the **Actions** button to save the list. The background color will change to white, confirming the list is saved.
32
+
33
+
:::image type="content" source="media/filter-fiddler-traffic-using-domain-name-client-process/show-only-the-following-hosts.png" alt-text="Screenshot that shows how to filter traffic based on host names.":::
34
+
35
+
Under the **Client Process** section, you can also select a specific process to filter on. This is particularly useful for filtering a standalone application. It might be less effective for capturing browser traffic because multiple processes with the same name can make it difficult to identify the correct one.
36
+
37
+
## Filter traffic using JavaScript code in the OnBeforeRequest function
38
+
39
+
> [!NOTE]
40
+
> This option is used especially for browser-based applications.
41
+
42
+
1. In Fiddler, go to **Rules** > **Customize Rules**. This action will open the **CustomRules.js** file in the FiddlerScript editor.
43
+
2. Locate the **OnBeforeRequest** function in the FiddlerScript editor.
44
+
3. Insert the following JavaScript code at the beginning of the function:
45
+
46
+
```javascript
47
+
// begin filter
48
+
49
+
// set this to false to disable filter and true to enable filter
50
+
var filterOn =true;
51
+
52
+
if (filterOn)
53
+
{
54
+
// hide all requests by default
55
+
oSession["ui-hide"] ="true";
56
+
57
+
// list of domain names to filter on
58
+
var host = ["localhost", "login.microsoftonline.com", "graph.microsoft.com"];
59
+
60
+
// list of processes to filter on
61
+
var processlist = ["chrome", "microsoftedgecp", "iisexpress", "powershell"];
62
+
63
+
for (var j =0; j <processlist.length; j++)
64
+
{
65
+
if (oSession.LocalProcess.Contains(processlist[j]))
66
+
{
67
+
for (var i =0; i <host.length; i++)
68
+
{
69
+
if (oSession.HostnameIs(host[i]))
70
+
{
71
+
oSession["ui-hide"] =null;
72
+
}
73
+
}
74
+
}
75
+
}
76
+
}
77
+
78
+
// end filter
79
+
```
80
+
81
+
:::image type="content" source="media/filter-fiddler-traffic-using-domain-name-client-process/add-javascript-code-onbeforerequest-function.png" alt-text="Screenshot that shows the JavaScript code added in the OnBeforeRequest function." lightbox="media/filter-fiddler-traffic-using-domain-name-client-process/add-javascript-code-onbeforerequest-function.png":::
82
+
83
+
Here are the explanations of some variables in the JavaScript code:
84
+
85
+
-`filterOn`:Set it to `true` to enable the filter and `false` to disable it.
86
+
-`host`: Contains the list of domain names to filter on.
87
+
-`processlist`: Contains the list ofprocess names to filter on.
88
+
89
+
4. Save the changes to the **CustomRules.js** file.
90
+
91
+
## References
92
+
93
+
- [Modifying a Request or Response](http://docs.telerik.com/fiddler/KnowledgeBase/FiddlerScript/ModifyRequestOrResponse)
Copy file name to clipboardExpand all lines: support/power-platform/power-automate/dataverse-cds/cds-user-cannot-access-power-automate-business-process-flows-on-demand-workflows.md
# Invalid credentials error when running desktop flows in Power Automate for desktop
9
9
@@ -52,6 +52,8 @@ To see an error message with specific details on what went wrong, ensure you hav
52
52
|-1073741062|Smart card logon is required and was not used||Connections to machines that require smart card logons aren't supported. Use a machine without this requirement.|
53
53
|-1073741715|Bad username or authentication information| The given credentials aren't correct. This issue might occur due to an incorrect user/password combination or username format.|1. Double-check that your username and password work on the machine. You can do this by signing out and signing back in with the same credentials. </br>2. If that works, verify you're using the correct username format by running the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command in the context of the desktop flow connection account. Check the `Executing Account Name` value (in the `Diagnostic Data` section) in the output and make sure it matches the username that was used. </br>3. If your machine is [Microsoft Entra joined](/entra/identity/devices/concept-directory-join) or hybrid, use the `[email protected]` format. If your machine is domain-only joined, use the `DOMAIN\user` format. </br></br>To determine the correct username format, check your machine's join state:</br> a. Run the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command. </br>b. Look for the `Device State` section in the output: </br>- If you see `AzureAdJoined : YES`, your machine is Microsoft Entra joined. </br>- If it says `NO` after `AzureAdJoined` but `YES` after `DomainJoined`, your machine is domain-only joined. |
54
54
|-1073741730|The domain isn't available|| Make sure you're using the correct username format for your machine join state. If your machine is [Microsoft Entra joined](/entra/identity/devices/concept-directory-join) or hybrid, use the `[email protected]` format. If your machine is domain-only joined, use the `DOMAIN\user` format. </br></br>To determine the correct username format, check your machine's join state: </br>1. Run the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command. </br>2. Look for the `Device State` section in the output: </br>- If you see `AzureAdJoined : YES`, your machine is Microsoft Entra joined. </br>- If it says `NO` after `AzureAdJoined` but `YES` after `DomainJoined`, your machine is domain-only joined. |
55
+
|-1073741714|User account restriction has prevented successful authentication | The referenced username and authentication information are valid, but a user account restriction, such as time-of-day restrictions, has prevented successful authentications.| Confirm that no security or account restriction policies prevent this user from successfully signing in.|
56
+
|-1073741712|The user account is restricted such that it may not be used to log on from the source workstation || Confirm that no security or account restriction policies prevent this user from successfully signing in.|
55
57
56
58
If you don't have a more specific error associated with the problem, the easiest way to troubleshoot is to sign in to the machine with the exact credentials you entered in your connection. You can try this method by signing in to the machine locally or through a Remote Desktop connection. You should receive the same error message that Power Automate receives when trying to authenticate your credentials, which should help you troubleshoot the issue.
0 commit comments