Previous Topic: Fixed Issues in 1.52Next Topic: Fixed Issues in 1.5


Fixed Issues in 1.51

The following issues are fixed in CA CloudMinder 1.51.

Support Ticket

Problem Reported

21398571-1

Remove AppLogic warning message from the CA CloudMinder kit installer.

21405244-1

Icons go missing when logging out of Identity Management.

21420488-1

Identity Management button styles are inconsistent.

21423543-1

Issues with Web service and public user accounts.

21424021-1

Exception (tews6.wsdl.lmsException) is generating stubs with Axis.

21459422

Metadata is not updated in IAM CS.

21477905-1

Google Oauth gives the error "Unable t get the attributes for the user" intermittently.

21522100-1

Connector installation fails if a password contains a special character.

21532475-1

CA SiteMinder® authentication for TEWS has issues.

21586286-1

The WCTX parameter is not preserved when using WS-Fed to access SharePoint.

21592346-1

Internet Explorer behaves incorrectly when resizing a screen.

21620829-1

[Connector] Socket Closed #2 message.

21634496

Error message is not displayed when wrong credentials are entered.

21634502

Re-login is denied even when a user submits valid credentials on the second attempt to log in.

21634505

User account is not locked even after three invalid password attempts.

21636087-1

The customer cannot achieve an active partnership running CA CloudMinder, and sees an error in the Administration user interface.

21655098-1

Imported services do not display in the Service Wizard.

21656651

An error occurs without ArcotID PKI application installed.

21668496-1

Policy server upgrade fails with core dump: *** glibc detected *** /opt/CA/siteminder/bin/XPSDDInstall: double free or corruption (fasttop): 0xf7500468.

21716142

Problems with Shell\Wipro partnership: Unable to view and modify.

21730077-1

"User Authentication Details" report does not capture the required data.

N\A

On a slow running machine, the Forgot Username task times out to the Task Pending screen before the username is displayed on the page.

Note: This issue was addressed by creating templates using email policies.