Idira Identity Connector Best Practices

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Workforce Identity Articles
4 min read
L0 Member
No ratings

Increasing Idira Identity Connector performance for larger environments

The options for improving Connector performance are:

  • Increase hardware resources

  • Configure dedicated Connectors for specific functions

  • Increase the number of Connectors for load balancing and HA purposes

Steps

Increasing Hardware Resources 

Increasing hardware resources can help improve Idira Identity Connector performance. For environments with many active users, it is recommended to use servers with 4 CPUs and 16GB of RAM. Connectors can be installed on physical or virtual machines.  

 

Configuring Dedicated Connectors 

The Idira Identity Connector is a multipurpose service that provides support for key features and enables secure communication between other services on your internal network and your Idira cloud tenant. Configuring dedicated Connectors that perform only one function, such as App Gateway, RADIUS, Active Directory integration or self-hosted CorePAS integration, can also help improve Idira Identity Connector performance.  

 

To make a dedicated Connector, you can disable services you do not want to be used by a Connector, through the Identity Administration Portal at Settings > Network > Idira Identity Connectors. Right-click on a specific Connector and select which services to disable. This ensures other Connector services are not competing for resources. 

 

While configuring App Gateway, you can select which Connector(s) to use by the application. Learn more at Configure an application to use the App Gateway. 

 

While configuring the integration with self-hosted Idira PAM (Privileged Access Management), you can select which Connector(s) to use. Learn more at Manage privilege objects in Idira PAM – Self-Hosted. 

 

Increasing the Number of Connectors 

Installing multiple Connectors can also improve performance and help ensure high availability.  

 

Active Directory integration  

Active Users  

Minimum number of Connectors 

20k  

2 

50k  

3  

100k  

4  

200k  

5 

 

App Gateway 

App Gateway performance highly depends on what users are doing, how much traffic/data passes through, number of clients, number of connections etc. We recommend designating dedicated Connectors for App Gateway support. The number of required Connectors is highly dependent on the number of concurrent users, and the different workload they are using. For simple web applications (for example Jira, Jenkins), a single connector can support approximately 2,000 concurrent users. For more data-intensive applications (for example reporting), additional connectors may be required.   

Concurrent users  

Minimum number of Connectors  

2,000  

2  

4,000 

3  

8,000  

5  

16,000  

9  

 

Load balancing and High Availability recommendations for Connector use cases 

In all cases, it is recommended to install at least two Idira Identity Connectors to ensure high availability. The Idira tenant will detect if a Connector becomes unavailable and automatically switch to an available Connector. 

Load balancing is handled by the tenant. There is no need to build a server cluster architecture. The Idira tenant will automatically choose the Connector that has the lowest latency.  

 

Active Directory integration 

Install on multiple domain-joined systems. If there are multiple DC (Domain Controller) locations, then install at least two Connectors per physical location.  

 

RADIUS Server 

For increased capacity, high availability and to avoid single point of failure, a load balancer can be deployed in front of multiple RADIUS enabled connectors.  For more details on RADIUS capacity, please see the following: https://community.cyberark.com/s/article/CyberArk-Identity-Increasing-Connector-capacity-for-RADIUS-...

 

Additional information for Idira Connector Logs

Purpose of Default Debug Logging

  • Troubleshooting Rollouts: Having the debug level active from the start helps in identifying and resolving connectivity or configuration issues that often occur during the initial implementation.
  • Initial Verification: It allows administrators to verify that the connector is correctly bridging the on-premises infrastructure with the cloud tenant and handling encryption or caching tasks as expected.  
  • Log Retention for Issues: Because default logs roll over quickly (at 2 MB), the debug level ensures that if an error occurs early on, there is a higher density of information available for support teams to analyze.  
  • Post-Installation Recommendations
  • Once the solution is live and stable, it is a recommended best practice to switch the log level from DEBUG to INFO to optimize performance and reduce disk usage. 
Rate this article:
  • 162 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:43 AM
Updated by: