DOCSEARCHbyAlgolia
Submit Docs

RSA Governance and Lifecycle

website·Indexed 29 days ago

https://pradeepkg.github.io/RSA/

Documentation for RSA's identity governance and workforce management solutions, including API references for security settings, change requests, and user management (Lifecycle version 8.0.0.188886 P10 HF01). It provides integration guides and collector configurations for various applications such as Workday, PagerDuty, Datadog, PingOne, and SAP BPC.

Tokens
92.8K
Snippets
370
Records
557
Agent score
73%

What's inside RSA

  1. Overview of IBM iSeries (AS400) Identity Management via QSYS2

    The IBM iSeries (AS400) uses the QSYS2 system-wide catalog schema to provide centralized metadata views for identity and access management, similar to INFORMATION_SCHEMA in other databases. Key views include:

    • USER_INFO: Lists all user profiles system-wide.
    • SYSTABLES: Lists all tables across every schema/library.
    • AUTHORIZATION_LIST_USER_INFO: Lists all authorization lists and memberships.
    • GROUP_PROFILE_ENTRIES: Lists all group memberships for every user.

  2. Overview of RSA G&L integration with Keeper Enterprise

    The RSA G&L plugin integrates with Keeper Enterprise using the Keeper Secrets Manager (KSM) Java SDK to retrieve credentials for collectors and connectors. The integration ensures that credentials are not cached; every retrieval fetches the current password directly from Keeper. All HTTPS transport and end-to-end encryption are managed by the KSM SDK.

  3. Overview of attribute synchronization in RSA Governance & Lifecycle

    RSA Governance & Lifecycle (RSA G&L) provides attribute synchronization to maintain consistency between user identity data and account data across downstream systems. This process automates the synchronization of key attributes—including roles, email addresses, and group memberships—to reduce manual errors and ensure that connected systems remain up-to-date.

  4. Overview of RSA G&L integration with BeyondTrust Password Safe

    The BeyondTrust Password Safe plugin integrates RSA Governance and Lifecycle (G&L) using the BeyondTrust REST API v3 and OAuth 2.0 authentication. The integration allows RSA G&L to retrieve credentials for collectors and connectors. To ensure password rotation policies are respected, credentials are not cached; each request fetches the current password directly from BeyondTrust.

  5. Overview of Deltek CostPoint ERP Capabilities

    Deltek CostPoint is an ERP software solution specifically designed for government contractors. It provides integrated management for project accounting, labor management, manufacturing, and business intelligence. Key functional modules include:

    • Payroll, Budgeting, and Planning
    • Reporting and Enterprise Insights (Planning and Forecasting)
    • Human Resources and Benefits
    • Manufacturing and Compliance
    • Subcontractor and Contract Management
    • Time and Expense tracking

  6. Overview of RSA G&L Attribute Synchronization

    Attribute synchronization in RSA Governance & Lifecycle (G&L) ensures consistency between user identity data and account data across downstream systems (e.g., Active Directory, Oracle databases). When a change in a user attribute is detected after identity data collection and unification, G&L generates a change request with change items for each mapped account in the target business sources to update the corresponding attributes.

  7. Understand the about command API response

    A successful response (HTTP 200) returns a data object containing:

    • server-version: The version of the server software.
    • database-version: The version of the database schema.
    • patches: A list of installed patches (empty if none are installed).
    {
    "data": {
        "type": "about",
        "database-version": "8.0.0.184636",
        "server-version": "8.0.0.184636",
        "patches": "P10_HF01"
    }
}

  8. Configure parameters for the about command API

    The about command accepts the following query parameters:

    • cmd: Must be set to about.
    • format: Determines the response format. Options are properties (default, returns key=value pairs) or json (returns a JSON object).

  9. PingOne Identity and Access Management (IAM) Capabilities

    PingOne is an IAM solution by Ping Identity providing secure user authentication, authorization, and single sign-on (SSO). It includes multifactor authentication (MFA) and adaptive security for access control. Regarding its identity model, PingOne supports Accounts and Groups, but does not support Identities, App Roles, or Entitlements.

  10. Reference the PV_CHANGE_REQUEST_WORK_ITEM public view columns

    The PV_CHANGE_REQUEST_WORK_ITEM public view provides detailed information about change request work items. Use these column names when specifying the columns parameter in your request to retrieve specific work item data.
    // Example of columns available in PV_CHANGE_REQUEST_WORK_ITEM
{
  "workitem_id": "Composite identifier (activity_instance_id:activity_instance_database:workflow_instance_iteration)",
  "workflow_instance_name": "Name of the workflow step (e.g., Supervisor Approval)",
  "complete_by": "User ID responsible for completion (-1 for system)",
  "category_name": "Category of the work item",
  "change_request_id": "Foreign Key referencing CHANGE_REQUESTS.ID",
  "job_reference": "Reference identifier for the job",
  "activity_instance_id": "ID of the activity instance in the workflow engine",
  "activity_instance_database": "Database identifier (e.g., WPDS)",
  "workflow_instance_iteration": "Iteration number of the workflow instance",
  "process_instance_id": "ID of the associated process instance",
  "name": "Display name of the work item",
  "work_state": "Current state (e.g., Completed, Canceled)",
  "job_state_id": "Numeric identifier for the job state",
  "planned_time": "Planned completion time in seconds",
  "duration_type": "Type of duration measurement",
  "accumulated_time": "Time accumulated in seconds",
  "available_date": "Date/time the work item became available",
  "open_date": "Date/time the work item was opened",
  "first_open_date": "First date/time the work item was opened",
  "complete_date": "Date/time the work item was completed",
  "last_modified_user_id": "User ID who last modified the record (-1 for system)",
  "last_modified_date": "Date/time of the last modification",
  "completion_code": "Numeric completion code",
  "due_date": "Date/time the work item is due",
  "in_queue_time_value": "Queue time as fractional days",
  "in_queue_time_hours": "Queue time in whole hours",
  "in_queue_time_days": "Queue time in whole days",
  "in_queue_time_text": "Human-readable queue time",
  "open_time_value": "Open time as fractional days",
  "open_time_hours": "Open time in whole hours",
  "open_time_days": "Open time in whole days",
  "open_time_text": "Human-readable open time",
  "total_time_value": "Total elapsed time (available to complete) as fractional days",
  "total_time_hours": "Total elapsed time in whole hours",
  "total_time_days": "Total elapsed time in whole days",
  "total_time_text": "Human-readable total elapsed time",
  "overdue_time_value": "Overdue time as fractional days",
  "overdue_time_hours": "Overdue time in whole hours",
  "overdue_time_days": "Overdue time in whole days",
  "overdue_time_text": "Human-readable overdue time",
  "available_date_no_time": "Available date at midnight",
  "available_date_year": "Year of available date",
  "available_date_month": "Month number (1-12)",
  "available_date_month_text": "Full month name",
  "available_date_month_abv": "Abbreviated month name",
  "available_date_day": "Day of month",
  "available_week_of_year": "ISO week number",
  "open_date_no_time": "Open date at midnight"
}

  11. Understand the getRequestItems response schema

    The response contains metadata about the request and a list of RequestItems.

    Top-level Fields:

    • NumRequestItems: Total number of items in the request.
    • WorkItemId: The approval work item ID (id:WPDS:n format); empty if queried by request-id.
    • RequestId: Numeric ID of the change request.
    • RequestStatus: Current status (e.g., 'Approvals Phase Completed').
    • RequestItems.RequestItem: An array of request item objects (or a single object if only one is returned).

    RequestItem Object Fields:

    • ItemId: Unique numeric ID of the item.
    • TypeDescription: Human-readable change type (e.g., 'Add application role to user').
    • Operation: The action (e.g., 'Add', 'Remove').
    • OperandType: Target object type (e.g., 'User Account').
    • ValueType: Entitlement or value type (e.g., 'ApplicationRole').
    • EntitlementType: Display name of the entitlement type.
    • EntitlementName: Display name of the entitlement.
    • EntitlementRawName: Unformatted name of the entitlement.
    • BusinessSource: Name of the business source.
    • State: Current state (e.g., 'Pending Approval', 'Completed').
    • IsChangeToApprove: Boolean; true if queried by approval-id and the item is in scope for the approver; false if queried by request-id.
    • UserName: Display name (LastName, FirstName) if OperandType is User.
    • UserId: Numeric ID if OperandType is User.
    • AccountName: Login name if OperandType is Account.
    • ApplicationRoleName, UserGroupName, GlobalRoleName, GlobalRoleSetName, Data_Resource_Name: Specific identifiers based on the entitlement type.

  12. Set headers for RSA Governance & Lifecycle API requests

    Requests to the about endpoint require the following headers:

    • Authorization: A valid Bearer token.
    • Accept: application/json
    • Content-Type: application/json