I believe you can define a single policy and bandwidth for all applications, but utilize a specified source and destination to circumvent the IAM rather than using the passthrough option.

Enabling passthrough for RDP may result in policies and bandwidth being ignored because the IAM system is not able to inspect or apply its policies to the RDP traffic. This can happen when passthrough mode allows traffic to bypass IAM's policy enforcement mechanisms. Here's what you can do to address this issue

If Remote Desktop Protocol (RDP) was working properly before the integration of IAM and is now experiencing issues, it is possible that IAM is blocking the RDP traffic.

Did you try to bypass the source and destination?

1) The integration of IAM (Identity and Access Management) into the network could be the cause of the Remote Desktop Protocol (RDP) application not working properly. IAM is designed to manage user access and enforce security policies, which can sometimes conflict with the requirements of RDP. Here are a few potential causes and solutions for this issue:
IAM Access Control Policies: IAM may have implemented access control policies that restrict or block RDP traffic. Check the IAM configuration to ensure that the necessary ports (usually TCP port 3389 for RDP) are allowed for RDP traffic. Adjust the IAM policies accordingly to allow RDP connections.

IAM Authentication and Authorization: IAM may be enforcing authentication and authorization mechanisms that require additional steps or permissions for RDP access. Review the IAM authentication and authorization settings to ensure that RDP users are properly authenticated and authorized to use the application. This may involve configuring IAM rules, user groups, or access permissions specific to RDP.

Firewall and Network Configuration: Verify that the network firewall and other security devices are properly configured to allow RDP traffic. Sometimes, the integration of IAM may have inadvertently changed firewall rules or network settings that are affecting RDP connectivity. Consult with your network administrator to ensure that the necessary network configurations are in place for RDP.

IAM Integration Settings: If IAM has been integrated with other systems or applications, there could be specific integration settings or configurations that are impacting RDP functionality. Review the IAM integration settings and documentation to ensure that RDP is properly supported and configured within the IAM ecosystem. You may need to adjust IAM integration settings or consult with IAM vendors for guidance on RDP integration.

2) Enabling passthrough for RDP may result in policies and bandwidth being ignored because the IAM system is not able to inspect or apply its policies to the RDP traffic. This can happen when passthrough mode allows traffic to bypass IAM's policy enforcement mechanisms. Here's what you can do to address this issue:
Policy Adjustments: Review the IAM policies related to traffic management and bandwidth control. Ensure that the policies explicitly address RDP traffic and define the appropriate rules and restrictions. If passthrough mode is causing policies to be ignored, you may need to modify IAM policies to account for RDP traffic explicitly.

Traffic Shaping: Instead of relying solely on IAM policies, consider implementing traffic shaping or Quality of Service (QoS) mechanisms at the network level. These mechanisms can prioritize RDP traffic and allocate the desired bandwidth, even if passthrough mode is enabled. Work with your network administrator to configure traffic shaping rules that prioritize RDP traffic accordingly.

IAM Configuration: Review the IAM configuration settings related to traffic management and passthrough mode. Ensure that the passthrough mode is configured correctly and that it aligns with your desired policy enforcement requirements. Adjust the IAM configuration if necessary to ensure that policies and bandwidth control are not bypassed when passthrough mode is enabled.

Integrating IAM (Identity and Access Management) into a network can affect Remote Desktop Protocol (RDP) in several ways, depending on how the IAM system was configured and implemented. Some possible causes of the RDP issues after integrating IAM into the network include:

IAM access controls: The IAM system may have implemented new access controls or policies that restrict or block access to RDP. For example, if the IAM system is enforcing a policy that requires multi-factor authentication (MFA) for RDP access, users who were previously able to access RDP with just a password may no longer be able to do so.

Changes to user accounts: When IAM is integrated into a network, it may change the way user accounts are managed, such as adding or removing accounts, or changing user permissions. If the RDP application is not updated to reflect these changes, it may result in access issues.

Network configuration changes: Integrating IAM may require changes to network configuration, such as implementing new firewalls or routing rules. These changes can affect RDP connectivity and cause issues.

Integration issues: If the IAM system was not properly integrated into the network or if there are compatibility issues with the RDP application, it may result in connectivity issues or other problems.

To troubleshoot this issue, you may need to check the IAM system's access policies, review any changes to user accounts, and verify that network configuration changes have not impacted RDP connectivity. Additionally, you may need to check for any compatibility issues between the RDP application and the IAM system. You may need to involve your IT team or IAM vendor support to help diagnose and resolve the issue.

i think you can create 1 policy and bandwidth on top with all application but use the specific source and destination to bypass the IAM rather enable the passthrough feature.

Hi,

1. After correct installation, you can configure and debug the system. 1.1 Environment Requirement.
2. Policy will work if it is configured correctly when traffic passes through NGAF. Since if it is a local network,

Thanks