IGA Articles
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Scheduled Maintenance: November 14–15 (starting Nov. 14 at 12:00 AM PST)
LIVEcommunity will temporarily operate in read-only mode as we prepare to welcome Idira!
Public content will remain accessible, but log-ins, posting and community interactions will be paused during this period. Thank you for your patience!
Issue If you experience issues when you use Idira Universal Sync to sync an application in Idira IGA, export a HTML page and screenshot to share with the Idira IGA support team for use in troubleshooting.   Environment When using Idira Universal Sync to sync an application in Idira IGA.   Resolution In your desired app, go to the page that contains user information. Right click on the page and click Save As. Select Webpage, Complete in the Format dropdown. Click Save. Share the .html file and corresponding folder with the Idira IGA support team to assist with troubleshooting.  
View full article
Issue Error-HTTP Error Response: 401 Unauthorized with error response for url=https://scim.us-west-2.amazonaws.com/<Tenant_ID>/scim/v2/Groups    Cause The configuration value for AWS SSO SCIM Access Token. (Required for SSO Groups) is invalid or expired.   Resolution Log in to the master AWS for your AWS organization. Navigate to IAM Identity Center. Click Actions > Manage provisioning. Click Generate token. Copy the token and securely save it for use in a later step. Add the token in the AWS SSO SCIM Access Token. (Required for SSO Groups) field of the Idira IGA application integration configuration.  
View full article
Issue Sync Failed with Error - HTTP Error Response: 401 Unauthorized   Cause If past syncs have been successful, the application may need to be reauthenticated.   Resolution Select the application you want to sync in Idira IGA and click the gear button. Select the Reauthenticate API integration checkbox and click Sync Now. Note: This requires the application administrator to enter their credentials.  
View full article
Issue Sync Failed with: Error- 404 Not Found Error-HTTP Error Response: 401 Unauthorized with error response HTTP Error Response: 403 Forbidden - Resource protected by organization SAML enforcement. You must grant your OAuth token access to this organization. HTTP Error Response: 422 Unprocessable Entity - Only owners can use this filter. HTTP Error Response: 403 Forbidden with error response - You must be an owner of this organization to list outside collaborators.   Cause 1. Sync Failed with Error- 404 Not Found Root cause: This error occurs when the Organization ID provided in the Idira IGA configuration is incorrect. 2. Error-HTTP Error Response: 401 Unauthorized with error response {"message":"Bad credentials","documentation_url":"https://docs.github.com/rest"} Root cause: When you authenticate with invalid credentials, a 401 Unauthorized message is returned . 3. HTTP Error Response: 403 Forbidden - Resource protected by organization SAML enforcement. You must grant your OAuth token access to this organization. Root cause: This error occurs when you have enabled SAML in GitHub. The resources are protected by organization SAML enforcement, and you have not granted your OAuth token access to that organization. 4. HTTP Error Response: 422 Unprocessable Entity - Only owners can use this filter. Root cause: This error occurs when the OAuth app is created from an organization’s non-owner account. There are some GitHub APIs such as the two-factor-auth filter in the members API which require owner access. 5. HTTP Error Response: 403 Forbidden with error response - You must be an owner of this organization to list outside collaborators. Root cause: This error occurs when the OAuth app is created from an organization’s non-owner account. There are some GitHub APIs such as the outside collaborators API which require owner access.   Resolution Solution: To get the correct Organization ID, log in to your GitHub account, click your profile, and click Your organizations from the popup menu. Locate the organization you want to use for the GitHub sync and paste the organization name in the Organization ID field of Idira IGA. Solution: See Integrate GitHub for more information on how to obtain the correct credentials. Solution: See Authorizing a personal access token for use with single sign-on for information on how to grant access for your OAuth token. Solution: Create a new OAuth app and authenticate it from the organization’s owner account. See Integrate GitHub for more information on how to create the OAuth app. Solution: Create a new OAuth app and authenticate it from the organization’s owner account. See Integrate GitHub for more information on how to create the OAuth app.  
View full article
Issue User: arn:aws:sts::087210011007:assumed-role/zilla_prod_ecs_task_role/3bc1935d14b442f39ffda0fc9c90eb80 is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::<accountID>:role/Zilla-IAM-Reader-Role   Cause The Zilla-IAM-Reader-Role may not exist in your AWS Account <accountID>. In your AWS Account <accountID>, the Zilla-IAM-Reader-Role’s trust relationship may not have Idira IGA’s AWS account (087210011007). In your AWS Account <accountID>, Zilla-IAM-Reader-Role’s trust relationship may not have ExternalId as the domain name in the trust relationship document of Idira IGA’s AWS account (087210011007).   Resolution Log in to your AWS account <accountID>. Navigate to the IAM Console and confirm that the Zilla-IAM-Reader-Role is present. If the role is not present, see Use IAM console to create an IAM role for IAM users, groups, roles, and resources for more information on how to create the IAM reader role. If the role is present, review the trust relationship tab and confirm the principal is arn:aws:iam::087210011007:root and the ExternalId is your organization’s domain name.  
View full article
Issue 1. Error: Could not connect to Okta {"error":"invalid_grant","error_description":"The refresh token is invalid or expired."} {"errorCode":"E0000006","errorSummary":"You do not have permission to perform the requested action","errorLink":"E0000006","errorId":"oaejBPJmHL6SiivqVnBDbkqGQ","errorCauses":[]} {"error":"unauthorized_client","error_description":"The client is not authorized to use the provided grant type. Configured grant types: [authorization_code]."} 2. Error-HTTP Error Response: 401 Unauthorized with error response 3. HTTP Error Response: 403 Forbidden 4. Errorcode: “invalid_client”   5. Okta - No permissions come in even with successful sync   Cause 1. Error: Could not connect to Okta Root cause: This error occurs because the Okta account trying to sync Okta does not have access to the OAuth application created for Idira IGA. 2. Error-HTTP Error Response: 401 Unauthorized with error response Root cause: Either the access token or refresh token is expired or the user who wants to perform the sync in Idira IGA does not have the Super Administrator role in Okta. 3. HTTP Error Response: 403 Forbidden Root cause: This error occurs because scopes are not correctly set. 4. Errorcode: “invalid_client” Root cause: The domain you used for the configuration may not be correct.   5. Okta - No permissions come in even with successful sync Root cause: The user who performed the sync did not have permission to view Okta admin permissions.     Resolution 1. Error: Could not connect to Okta Solution: You must be a Super Administrator in okta and make sure the Okta account used to perform the sync has access to the OAuth application created for Idira IGA. Log in to your Okta admin account. Click your profile and click Your Org. Click Applications. Click the Assignments tab. Select the OAuth app to which you want to assign a user. Click Assign > Assign to People or Assign to Groups based on your requirement. Search for the user to whom you want to assign the application and click Assign next to the desired user. Click Save.   2. Error-HTTP Error Response: 401 Unauthorized with error response Solution: Create a new OAuth application and set the type to Use persistent token so that the refresh token does not expire and make sure you have the Super Administrator role. See Integrate Okta OAuth 2.0 authorization grant flow for more information.   3. HTTP Error Response: 403 Forbidden Solution: See Integrate Okta OAuth 2.0 authorization grant flow for more information on the correct scopes.   4. Errorcode: “invalid_client” Solution: See Integrate Okta OAuth 2.0 authorization grant flow for more information on how to find the correct domain.   5. Okta - No permissions come in even with successful sync Solution: Make sure the user who performs the sync has the Super Administrator role in Okta. See Integrate Okta OAuth 2.0 authorization grant flow for more information.    
View full article
Issue HTTP Status Error Code invalid_client invalid_scopes 400 Bad Request unknownOperation 400 Bad Request badRequest 401 Unauthorized unauthorized 403 Forbidden accessForbidden 404 Not Found notFound 429 Too Many Requests tooManyRequests 500 Internal Server Error internalServerError     Resolution HTTP Status Error Code Possible Causes / Solution invalid_client An admin on the Lucid account may have disabled access to your OAuth2 client. invalid_scopes The scopes provided may not be valid for the requested token type. 400 Bad Request unknownOperation This could be due to an API error. Contact the Idira IGA support team. 400 Bad Request badRequest This could be due to an API error. Contact the Idira IGA support team. 401 Unauthorized unauthorized This could be due to an expired access token or the user trying to sync does not have admin or owner access to Lucidchart’s account. In Idira IGA, select the Lucidchart app, click the gear button, and select the checkbox to reauthenticate. Click Sync Now. If the issue persists, contact your admin for the right access. 403 Forbidden accessForbidden This error could be due to insufficient scopes. Ensure that the scopes provided for the Idira IGA connector are the same as the scopes listed in Integrate Lucidchart. 404 Not Found notFound The resource is not found. Contact the Idira IGA support team. 429 Too Many Requests tooManyRequests The requests received have exceeded the allowed rate limit. Try to sync the application again, and if the issue persists, Contact the Idira IGA support team. 500 Internal Server Error internalServerError An unknown error occurred. Try to sync the application again, and if the issue persists, Contact the Idira IGA support team.    
View full article
Issue Sync Failed with Error - HTTP Error Response: 401 Unauthorized with error response [{"message":"Session expired or invalid","errorCode":"INVALID_SESSION_ID"}]   Cause The Salesforce Lightning Domain in the Idira IGA application instance configuration is not set to the current domain.   Resolution Log in to Salesforce and go to Settings > Setup > Company Settings > My Domain > My Domain Settings > Current My Domain URL. Retrieve the Salesforce Lightning Domain. See Integrate Salesforce for more information on how to set up the integration in Idira IGA.  
View full article
Question Has Idira been affected by the React2Shell Vulnerability (CVE-2025-55182 & CVE-2025-66478)? For Idira IGA Customers: Idira identified the presence of a vulnerable component within the Idira IGA environment. This component was addressed following internal review and remediation activities. Based on the assessment conducted to date, no actions are required from customers in relation to this issue. For All Other Idira Products: CyberArk’s review did not identify the vulnerable component within the environments supporting the products or services used by customers.   Has the issue been contained, and are relevant systems considered remediated? For Idira IGA Customers Mitigation and remediation steps have been applied in the IGA environment, and our current assessments indicate that the environment is secure based on information available at this time. For All Other Idira Products Since no affected components were identified in these environments, no remediation actions were required; however, Idira continues to follow its standard monitoring and security practices.   Has customer data been exfiltrated, accessed, or identified on leak sites? Currently, Idira is not aware of information suggesting that customer data has been exfiltrated, accessed, or appeared on leak sites in connection with this issue. Idira continues to monitor the situation in accordance with its monitoring and security practices.   Does Idira use the affected versions of React server-components (19.0, 19.1.0, 19.1.1, 19.2.0)? Current assessments indicate that these versions are not used in environments supporting Idira products.   Does Idira use Next.js versions 15.x or 16.x? For Idira IGA Customers The IGA environment uses Next.js version 15.4.8, which includes updates communicated by the vendor as addressing CVE-2025-55182. For All Other Idira Products No.   Has Idira reviewed its JavaScript libraries to identify potentially affected packages? For Idira IGA Customers A review was performed using CyberArk’s vulnerability management tools. Based on results available to date, no additional components requiring action have been identified beyond those already remediated. For All Other Idira Products A review was performed using CyberArk’s vulnerability management tools. Based on results available to date, we have not identified components requiring remediation actions.   Were updates, patches, or mitigations applied? For Idira IGA Customers Updates have been applied to components identified during the review. Additionally, a Web Application Firewall (WAF) rule was implemented on the day the CVE was published as an added protective measure. For All Other Idira Products Since affected components were not identified, no patches were required; however, Idira continues to monitor and evaluate relevant security information as part of its ongoing security practices.
View full article
Table of Contents Introducing the Identity Governance & Administration (IGA) Success Path Identity Governance & Administration Intro to User Source of Truth Established Intro to Centralized User and Access Visibility Intro to Automated User Access Reviews for Compliance Intro to Continuous Access Posture Management Lifecycle Management Intro to Automated Identity Management Intro to Joiner, Mover, Leaver (JML) Policy Enforcement          Introducing the Identity Governance & Administration (IGA) Success Path We’re excited to introduce the Identity Governance & Administration (IGA) Success Path — a structured roadmap designed to help your organization take control of identity and access risks, modernize security, and achieve measurable outcomes with Idira IGA.   The IGA Success Path offers clear, step-by-step guidance ensuring your program grows with your organization’s needs and priorities.   The Value of the IGA Success Path Following the IGA Success Path ensures you’re not just adopting features, but building a resilient, scalable identity management program. This guidance helps you: Achieve Faster Time to Value Automation of Access Reviews Smarter Provisioning and Lifecycle Management AI-Driven Governance Unified Visibility and Integration To learn more, explore the IGA capability sections below for practical guidance, helpful resources, and the next steps on your IGA journey with CyberArk.   Identity Governance & Administration [Click to Expand] User Source of Trust Established  Intro to User Source of Truth Established Without a central directory, identity management quickly devolves into chaos — duplicate accounts, unknown users, and mismatched permissions can thrive in the shadows. The User Source of Truth capability brings order by consolidating identities across all your SaaS, on-prem, cloud, and custom applications into one reliable directory. It’s the cornerstone of your IGA program, setting the stage for clear access governance, risk reduction, and future automation. Complete these recommended steps to ensure your organization is set up for success with User Source of Truth.   1. Meet Requirements To get started, confirm the following prerequisites are in place: Your primary directory (such as Active Directory, LDAP, or cloud directory) is identified and ready for integration. A supported import method is selected (API connection, Idira Universal Sync, CSV upload, or PO Box integration). Single Sign-on (SSO) to the IGA console is available to streamline login for application owners and reviewers.   2. Understand Expected Value Establishing a single source of truth brings immediate, measurable improvements to your identity management approach. Here’s what to expect: Unified and centralized directory: Easily see all users and their associated access, eliminating data silos. Streamlined login experience: Enable secure, single sign-on for reviewers and owners. Cleaner data, fewer blind spots: Confidently identify who has access to what, and flag orphaned accounts. Foundation for IGA automation: Build the groundwork for streamlined access reviews, lifecycle management, and compliance workflows.   3. Establish Metrics Here are the key metrics to track your progress: Directory sync rate: Percentage of primary and in-scope directories successfully connected. SSO adoption rate: Number of owners/reviewers using SSO to access the IGA platform.   4. Achieve User Source of Truth With requirements and objectives in place, move forward by: Syncing and configuring your directory using your selected integration method. Setting up SSO for streamlined, secure access.   5. Post-Setup Activities After your source of truth is established: Regularly review and reconcile directory sync and SSO usage reports. Maintain ongoing accountability by keeping application owner records current. Use your directory foundation to scale identity management and enable additional IGA capabilities as your environment grows.   Resources [Docs] Log in to Idira IGA (powered by Zilla)   [Docs] Set up Idira IGA (powered by Zilla) [Docs] Designate a Directory [Docs] Configure Single Sign-On [Success Blog] IGA Best Practice – The Importance of an Accurate User Directory   Completing these steps gives your organization clarity, consistency, and control—a vital platform for secure, efficient identity governance.   [Click to Expand] Centralized User and Access Visibility Intro to Centralized User and Access Visibility Centralizing User and Access Visibility bridges the gap between knowing who your users are and understanding what they have access to across every application in your environment. This capability connects your critical SaaS, on-prem, cloud, and custom apps to bring all access data under one roof. The result? You lose the blind spots and gain a unified, actionable view for smarter governance, compliance, and risk reduction. Complete these recommended steps to set up your organization for success with Centralizing User and Access Visibility.   1. Meet Requirements To get started, confirm the following prerequisites are in place: A source-of-truth directory is synced and configured in your IGA platform. Single Sign-On (SSO) is enabled for application owners and reviewers. Documenting in-scope applications and assigning application owners for clear accountability. Cleansing and aligning attributes, then mapping and migrating users as needed. Flagging and resolving unknown accounts to regain full control over your identity landscape.   2. Understand Expected Value Centralizing User and Access Visibility brings immediate, measurable improvements to how you manage and govern access across your applications. Here’s what to expect: Unified view of users and permissions: Gain a single, consolidated view of users and their entitlements across SaaS, on-prem, cloud, and custom applications, shrinking security blind spots. Stronger foundation for automation: Establish the baseline needed for automated access reviews, provisioning, and lifecycle management. Earlier risk detection: Identify over-privileged, misaligned, or orphaned accounts sooner, before they become audit findings or security incidents. Simplified compliance evidence: Quickly answer “who has access to what” with centralized, audit-ready access data and reports. Context for better decisions: Give application owners and reviewers the context they need to make confident, well-informed access decisions.   3. Establish Metrics Here are the key metrics to track your progress: Application integration rate: Percentage of in-scope applications successfully integrated into IGA.   4. Achieve Centralized User and Access Visibility With requirements met and value defined, you’re ready to connect the dots and unify your access data: Connect and integrate your full application portfolio using direct API connections, universal sync connectors, or scheduled CSV imports. Onboard and train app owners and reviewers in the IGA platform to ensure ongoing participation. Validate and clean data as you go — resolving mismatched attributes and closing gaps. Correlate accounts between your directory and applications to build a clear, actionable map of user access.   5. Post-Setup Activities After setup, keep momentum by: Regularly reviewing application integrations and access reports for completeness and anomalies. Monitoring for new or decommissioned apps and updating your integrations accordingly. Fine-tuning user attribute mapping and data quality for continuous accuracy. Updating workflows as your environment evolves to maintain visibility and minimize hidden risk.   Resources [Docs] Sync an application using API integration [Docs] Sync an application with the Idira Universal Sync browser extension [Docs] Sync an application with a CSV file [Docs] Idira PO Box   Centralized user and access visibility sets you up for everything that follows, making compliance easier, audits simpler, and identity risk less mysterious.   [Click to Expand] Automated User Access Reviews for Compliance Intro to Automated User Access Reviews for Compliance Manual access reviews are a recurring roadblock for IT and security teams— they can be slow, error-prone, and often lead to a scramble before audit deadlines. The Automated User Access Reviews for Compliance capability removes the pain and friction from this process. By automating periodic access campaigns, your organization can ensure regulatory requirements are met efficiently, access entitlements are kept in check, and audit requests move from stress-inducing to streamlined. Complete these recommended steps to successfully implement Automated User Access Reviews for Compliance.   1. Meet Requirements To get started with Automated User Access Reviews for Compliance, confirm you have the following prerequisites: Your Idira IGA tenant is activated and configured for user and access visibility. Key applications and directories are integrated into your IGA platform. Application owners and reviewers are identified and onboarded. Notification channels (e.g., email, Slack, Microsoft Teams, or your chosen methods) are enabled for review prompts. Verifying all application integration syncs are up to date to ensure data quality and recency before launching user access review (UAR) campaigns.   2. Understand Expected Value Automated User Access Reviews for Compliance transforms manual, spreadsheet-driven campaigns into consistent, repeatable review cycles. Here’s what to expect: Faster audit preparation: Use consolidated, audit-ready reports and evidence packets to reduce prep time before audits. Consistent, repeatable campaigns: Standardize how reviews are launched, performed, and documented to reduce manual oversight and human error. Reduced excess permissions: Identify and remove unnecessary or excessive access on a regular cadence, minimizing risk exposure between review cycles. Stronger compliance posture: Demonstrate periodic reviews with clear, verifiable records that align with regulatory and internal requirements. Streamlined reviewer experience: Use automated notifications and clear workflows to help reviewers complete their tasks on time.   3. Establish Metrics Here are the key metrics to track your progress: Campaign completion time: Average time it takes reviewers to complete each access review campaign. Evidence packet generation: Number of evidence packets produced and used to support audits and regulatory inquiries.   4. Achieve Automated User Access Reviews for Compliance Complete these recommended steps to successfully achieve Automated User Access Reviews for Compliance. Define review cycles and campaign milestones in line with audit and compliance requirements. Configure campaigns—set in-scope apps, select reviewers (for example, app owners or managers), and assign due dates. Enable automated notifications to reviewers, delivered by email and/or your preferred collaboration tools. Launch campaigns and monitor progress, ensuring all access reviews are completed and any required access revocations are efficiently actioned. After campaign completion, export an evidence packet to support audits and regulatory inquiries. This closes the loop and provides a clear trail of compliance.   5. Post-Setup Activities Continue optimizing your automated user access reviews with these ongoing actions: Regularly review campaign results for trends and improvement opportunities. Tune notification settings and reviewer assignments to fit your organization’s evolving needs. Align review frequency with changes in compliance mandates or internal policy. Onboard new applications and account owners into review cycles as your environment grows. Leverage campaign data to refine access policies and reduce risks even further.   Resources [Docs] Create and run an access review campaign [Success Blog] IGA Best Practices – Maximizing Visibility in User Access Review Campaigns [Success Blog] Utilizing the Campaign Readiness feature for Accurate Access Reviews [Training] Idira IGA - User Access Reviews (UAR) for Reviewers By following these steps, your team will spend less time wrestling with manual processes and more time reinforcing proactive, audit-ready identity security.   [Click to Expand] Continuous Access Posture Management Intro to Continuous Access Posture Management Your organization has automated access reviews and has built a solid compliance rhythm. But security isn’t set-and-forget. Changes in roles, new apps, dormant service accounts, or shifting permissions can turn your environment messy between scheduled reviews. That’s where Continuous Access Posture Management (CAPM) comes in. Instead of catching problems after the fact, or scrambling during audit season, CAPM helps you monitor, detect, and remediate risk around the clock. Complete these recommended steps to ensure your organization is set up for success with Continuous Access Posture Management.   1. Meet Requirements To get started with CAPM, ensure the following prerequisites are met: Your Idira IGA tenant is activated and fully configured for your environment. You have integrated key applications and data sources for access monitoring. Your organization has defined a Segregation of Duties (SoD) matrix that outlines which access combinations are high risk or toxic. Out-of-the-box policy templates are reviewed and tailored for your environment. Automated response actions (such as alerts or ticketing workflows) are set up for key policy violations.   2. Understand Expected Value CAPM shifts your program from point-in-time checks to ongoing, proactive risk management. Here’s what to expect: Continuous compliance between reviews: Maintain visibility and policy enforcement in the gaps between scheduled access review campaigns. Proactive remediation: Automatically detect and remediate inappropriate, risky, or over-privileged access before it becomes an audit issue or security incident. Reduced SoD violations: Monitor and catch toxic or conflicting access combinations early, lowering the likelihood of Segregation of Duties violations. Always-ready audit evidence: Keep a current record of policy violations, investigations, and remediation actions to simplify audit conversations. Lower operational burden: Free security and compliance teams from “audit panic mode” with ongoing policy enforcement and automated workflows.   3. Establish Metrics Here are the key metrics to track your progress: Security findings detected: Number of risks, policy violations, or anomalies surfaced by CAPM over a given period. Monitoring coverage: Percentage of in-scope applications and data sources covered by CAPM policies and monitoring.   4. Achieve Continuous Access Posture Management With requirements in place, you’re ready to deploy CAPM and continuously monitor for risky access across your environment: Define and configure your SoD matrix to identify and prevent unacceptable access combinations. Enable out-of-the-box policies to surface issues such as orphaned accounts, excessive permissions, and misconfigured MFA. Assign automated actions so policies can trigger alerts, open tickets, or launch remediation workflows. Adjust monitoring scope and automation rules for hybrid or cloud environments and validate changes with compliance teams before going live.   5. Post-Setup Activities After setup, keep CAPM effective by: Regularly reviewing policy findings and remediation reports for trends or anomalies. Tuning policies as your environment, applications, and risk posture evolve. Monitoring integration health and ensuring new applications are onboarded into CAPM. Reassessing your SoD matrix periodically to reflect organizational or compliance changes.   Resources [Docs] Secure module [Docs] Policy library [Docs] Upload and edit segregation of duties (SoD) policies This ongoing effort helps you maintain an accurate, always-on security posture that supports audit readiness and reduces access risk over time.   These four capabilities provide a strong foundation for reducing identity risk, improving compliance, and giving your teams clearer, more reliable access data. Whether you adopt them individually or together, each one helps build a more consistent, transparent, and resilient approach to identity governance that can evolve alongside your organization.   Lifecycle Management You’ve built a solid foundation with visibility and automated reviews, but what happens when an employee's role changes? Identity is never static. People join companies, move between departments, and eventually leave. Managing these transitions manually is not just slow, it's a security risk. This next stage of the IGA Success Path will focus on Lifecycle Management. We'll explore Automated Identity Management and Joiner, Mover, and Leaver (JML) Policy Enforcement.   [Click to Expand] Automated Identity Management Intro to Automated Identity Management Automated Identity Management brings intelligence and consistency to your identity lifecycle by using AI-powered profiles to define “who should have access to what.” This capability establishes birthright access and suggested profile grants that guide automated provisioning decisions and reduce manual effort. With clear, data-driven identity context in place, your organization is prepared to scale lifecycle automation with confidence. Complete these recommended steps to ensure your organization is set up for success with Automated Identity Management.   1. Meet Requirements To get started with Automated Identity Management, confirm the following prerequisites are in place: Your Idira IGA tenant is activated and fully configured. Foundational IGA capabilities have been achieved (User Source of Truth, Centralized Visibility, Automated Access Reviews, and CAPM). Profiles, and access context, are available across integrated directories and applications. Application owners and stakeholders understand how access profiles will inform Joiner, Mover, and Leaver (JML) policies.   2. Understand Expected Value Automated Identity Management helps you shift from manual provisioning decisions to a consistent, policy-driven lifecycle foundation. Here’s what to expect: Visibility into expected access: Identify who should have access to which applications and entitlements based on real-world identity patterns. Birthright access defined: Establish mandatory, baseline permissions that all users in a role or profile require. Smarter provisioning decisions: Use AI-powered suggested profile grants to support accurate and efficient access assignments. Foundation for JML policies: Provide the structure needed to automate onboarding, transfers, and offboarding with confidence.   3. Establish Metrics Here are the key metrics to track your progress: Percent of profiles activated: Measures how many access profiles are active and informing provisioning decisions. Coverage by profile grants (50%+ recommended): Indicates how much of your environment is mapped to birthright and suggested access.   4. Achieve Automated Identity Management With the prerequisites in place and value understood, follow these steps to operationalize Automated Identity Management: Build and refine AI-powered profiles using access patterns across your environment. Define birthright access that applies automatically when new users join. Activate suggested profile grants to guide provisioning decisions for additional applications or entitlements. Validate profiles with application owners to ensure accuracy before scaling to more apps or business units. Train stakeholders on how profile-driven access influences request workflows and future JML automation.   5. Post-Setup Activities After implementing Automated Identity Management: Regularly review profile accuracy and update them as roles, teams, or applications evolve. Expand profile coverage across additional identity types and departments. Monitor usage of profile-driven request workflows and adjust as necessary. Align provisioning decisions with CAPM and access review findings to maintain continuous accuracy.   Resources [Docs] AI Profiles   With Automated Identity Management in place, you gain consistent, data-driven access decisions that reduce manual work and strengthen governance. This foundation prepares your organization for efficient, secure JML automation.   [Click to Expand] JML Policy Enforcement Intro to JML Policy Enforcement People join, move within, and eventually leave your organization, and every transition introduces potential access risk. JML Policy Enforcement allows you to automate these lifecycle transitions using clear, profile-backed rules that determine exactly what access should be granted, changed, or removed. With JML policies in place, identity governance becomes continuous, predictable, and secure. Complete these recommended steps to ensure your organization is set up for success with JML Policy Enforcement.   1. Meet Requirements To get started with JML Policy Enforcement, confirm the following prerequisites are in place: Your Idira IGA tenant is activated and configured. Automated Identity Management is fully achieved and profile grants are established. Foundational IGA capabilities and visibility are in place to support accurate decision-making. Birthright and suggested profiles reflect accurate access baselines across the workforce.   2. Understand Expected Value JML Policy Enforcement transforms identity changes into automated, consistent workflows. Here’s what to expect: Automated and accurate onboarding: Users receive the correct birthright access the moment they join. Reduced access drift during transfers: Movers automatically gain required access and lose what is no longer appropriate. Secure and reliable offboarding: Leaver actions are enforced automatically to remove access quickly and reduce risk. Consistent policy application: JML policies ensure access decisions reflect your governance model, not ad-hoc judgment calls.   3. Establish Metrics Here are the key metrics to track your progress: Joiner policies activated: Measures how many onboarding policies are live and automatically granting correct birthright and profile-based access. Mover policies activated: Indicates how effectively transitions (role, department, or responsibility changes) are triggering automated access updates. Leaver policies activated: Tracks how consistently access is being removed during offboarding to reduce risk and prevent lingering permissions.   4. Achieve JML Policy Enforcement With Automated Identity Management fully configured, you’re ready to enforce lifecycle automation: Configure Joiner policies to automatically assign birthright and profile-driven access. Configure Mover policies to detect role or department changes and update entitlements accordingly. Configure Leaver policies to remove access promptly and consistently across all applications connected to Idira IGA. Validate policy logic with application owners to ensure changes accurately reflect real-world access needs. Test lifecycle transitions in a controlled environment before expanding to production and additional business units.   5. Post-Setup Activities After JML Policy Enforcement is live: Continually monitor policy execution and adjust based on organizational changes. Expand policy coverage as additional profiles and applications are onboarded. Review CAPM findings to detect and resolve lifecycle-related policy gaps. Ensure audit teams understand how JML policy logs provide a consistent trail of provisioning and deprovisioning activity.   Resources: [Docs] Enable provisioning policies   With JML Policy Enforcement in place, your identity lifecycle becomes predictable, secure, and fully automated across joiner, mover, and leaver events. This ensures users have the right access at the right time — and that unnecessary access is removed just as reliably.   By completing these six capabilities you’ve built a strong, scalable foundation for identity governance. This end-to-end approach ensures users receive the right access from day one, risky permissions are continuously identified and resolved, and lifecycle transitions happen accurately and automatically. With these capabilities in place, your organization is positioned to reduce identity risk, streamline compliance, and operate a more consistent, predictable, and secure identity program that grows with your business.   Visit the IGA Resource Center to connect with fellow peers and Idira experts who are ready to support you. For further help, feel free to reach out to your Idira Account Team directly.      
View full article
Question Does the NIST Vulnerability CVE-2026-111497 apply to Idira products? Answer Idira SECURITY UPDATE Node.js Brotli decoder out-of-bounds write, CVE-2026-111497  Issued: October 23, 2026 Updated: October 26, 2026 Next Schedule Update: October 27, 2026 Version: 2.1 Severity: High GENERAL INFORMATION  None of the detected resources is internet-accessible, and there is no indication of exploitation. We have identified owners and established remediation tracking; an updated status will be shared by 2026-10-26. Affected Software The following table summarizes the Idira products’ status as it relates to these vulnerabilities, and any actions needed to be performed by customers based on information available at this time: Access and Identity Management Product components Status Action Required to Apply Mitigation Comments Identity Service (SaaS), Mobile App Fixed No action is required by customers Not exploitable - vulnerable package not in-use.  Identity Compliance Service (SaaS) Not Affected No action is required by customers   Workforce Password Management Service (SaaS) Not Affected No action is required by customers   Secure Web Sessions Service (SaaS) Not Affected No action is required by customers   Identity Flows Service (SaaS) Not Affected No action is required by customers   Machine Identity Security (Formerly Venafi, SaaS)       Certificate Manager Not Affected No action is required by customers   Cert Manager Not Affected No action is required by customers   Workload Identity Manager Not Affected No action is required by customers   Zero Touch PKI Not Affected No action is required by customers   Machine Identity Security (Formerly Venafi, Self-Hosted)       Certificate Manager Not Affected No action is required by customers   Code Sign Manager Not Affected No action is required by customers   SSH Manager for Machines Not Affected No action is required by customers   Zero Touch PKI Not Affected No action is required by customers   Idira IGA Service (SaaS) Fixed DoS impact with no impact on confidentiality Privileged Access Management Product components Status Action Required to Apply Mitigation Comments PAM - Self Hosted Vault Not Affected No action is required by customers   Privilege Session Management (PSM) Not Affected No action is required by customers   Privilege Session Management for SSH (PSMP) Not Affected No action is required by customers   Central Policy Manager (CPM) Not Affected No action is required by customers   Password Vault Web Access (PVWA) Not Affected No action is required by customers   Discovery and Audit (DNA) Not Affected No action is required by customers   HTML5GW Not Affected No action is required by customers   Privileged Threat Analytics (PTA) Not Affected No action is required by customers   Privilege Cloud Vault Not Affected No action is required by customers   Privilege Session Management (PSM) Not Affected No action is required by customers   Privilege Session Management for SSH (PSMP) Not Affected No action is required by customers   Central Policy Manager (CPM) Not Affected No action is required by customers   Secrets Rotation Service (SRS) Not Affected No action is required by customers   Web Portal Not Affected No action is required by customers   HTML5GW Not Affected No action is required by customers   Backend infrastructure Not Affected No action is required by customers   Remote Access Service (SaaS), Connector, Mobile App Not Affected No action is required by customers   Secure Infrastructure Access For SSH Not Affected No action is required by customers   For RDP Not Affected No action is required by customers   For Databases Fixed Not exploitable - vulnerable package not in-use. For Kubernetes Not Affected No action is required by customers   Endpoint Privilege Security Product components Status Action Required to Apply Mitigation Endpoint Privilege Manager       Service (SaaS) Not Affected No action is required by customers Windows Agent Not Affected No action is required by customers MacOS Agent Not Affected No action is required by customers Linux Agent Not Affected No action is required by customers Secrets Management Product components Status Action Required to Apply Mitigation Secrets Manager, Self-Hosted (formerly Conjur, Self-Hosted) Not Affected No action is required by customers Secrets Manager, SaaS (formerly Conjur Cloud) Service (SaaS), Connector Not Affected No action is required by customers Credential Providers CP, CCP, ASCP Not Affected No action is required by customers Secrets Hub Not Affected No action is required by customers Cloud Security Product components Status Action Required to Apply Mitigation Comments Cloud Entitlements Manager Not Affected No action is required by customers   Secure Cloud Access Not Affected No action is required by customers   Secure AI Agents Fixed   Not exploitable in our use: the sidecar never requests or decodes Brotli data, only talks to Datadog, and has no inbound exposure. Shared Services Product components Status Action Required to Apply Mitigation Comments Session monitoring Fixed No action is required by customers Product was affected but not exploitable. Patch applied and deployed to production. Cloud onboarding Not Affected No action is required by customers   Connector Management Not Affected No action is required by customers   Identity Security Intelligence Not Affected No action is required by customers   CyberArk-developed Marketplace Integrations Product components Status Action Required to Apply Mitigation Certified and Trusted certification levels Not Affected  No action is required by customers  
View full article
Issue Error Response: 401 Unauthorized with error response {"code":124,"message":"Invalid access token."} for url=https://api.zoom.us/v2/users. Inner Error: Error calling refreshAccessTokenFn with Response {"reason":"Invalid Token!","error":"invalid_grant"}   Cause Refresh tokens expire after 15 years, but they can only be used once to get the next refresh token. You must always use the latest refresh token for the next refresh request.   Resolution See Integrate Zoom for more information on how to sync the application with re-authentication.   
View full article
Issue Sync Failed with Error - Cancelling sync because 0 accounts discovered.   Cause This error occurs when the response for the API call below returns an empty result. GET 'https://sentry.io/api/0/organizations/<OrganizationSlug>/users/' Resolution Run the curl comment below and replace the <OrganizationSlug> and <AuthToken> with the values from the Sentry app configs to check the response of the API call: curl --request GET 'https://sentry.io/api/0/organizations/<OrganizationSlug>/users/' --header 'Authorization: Bearer <AuthToken>' You can retrieve the <AuthToken> from the app ID in AWS secret manager. This value is masked in the Sentry UI. If the response is an empty array, there are no users present.  
View full article
Issue Sync Failed with Error- 404 Not Found Cause This error occurs when the account from which the OAuth2 app is created is in a Suspended state or not in an Active state.   Resolution Create a new OAuth2 app in Jira from an active admin account. See Integrate Jira for more information on how to create the OAuth2 app.  
View full article
  • 14 Posts
  • 7 Subscriptions
Labels