Previous Topic: Fixed Issues in 1.5Next Topic: Third-Party Software Acknowledgments


Fixed Issues in 1.1.2

The following issues are fixed in CA CloudMinder 1.1 SP2.

Support Ticket

Problem Reported

21277334-2

 

The max length of ETGLOBALUSERNAME is 256 characters

21356958-1

An error occurs when loading flows for Forgot Username, Forgot Password, Submit OTP, and Register the Device

21365665-1

User doesn’t get redirected after self-registration

21372274-1

Problem with Advanced Authentication Reset Password Screen

21374033-1

DATETIME format in WebService trust

21374151-1

Incorrect SAML version shown in CloudMinder response

21380133

SLO NullPointerException

21394902-1

Wrong task name for CAMSelfRegistrationWorkflow

21396738-1

Newly created endpoint is not listed in tenant User Console

21396863-1

Tenant environment URL loads slowly

21396988-1

Issue with ACS URL in partnership

21398500-1

Login page doesn't come up

21399204-1

Updating a logo requires an SPS restart

21408309-1

Clicking the link on Forget Username and Forget Password causes 500 error

21420499-1

Inconsistent button style - "Register Now" button

21420645-1

Requested Resource Error

21425298-1

IE security warning appears for "ArcotID PKI with Risk Authentication"

21435133-1

Wrong redirection in Forgotten Password task

21436678-1

Secondary authentication screen does not show SMS or email

21472889-1

User name display incorrect during PIN reset task (truncated)

21473758-1

Insecure content warning

21487520-1

External URL tab redirects to wrong location

CQ 166303

Emails sent to users who use the Forgot My Pin task are sent from cloudminder@ca.com instead of the email address configured in the tenant settings

 

CQ 167200

A user name that contains a blank space or the following special characters causes errors during activation or authentication: % + " & [ \ ] ^ ' { | } < > # , / \r \n * =

CQ 167505

Duplicate links appear on the Home page after restarting the JBoss application server

CQ 168479

An HTTP 500 error occurs when you specify AES-256 as the encryption algorithm for a SAML 2.0 partnership. An error is also written to the FWStrace.log.