![]() ![]() In a clustered environment, afx start incorrectly checked for the application running in standalone mode. When the database suddenly went down or was unable to connect to AFX, AFX stopped running until the AFX service was restarted. Output parameters were not resolved when DN suffix mapping was used for account creation. When canceling a change request there was a significant delay.Īccount information on the MAEDC wizard was not displayed as expected to users authorized to edit or administer the MAEDC. Subject of email incorrectly contained HTML markup. ![]() Under Requests > Requests, clicking certain change requests resulted in the following error: “The request could not be handled” due to a bug in the Oracle JDBC driver. Pre-processing for unauthorized change detection failed with the ORA-06402: PL/SQL: numeric or value error. When a user is granted the same entitlement through both a role and an account and the account is deleted from the user, an error occurs when the role is later deleted from the user. Optimized statements for Change Requests involved with determining missing or extra indirect entitlements. When multiple users were selected, submission variables appeared in only the first change request.Ĭhange requests to remove a user from a group that were generated by a Group review did not complete if the fulfillment workflow was configured to “Create a Job per group.” In a review definition that already had a coverage file that determined the monitors, if the definition was edited to deselect the coverage file option, the earlier coverage file was still saved with the review definition despite being displayed as unselected in the user interface. Multi-step review generation failed when secondary step definitions enabled the user selection option "By selecting supervisors and using their subordinate users.”Ī review with a value for SIGN_OFF_ENABLED other than Y or N caused a server startup failure. ![]() Users were able to schedule reviews and collectors using a past date. The user interface took a long time to load certain tabs in reviews that had large data sets. When a role containing app-roles was deleted in a role review, change items to remove the app-roles were not generated. Review generation took more than sixty hours when the review did not use the option “Include group memberships that are entitlements of their assigned global roles.” In review definitions, the "include sub-groups" option was available for selection when no specific groups were selected. ![]() The status for a review was not updated properly upon review completion. When a review item that had been maintained with expiration was revoked, the reviewer was incorrectly set to AveksaAdmin. In the legacy user access review definition, previously selected options for the Replace state were reset when editing the review definition without opening the States tab.ĭuring delegation from the "By Reviewer" tab of reviews, a "Delegated From" user was incorrectly identified as the last reviewer when expanding the tab instead of the actual reviewer from whom items were delegated. Access CertificationĪfter the scheduled run time for a review was changed, the task was duplicated in the memory and the review was run multiple times. #Nups patcher crashes PatchThe following issues were fixed in RSA Identity Governance and Lifecycle version 7.1 Patch 7. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |