The following issues were fixed in RSA Identity Governance and Lifecycle version 7.1.
Issue | Description |
---|---|
SF-803269 ACM-63517 | Specifying date-type attributes for user review criteria resulted in the following error: ORA-01840: input value not long enough for date format. |
SF-835743 ACM-66520 | The Grouped by Application tab for a user review did not display groups and roles by their directory or role set as expected. |
SF-976100 ACM-76116 | "Update Un-Reviewed Items" action in review item history showed AveksaAdmin instead of the actual user who performed the action. |
SF-817109 ACM-64793 | Reviewer delegation or reassignment comments greater than 4,000 characters in length prevented saving a review change with the JDBCException - ORA-01461 error. |
SF-831090 ACM-67887 | Reviewers with only "save" privileges and not sign-off privileges could not properly see review items queried by V_AVR_ER_ITEM_DETAIL. |
SF-1008441 ACM-78070 | The accounts and entitlements count displayed incorrect values when a reviewer applied more than one grouping. |
SF-1037868 ACM-79267 | The review results for user access reviews did not include the role entitlements for all users. |
SF-1008019 ACM-78225 | Bulk Actions did not apply to accounts with unreviewed entitlements if the accounts were signed off. |
SF-1202327 ACM-89970 | Large-scale reviews used all available memory and crashed the server with OutOfMemory errors. |
Issue | Description |
---|---|
SF-903529 ACM-71833 | In a form-based workflow where forms were approved and then fulfilled, the workflow intermittently skipped the approval step. |
SF-942388 ACM-73931 | Revocation change requests did not display work items. |
SF-983142 ACM-75849 | Rejecting one user in a request with multiple users during the approval phase removed too many pending accounts. |
SF-917409 ACM-72808 | Under Requests > Activities > By Entitlement and Requests > Approvals > By Entitlement, the Monitoring Policy view does not display activities for deleted accounts. |
SF-823162 ACM-68232 | The CSV file exported from Requests > Activities was corrupted. |
SF-1025998 ACM-79262 | Account removal triggered for a user with "Complete Manual Activity before collection" set to "Yes" did not completely remove accounts from user access before the collection. |
SF-909706 ACM-72131 | On the By Entitlement tab of the My Activities page, an account's custom attributes were not populated. |
SF-959975 ACM-74600 | The Fulfillment Handler was using the XML configuration instead of the internal configuration. |
SF-898527 ACM-73205 | Manual workflow activity showed an incorrect timestamp when an escalation canceled the workflow. |
SF-1063876 ACM-81061 | A "Request could not be handled" error occurred when clicking on a submitted form request created via web service. |
SF-865253 ACM-70239 | The "last reviewed" or "completed on" date collected in a user access review was not displayed in the user access tab. |
SF-1121505 ACM-86374 | Change Verification was still pending for an Account or group access removal after the account or group was deleted. |
Issue | Description |
---|---|
SF-894540 ACM-71583 | After deleting account mappings, entitlements associated with the mapped accounts were still displayed under the User Access tab. |
SF-894535 ACM-71731 | Accounts that were mapped manually from an import file before upgrading could not be unmapped in bulk. |
SF-910809 ACM-72136 | The Oracle error ORA-06512 stopped the process when unmapping shared accounts. |
Issue | Description |
---|---|
SF-1000278 ACM-77008 | The AFX SOAP Connector used the wrong SOAPAction Header from the WSDL when multiple SOAPActions shared the same SOAP XML request body. |
SF-1021681 ACM-79230 | ServiceNow documentation needed additional details about permissions. |
Issue | Description |
---|---|
SF-854649 ACM-67933 | Users that were deleted and then re-activated could not login using ADC authentication. |
SF-982764 ACM-75796 | A login with invalid credentials reported an error message with "account: {0}" instead of the account that could not log in. |
SF-983896 ACM-75612 | The query parameter SSOLogin=false, used to bypass SSO, no longer worked after upgrading to 7.0.2. |
SF-1031227 ACM-78712 | An error stopped the password reset if the Challenge Questions page did not validate mandatory questions that were skipped. |
SF-1059055 ACM-80559 | Users had issues resetting a password because account names were not case-sensitive for an external password reset as they are for the login screen. |
Issue | Description |
---|---|
SF-943653 ACM-73734 | In the new Workflow Editor, the context menu for workflow variables was missing the options Previous Node Assigned To and Previous Node Completed By. |
SF-928182 ACM-73104 | The number of escalations in a workflow was incorrectly limited. |
SF-866742 ACM-69358 | When creating a workflow for custom tasks, using the automatically populated Reference Name resulted in an error. |
SF-842253 ACM-67139 | Tooltip messages on a rejected change request incorrectly indicated that there was an error. |
SF-950758 ACM-74131 | When accounts were disabled, an incorrect change request item was created. |
SF-874232 ACM-71674 | When creating a change request, the user selection screen appeared twice when multiple forms were configured. |
SF-889452 ACM-72560 | The Cancel Change Request node for manual fulfillment workflows listed Reject Change Request selections that were not actually available for use. |
SF-974919 ACM-75383 | A sub-process node still expanded the workflow when the Enabled setting was unchecked. |
SF-816607 ACM-67252 | A high workflow volume of excessive Oracle transactions could, due to a race condition, cause some workflow requests to be stuck in open state, stall on nodes like the Manual Fulfillment Node, or generate an ORA-02291 integrity constraint error. |
SF-956207 ACM-75139 | In a manual activity workflow, a Mark Verified Node could erroneously complete verification of manual fulfillments. |
SF-745588 ACM-60984 | The user using the REST Web Services Node was unable to set "Content-Type", which instead defaults to "text/plain". |
SF-920455 ACM-73174 | When “Wait for Result” was selected, workflows were stuck in the Provisioning Command phase. |
SF-895630 ACM-71205 | Workflow Java node was unable to save configuration. |
SF-845740 ACM-67829 | After pending submission change requests were removed by a clean-up task, the pending accounts were deleted but the dependent change request items remained. |
SF-913090 ACM-72140 | A group entitlement was not included in a change request when added from a role review. |
SF-956470 ACM-74461 | The workflow job history did not filter out jobs that were being deleted by the purge process, causing an ORA-01722 invalid number error. |
SF-936413 ACM-73792 | An error could occur when all line items were rejected in a change request if the system processed the workflow before it could process the line item changes. |
ACM-76117 | Large workflows usually with more than 23 nodes could not be saved. |
SF-974932 ACM-75348 | The drop-down list of processes in a child workflow could not show a list of more than 100 processes. |
SF-820520 ACM-66029 | Duplicate 'remove' change items appeared from a request to remove a role from a user that had duplicated entitlements. |
SF-988230 ACM-76091 | The REST Web Service node could not use user data to process a response variable. |
SF-988600 ACM-76630 | The workflow editor would not allow an invalid workflow condition to be displayed on a decision node. |
SF-1000082 ACM-76911 | Passing null or undefined workflow variables between nodes may have been stopped by a null pointer exception error. |
SF-906471 ACM-72817 | Importing a workflow with the overwrite option did not update the workflow name. |
SF-997361 ACM-77724 | Conversions of decision nodes did not succeed unless performed during a patch upgrade. |
SF-1017258 ACM-77999 | A subprocess node did not handle the ability to add group and role owner attributes. |
SF-1025290 ACM-78311 | An unprivileged end user could edit the workflow to approve requests. |
SF-990759 ACM-76958 | Account data change verification for the Windows Server accounts collector would abort after running for more than 16 hours. |
SF-951308 ACM-77144 | Non-numeric values in the wp_proci table's lu_id field caused the workflow job table to not display properly. |
SF-1021962 ACM-78218 | The URL workflow variable didn’t resolve correctly when an escalation was raised on a request workflow. |
SF-847108 ACM-61009 | Performance optimizations for AFX queries in Oracle 12c. |
SF-042252 ACM-79705 | A business owner assigned to an application could approve and reject other, unassigned applications kept in the same directory for accounts grouped by business fields. |
SF-931653 ACM-73399 | In a workflow, a resource could not be modified when a dependent Group, User, or Role could not be found on an imported server. |
SF-917117 ACM-72339 | In the Workflow Editor, saving SQL nodes with the variable type Public could result in the Oracle error: "ORA-00972: Identifier is too long." |
SF-921304 ACM-72337 | When configuring a decision node to check whether a workflow variable exists, the Right Operand field is incorrectly required. |
SF-991315 ACM-76476 | Concurrent processing of a role management database update and change requests risked an indefinite open state for change requests. |
SF-999080 ACM-77324 | Workflow Editor SQL windows did not resize. |
SF-946297 ACM-73893 | A user could edit a workflow email node and save changes with the Refresh button without the required privileges for both actions. |
SF-965923 ACM-74833 | A collector node in the workflow editor did not validate for a selected account data collector. |
SF-921304 ACM-72550 | The save button did not enable for changing the "Evaluated to true" checkbox on a decision transition unless another change was made to the transition. |
SF-1018384 ACM-78740 | Exclusion rules for a node did not properly apply to employees designated as a delegate by an out-of-office supervisor. |
ACM-72111 | Workflow form compilation errors occurred due to conflicts with ports secured by SSL. |
SF-1044220 ACM-80257 | A change request did not successfully complete if a business owner's rejection re-mapped the account name derived from the account template to the account's unique ID. |
SF-992247 ACM-76647 | A rejected change request approval step did not display when the workflow had completed. |
SF-1046799 ACM-79688 | Workflow decision nodes always evaluated manually entered variables as false. |
SF-906005 ACM-71857 | An SQL error occurred when saving changes to an existing workflow process if it contained a delay node that was created in an earlier version of the product. |
SF-914725 ACM-72045 | A workflow copied from another workflow did not carry over the email body of the "Send Email" node. |
SF-1062447 ACM-81011 | Changes to due dates, priorities, and status could use cached data instead of the updated data. |
SF-1070592 ACM-81877 | Email approval templates incorrectly encoded the Email Approval Reply text. |
SF-1031265 ACM-81002 | The Workflow configuration to select 'Use Process configured on' was not available in the drop-down options after they paged. |
SF-1096258 ACM-83234 | The event type "Reject Changes handled by this workflow" was not available for Cancel Change Request nodes. |
SF-1018709 ACM-79677 | The email fulfillment handler did not contain an option to edit the email body or add workflow variables. |
SF-1101627 ACM-83545 | A Delete Account change request could be marked as complete but still show a status of "Pending Action". |
SF-1098925 ACM-83236 | Imported legacy workflows created before version 7.0.1 had a legacy value not handled by the new architect editor. |
Issue | Description |
---|---|
SF-881641 ACM-70617 | When a collected date did not match a supported date format, the entire collection fails, and the error ORA-01830 is displayed. |
SF-903111 ACM-71836 | Lotus Notes collections failed when attempting to use SSL communication. |
SF-919973 ACM-72616 | The Accounts data table for an ADC incorrectly displayed the Last Collected Date after a successful run. |
SF-890141 ACM-70748 | The example string for the Oracle Database collector URL had a typo that replaced a forward-slash with a colon. |
SF-021848 ACM-48713 | The App Metadata collector was case sensitive when referencing the owner ID fields. |
SF-556737 ACM-45979 | The App Metadata collector did not update a business owner reference when the business owner information was deleted and then added back since the last collection. |
SF-967914 ACM-75176 | Identity collection removed an account from the Access tab when a user was marked as deleted. |
SF-915352 ACM-72796 | Testing the connection for the Airwatch collector resulted in a JSON error. |
SF-792018 ACM-63785 | The activity owner did not save when creating a local entitlement collector. An edit was required to add the activity owner. |
SF-964094 ACM-76458 | After installing RSA Identity Governance and Lifecycle, the identity collector would not connect to Novell IDM. |
SF-991315 ACM-76565 | For a change request that failed due to an invalid CR_ID, the review submission did not roll back updates to the database as expected. |
SF-1003979 ACM-77722 | The application metadata collector could not use the "category" attribute of an application for collections. |
SF-999750 ACM-76886 | Deactivating an existing data access collector from the General tab discarded settings for user and group resolution rules. |
SF-00909993 ACM-71772 | ADCs are failing with the following error: “Unprocessed Continuation Reference”. |
SF-795126 ACM-62974 | Application metadata collections of wrong date formats for date attributes caused collection failures. |
SF-1048233 ACM-80958 | When using the Test button on a SQL query for a database collector, the screen incorrectly displayed a SQLException for a valid SQL statement. |
SF-954031 ACM-78053 | The transformer did not correctly create a CSV file for the CyberArk application. |
SF-1039961 ACM-79634 | The Salesforce collector did not collect LastLoginDate as expected due to an invalid date format error. |
SF-1058274 ACM-80940 | The WorkDay collector was failing with the following error: “Unmarshalling Error: unexpected element.” |
Issue | Description |
---|---|
SF-882233 ACM-71264 | When a chain of certificates was involved in the handshake, the SOAP connector failed over 2-way SSL. |
SF-877139 ACM-70139 | Attribute values edited to be blank did not carry over to the connector in attribute synchronization. |
SF-966500 ACM-75158 | Stored procedures called using a DB2 connector returned a null pointer exception. |
SF-947029 ACM-74335 | Unable to create a connector with a generic database using the DB2 connector template. |
SF-973647 ACM-75745 | AFX Connectors did not deploy when the connector dependency file ID exceeded 999. |
SF-862539 ACM-70218 | Disabled users were enabled after a password reset. |
SF-973760 ACM-75597 | The Archer connector did not deploy when the password to access had $ in the string. |
SF-965812 ACM-75343 | AFX requests for account creation fulfillment did not succeed due to "no signature of method" errors on the SOAP webservice connector caused by an encrypted password. |
SF-1030498 ACM-79568 | The SAP AFX Connector did not decrypt passwords when creating an account, preventing login with the password assigned. |
SF-1045422 ACM-79915 | The Lieberman EDC did not save the value for the Domain Name parameter. |
SF-927034 ACM-73176 | Users with multiple accounts in the same Active Directory database could not sync their passwords. |
SF-807227 ACM-64072 | The Oracle AFX connector failed when a password contained the $ special character. |
Issue | Description |
---|---|
SF-990118 ACM-76648 | The PV_USERS view did not update with new custom user attributes. |
SF-942744 ACM-73716 | Some custom attribute properties, such as "In Detail," "In Popup," and "In Table" risked reverting to their default values because they did not copy to an exported file. |
SF-850054 ACM-70797 | Custom attribute values for an application on the Summary page did not appear after uploading a customer strings file. |
Issue | Description |
---|---|
SF-871409 ACM-70140 | The My Requests dashboard displayed incorrect values for All Requests, Pending, and Completed. |
SF-961911 ACM-74697 | When the custom attribute ForcePageCleanup was used, "Request could not be handled" errors appeared when switching pages in the UI. |
Issue | Description |
---|---|
SF-903491 ACM-71396 | When a single expiration date for an account was collected in an unsupported format, the Active Directory collections failed. |
SF-829704 ACM-66345 | When an Active Directory account collection contained an attribute with a date value in an unsupported format, the entire collection failed. |
SF-907379 ACM-71714 | After enabling the Complete Manual Activity Before Collection feature, duplicate user entitlements appeared when the collector collected the added entitlements. |
SF-854003 ACM-70365 | When unifying multiple IDCs, some attributes are not populated. |
SF-944541 ACM-73810 | During collection, some groups could not be created when attribute values were null. |
SF-907978 ACM-72044 | After a collection failed, the Last Collection Date displayed the date of the last successful collection, but the Last Collection Status flag displayed the status of the most recent collection, regardless of its success. This could result in the Last Collection Date displaying the date of a successful collection, while displaying a red (failure) flag to indicate a more recent unsuccessful run. |
SF-914637 ACM-71877 | After upgrading, indirect processing failed due to duplicate entries of manually mapped accounts in the T_CE_EXPLICIT_RELATIONS table. |
SF-874496 ACM-69828 | Pagination was not working on the Attribute Synchronization page. |
SF-968405 ACM-75062 | When applying entitlements to a group and finding either sub-group members or groups that are entitlements in Collected Global Roles, group resolution was incorrectly case-sensitive. |
SF-948261 ACM-73932 | Identity collector could fail when USER_ID is used in a Unification Join. |
SF-955199 ACM-74460 | Indirect Relationship processing did not reliably succeed because of Oracle error ORA-30926. |
SF-954489 ACM-74783 | A custom user-type attribute of a business source could get resolved to a terminated user if the custom attribute value did not distinguish the active or terminated user status. |
SF-729636 ACM-57408 | The MAEDC did not reject references to local applications. |
SF-976294 ACM-75655 | Indirect relationship processing of account changes for an ADC had performance issues and did not succeed when processing new account relationships. |
SF-819318 ACM-65066 | The collector did not allow edits because one of the collection data run tasks showed “in progress,” but no collection was actually happening. |
SF-910243 ACM-71796 | When a moved column value was too large for the new field, indirect relationship Processing for the Data Access Collector did not succeed due to error ORA-12899. |
SF-993679 ACM-76572 | A data type difference between two tables caused IDC Collector to not successfully collect due to ORA-01722: invalid number. |
SF-985280 ACM-75977 | A Change Verification job ran a long time for the Attribute Synchronization watches. |
SF-964401 ACM-74754 | The "Collect Identity" dialog box for selecting only non-mandatory collectors incorrectly implied that unification would run after collection. |
SF-945246 ACM-74003 | Collector configuration could not be modified, even when collection was not actively running. |
SF-996452 ACM-76856 | Identity unification did not succeed because duplicate users caused unstable rows in the source tables. |
SF-999529 ACM-77260 | The group owner had to be processed again in later collections after a group collection did not resolve group owner values to a user. |
SF-939467 ACM-73665 | A collector may not finish processing due to error "java.lang.ArithmeticException: / by zero" when one of its internal processing files was between 8192 and 8195 bytes in size. |
SF-991460 ACM-76508 | Collected IDC attributes were not being properly applied to the unified user. |
SF-853028 ACM-68135 | The entitlement collector, when using a MySQL database as a source, did not correctly collect the approle memberships and entitlement relationships. |
SF-1025190 ACM-78293 | The application metadata collector did not successfully run on a database with a large history of data runs. |
SF-985551 ACM-76498 | During IDC processing, new users were sometimes not properly processed into the table T_RAW_USER, and this caused missing unified user attributes. |
SF-831492 ACM-66204 | Collected user accounts mapped to unique identity attributes, such as email address, were not unmapped and orphaned when the value of the identity attributes changed. |
SF-758832 ACM-62291 | When the truncate data option is selected, strings with multi-byte data are not properly parsed. |
ACM-78555 | Benign errors stating "unable to find an attribute length" displayed in the logs when running collections. |
SF-906377 ACM-77158 | In some cases, users moved from lower priority IDC to higher priority IDC (and vice versa) created duplicate identities in the data. |
SF-944339 ACM-73752 | When importing a user account mapping for an orphan account, the new mapping was not reflected in the Total Orphan count in the application’s General tab. |
SF-1044348 ACM-80237 | Unification did not complete due to duplicate entries that caused unstable rows in the source tables. |
SF-1027126 ACM-78580 | The ADC occasionally performed poorly in runtime when validating data on step 2 of pre-processing. |
SF-1073461 ACM-81946 | User access table could not show entitlements of manually mapped accounts. |
SF-628040 ACM-54093 | Collection of AD date-time attribute values did not properly convert to the Aveksa server time zone. |
SF-1018130 ACM-79114 | User type attributes did not correctly display the User name, but showed the ID instead. |
SF-1083500 ACM-82456 | Excessive memory usage during RDC processing caused the Oracle error "ORA-04030: out of process memory”. |
SF-1072789 ACM-81847 | After an upgrade, an Oracle error for an oversized column occurred when running the ADC and calculating relationship changes. |
SF-746902 ACM-58736 | The long business description of an application did not show on the editing screen after it was collected. |
SF-1055180 ACM-80332 | Unification performance issues occurred in an IDC hierarchy with multiple joins. |
SF-1077479 ACM-83014 | Unification duplicated users with new records and terminated the original users when users moved from one IDC to another. |
SF-1058100 ACM-80563 | When a user was moved from one IDC to another, unification terminated the original user and created a duplicate user. |
Issue | Description |
---|---|
SF-955928 ACM-74779 | Users with both monitor and reviewer roles lost review items after reassignment from reviewer to monitor. |
Issue | Description |
---|---|
SF-889066 ACM-71028 | During the merge users step of the unification process, performance was degraded. |
SF-668203 ACM-53477 | The fulfillment_phase_start_date and approval_phase_completed_date columns in the CHANGE_REQUEST public schema were not populated correctly until the request was completed. |
SF-856272 ACM-68175 | After clicking the Add Members button in a role, the Suggested Members view took over 20 minutes to load the list of users. |
SF-902331 ACM-72071 | Performance issues occurred when attempting to load entitlement records for a change request form. |
SF-816551 ACM-68878 | The Aveksa Statistics Report incorrectly reported the system hostname and IP when the remote database was updated with a database dump from another machine. |
SF-968303 ACM-75048 | Exporting the activity table could cause "Out of Memory" errors when there was a large amount of activity data. |
SF-629019 ACM-72836 | If columns for user data such as the first or last name were used, a user accounts table may not have displayed properly after an upgrade to 7.0.1 or later. |
SF-924000 ACM-74184 | File import data filtering enhancement. |
SF-752469 ACM-58925 | Backup Jobs scheduled through the UI would stay in-progress and not complete. |
SF-795053 ACM-55401 | The Aveksa Statistics Report did not report the correct sizes in the internal table summary. |
SF-977818 ACM-75607 | The V_DC_LATEST_FAILED_RUN view did not include collections that failed on circuit-breaker. |
SF-1082570 ACM-82474 | Exports through either the command line or the user interface failed if the process was previously interrupted and then started again. |
Issue | Description |
---|---|
SF-864475 ACM-69179 | Business descriptions for groups were deleted by the system during post-collection processing. |
SF-881726 ACM-70178 | Imported group business descriptions disappeared after collection. |
SF-934145 ACM-75847 | The overwrite option to import business descriptions for application roles did not work. |
Issue | Description |
---|---|
SF-865404 ACM-69677 | Emails containing non-ASCII (UTF) character encoding were not sent properly. |
SF-833463 ACM-66241 | When a multi-step review was generated, the SecondStep Review triggered the NewReviewGeneratedEvent twice, resulting in duplicate e-mails. |
SF-846422 ACM-68937 | When the approver node in an access request workflow used Email Reply Processing, an HTML email response could not be parsed correctly. |
SF-950680 ACM-74072 | After a workflow update using the Workflow Editor, activity nodes in the workflow could not send email. |
SF-834136 ACM-69395 | Email nodes in a request workflow, which were not processed within an approval workflow, sent messages with blank role names. |
SF-955052 ACM-73143 | Source edit attempts for workflow email HTML did not consistently work. |
SF-820417 ACM-65032 | When multiple reassignments were done at once to different users with different comments in a review, only one of the comments was included in emails sent to the users. |
SF-922103 ACM-72618 | When using the OptionalComments variable in an email template, approval comments were repeated within the email for each work item in the request. |
SF-988027 ACM-76487 | International characters in HTML data prevented saves of email templates and email nodes. |
SF-977178 ACM-75978 | Excessive PasswordResetEvent and PasswordExpirationEvent ERRORs filled the aveksaServer.log file and delayed startup and shutdown. |
SF-1004206 ACM-77308 | Password resets issued by the administrator sometimes incorrectly displayed a 3-character password for the user accounts due to special characters in the view page. |
SF-1010051 ACM-77547 | When the email template AdminErrorNotificationMail is modified, that template could not populate the variable fields in the body when sending the admin Error email. |
SF-932643 ACM-73930 | Email events generating emails in a non-English could not change the language of the hyperlink text from English. |
SF-1014915 ACM-77735 | An encoded approval response was sent to a change request email approval. |
Issue | Description |
---|---|
SF-832386 ACM-70244 | Installer and uninstaller removed Aveksa_System.cfg, which rendered the staging folder unusable for reinstallation. |
SF-888171 ACM-72528 | ITIM Agent 7.0.1 did not start after installation due to a Java class error. |
SF-995380 ACM-76587 | Could not complete the migration to version 7.0.2 Patch 1 when Oracle 12c database compatibility is set to a value lower than 12.1. |
SF-872354 ACM-69405 | During a new installation, if the Oracle UID, oinstall GID, or both are not the default value of 500, the install script performs chown -R /tmp/Aveksa/staging to oracle:oinstall, regardless of the current ownership. |
SF-1045387 ACM-79591 | An XML parsing error occurred in UI settings data for a given user when applying a patch. |
SF-1052918 ACM-81060 | The Oracle error ORA-01439 stopped initialization due to custom attributes with incorrect data types. |
SF-1078101 ACM-81325 | The patch build number did not update after applying a patch, which caused patch processing to reoccur at startup. |
SF-970037 ACM-76001 | Duplicate files in aveksa.ear caused errors when deployed. |
SF-942673 ACM-73935 | The installation or upgrade process would get stuck when one or more required install packages were missing. |
Issue | Description |
---|---|
SF-895722 ACM-71558 | The Sample Date form displayed "NaN" in some fields when the browser language was set to a non-English language. |
Issue | Description |
---|---|
SF-1011478 ACM-77437 | Large amounts of workflow data in gigabytes risked a server time-out that disrupted a workflow import task. |
SF-932143 ACM-73177 | Importing incomplete export files of custom user attributes caused errors that affected creating new custom user attributes and running identity account collections. |
Issue | Description |
---|---|
SF-950767 ACM-74441 | The custom user attribute SUPERVISOR_NAME conflicted with an existing, identical attribute during a schema migration. |
SF-976839 ACM-75848 | During migration, the file ACM-60520.sql was running for several hours. |
SF-974378 ACM-76009 | An upgrade from 7.0.1 p2 to 7.0.1 p3 caused error “ORA-30926: unable to get a stable set of rows in the source tables” while executing the script database/migration/migrateReviewData.sql. |
SF-974794 ACM-75390 | Database migration to 7.0+, when applying the ACM-61839.sql patch, did not succeed due to Oracle error ORA-30926 because groups with duplicate names are no longer allowed when collected for the same application by different collectors. |
SF-904759 ACM-71406 | The migration screen did not clarify that the build versions shown refer to the database schema versions. |
SF-897425 ACM-71062 | A null pointer exception error could occur while viewing the migration webpage after clicking the “Follow Output” link. |
SF-1098141 ACM-83172 | Benign Oracle error ORA-06502 appeared when upgrading from an earlier release. |
Issue | Description |
---|---|
SF-873800 ACM-74080 | In a RedHat environment with a remote database, users experienced slow user interface performance when updating challenge questions. |
SF-929698 ACM-73096 | Password policy was failing when the hyphen (-) character was included in the list of minimum required characters. |
SF-942864 ACM-74782 | Resetting a password using the Forget my Password link incorrectly sent daily reminders to the user, forcing the user to reset the new password again. |
SF-1031229 ACM-79103 | Password challenge questions allowed duplicate responses because they used to be case-sensitive. |
SF-1067876 ACM-81469 | A typo appeared in an error message.
|
SF-1039240 ACM-79546 | A Windows Registry Notification Packages change for AD Password Capture tool caused a windows crash on a reboot. |
SF-924320 ACM-73375 | The View Password URL could not be correctly configured through the User Interface. |
Issue | Description |
---|---|
SF-981041 ACM-75731 | The scheduled report sent an empty report when using SQL parameters in the query and choosing CSV attachment types. |
SF-942890 ACM-76875 | ASR report generation from the UI did not succeed because the database hostname could not be resolved. |
SF-922929 ACM-73707 | The Reports tab was missing for users granted permission through the 'Run Report' and 'View Report Results' options on report definitions. |
SF-792552 ACM-63502 | Filter criteria did not save when switching between the Query tab and the Filter Criteria tab. |
SF-978571 ACM-75807 | A generated report did not use a new filter after it was applied. |
SF-997123 ACM-76633 | The Aveksa Statistics Report generation stalled indefinitely after an XML parsing error. |
SF-893547 ACM-71068 | Text in the header row of a report was cropped and unreadable when a large number of columns were present. |
SF-946294 ACM-73894 | Sorting the reports table by the “Last Modified” column resulted in no reports being listed. |
SF-973770 ACM-75652 | A custom scheduled report displayed results without applying requested modifications to the SQL query. |
SF-1050335 ACM-80389 | A user summary table took longer than expected to download from the UI. |
SF-962852 ACM-74715 | When trying to filter by group name in the Group Memberships report, the popup picker showed the list of report definitions instead of group names. |
SF-868021 ACM-70441 | The Global Roles Summary by Owner report erroneously included deleted roles. |
Issue | Description |
---|---|
SF-918967 ACM-72683 | Change request form could not be submitted if it contained required hidden tables. |
SF-970650 ACM-75959 | The values of fields displayed but not enabled on a form did not show after the form was submitted. |
SF-930848 ACM-73141 | Could not access the Account Management form when the browser was configured to use a different default language than the RSA Identity Governance and Lifecycle server. |
SF-984592 ACM-76631 | Non-visual entitlement and account management tables incorrectly handled the shopping cart functionality. |
SF-938295 ACM-73922 | Action buttons on some entitlement screens had minor code performance issues when calculated. |
SF-887157 ACM-70735 | Newly created Provisioning forms did not have user variables available in the list of form fields. |
SF-843527 ACM-67287 | Fields could not be added to a request form using a web service with basic authentication. |
SF-1010503 ACM-79564 | A change request would not reflect a change in previously checked entitlements when using the back button to change the entitlements table filter provided from another component. |
SF-1044516 ACM-79555 | When the user interface was displayed in Portuguese, the date selector did not work. |
SF-1079363 ACM-82831 | The Password Reset form only created change items for passwords and did not process field components that created other kinds of change items. |
Issue | Description |
---|---|
ACM-74064 | When associating a role with a role set, the drop-down menu listed the raw names of the role sets, instead of the display names. |
SF-897929 ACM-71048 | The user interface displayed the Role Set Raw Name, instead of the expected Role Set Name. |
SF-920150 ACM-72275 | A change to a Role in a Role Set could not be reverted. |
SF-965884 ACM-74834 | Performance issues occurred when adding users and entitlements to a Role with active rules. |
SF-928834 ACM-73183 | The Add entitlements button became hidden in unnecessary contexts. |
SF-941379 ACM-73630 | When entitlements were added to roles through the Add Entitlements option in Actions, roles in role sets that restricted available entitlements could be displayed as selected, despite that the option was designed to pick only roles that allowed all Entitlements. |
SF-968444 ACM-75121 | Filters for entitlements and application roles did not function as intended on the second step of a multi-step user review. |
SF-832188 ACM-66415 | Role Discovery is not working in cases where entitlement matching criteria is not specified |
SF-911427 ACM-73976 | Users granted a role to edit entitlements could not remove entitlements. |
SF-987410 ACM-76936 | The role set table under Roles > Role Set showed the wrong values in the custom attribute columns. |
SF-730647 ACM-57064 | Role owner and group owner attributes were not available for selection when viewing all entitlements. |
SF-792647 ACM-65704 | Role status remains in Applied or Applied New State, even after change request is complete. |
SF-856943 ACM-68009 | The exports of a large number of roles timed out before successfully completing the task. |
SF-1007760 ACM-77310 | A user without access to a role's assigned roleset could remove the unseen roleset when editing the role. |
SF-987405 ACM-76935 | The UI incorrectly displayed the raw role name instead of the role name on the Apply Changes and Commit Changes To Roles screens. |
SF-1046008 ACM-80259 | Local Entitlements could be deleted when associated with a role in the "New" state. |
SF-1011117 ACM-77717 | Entitlements could not be added to business roles due to an internal Oracle error. |
SF-1067573 ACM-81344 | Curly braces in the Column IDs table caused errors when sorting users by "Role Out of Constraint". |
Issue | Description |
---|---|
SF-894858 ACM-71265 | The Termination rule did not submit change requests to disable accounts for deleted users. |
SF-916158 ACM-72138 | Rule processing fails when a rule name contains a colon. |
SF-928144 ACM-72795 | Implicit Account Removal was not working as expected. |
SF-945237 ACM-73882 | The Confirm dialog box did not reflect any background data changes and allowed data submission that did not match the confirmation. |
SF-966682 ACM-77504 | Termination rule processing would not detect terminated users if multiple identity collections and unifications were scheduled sequentially through Web Services. |
SF-881484 ACM-70087 | Provisioning termination rule did not generate change requests for Disable Accounts and Revoke Entitlements. |
SF-969733 ACM-75786 | A rule with an assigned remediator or a deleted email recipient caused a UI error when trying to view the rule details. |
SF-1060767 ACM-80583 | The termination rule did not generate the expected change request to disable manually mapped accounts. |
SF-1045601 ACM-79609 | The termination rule incorrectly generated change requests to disable accounts that were not assigned to a user. |
SF-1017682 ACM-80224 | The Attribute Change rule failed with an exception when generating a change request to add a local entitlement. |
SF-1042701 ACM-79712 | The Attribute Change rule did not generate a review when there is an existing review generated by the rule in an active or hold state. |
Issue | Description |
---|---|
SF-923995 ACM-72274 | Multiple sanitization passes were required to fully remove disallowed HTML markup. |
SF-924002 ACM-72278 | The file upload function under Admin > User Interface did not restrict the types of files, potentially allowing unsafe files to be uploaded. |
SF-924000 ACM-72276 | Parameters containing URLs needed additional cross-site scripting filtering mechanisms applied. |
SF-933060 ACM-73252 | Users can bypass disabled buttons in the Diagnostics screen to view, download, and delete ASRs. |
SF-866735 ACM-70721 | After enabling secure session cookie configuration on a WildFly cluster setup, the Enable Secure Session Cookie setting displays No on the Security tab. |
SF-1067853 ACM-81340 | Fixed a security vulnerability specific to target users in the Out Of Office request forms. |
Issue | Description |
---|---|
SF-636368 ACM-52265 | Color coding set as default by all users for rows defined by Control Type: Entitlement Table was lost if the user unchecked the Entitlement Type field in the table options. |
SF-855386 ACM-67958 | When using Internet Explorer 11 with Compatibility View or Enterprise Mode, the violation Revoke and Maintain buttons were disabled. |
SF-1027542 ACM-78552 | Could not log in to version 6.9.1 using Compatibility View in Internet Explorer 11. |
ACM-72791 | Initialization status message contained a typo. |
SF-858359 ACM-69870 | A review definition could not be deleted if either the associated rule had a defined remediator or the email recipient was a deleted user. |
SF-606336 ACM-51005 | The error displayed when a Multi-App Account Collector was not configured to collect the business source reference did not clarify the collector at fault. |
SF-932900 ACM-74704 | A Lotus Notes resource in the Create Directory process described the directory component as an application in error. |
SF-1065726 ACM-81745 | The advanced search did not properly display the unequal sign if the browser or application language was not set to English. |
SF-967960 ACM-76184 | Attributes did not display when searching in the Business Units or Application list. |
Issue | Description |
---|---|
SF-884876 ACM-70610 | When the initial Register User web service was under load, it periodically failed to correctly pass variables into the workflow. |
SF-953127 ACM-74334 | SOAP requests sent to the ServiceNow Cloud through the SOAP web service node using proxy authentication were failing. |
SF-981603 ACM-76590 | A request to create an account from a Web service did not succeed when only one parameter was used. |
SF-925848 ACM-72793 | Benign errors appeared in logging for a service provider that was no longer in use. |