| Issue |
Workaround |
|
The activity bar on the MPI login page does not reliably display during the login process and the "Login" button does not change to "Login in Progress" upon activating it.
This does not indicate that login is not progressing.
|
N/A (cosmetic only)
|
|
Calendar on Ad Hoc and TR Reports page defaults to year 4000.
|
Change date to desired value, then use calendar as normal.
|
|
Within the MPI workspace, when accessing reports and then using the browser "Back" button, the resulting page is distorted.
|
Right click mouse button, then select "Refresh".
|
|
System Messages Display window occasionally blanks out (no page to display error) but will work once the window automatically refreshes.
System Messages Display window occasionally stops automatically updating.
|
Right click mouse button, then select "Refresh".
|
|
When choosing "Browse" on the various pages to enter file path information, the dialog box will lock up unless the mouse pointer is moved inside the window prior to any typing.
|
Ensure that mouse pointer is moved inside dialog box prior to data entry.
|
|
Use of Internet Explorer and Windows XP/SP2 with the MPI requires that the pop-up blocker functionality in IE be configured to allow pop-ups from the MOSWEB URLs.
Without this configuration, the Market Status and System Messages windows will not be displayed.
The Participant Technical Reference Manual will be updated on June 10, 2005 to reflect the recommended settings.
|
N/A
|
|
Use of Internet Explorer and Windows XP/SP2 with the MPI will sometimes produce the error message "The page cannot be displayed", when logging in.
|
Use browser "Back" button, re-enter password, and click "Login".
The login will succeed on this second attempt.
|
|
Prior to Release 17.0, under certain conditions, a client digital certificate which has been previously imported into the browser, but has since expired, will successfully roll over and become valid upon MPI login.
With the release of the new MPI code in March 2007 we expect that this issue has been resolved.
The IESO will continue to monitor for this situation.
|
N/A
|
|
Prior to Release 17.0, under certain conditions, certificate keys expire even though the certificate is used regularly.
With the release of the new MPI code in March 2007 we expect that this issue has been resolved.
The IESO will continue to monitor for this situation.
|
Participant must request IESO to recover the certificate.
|
|
For V7 certificates, the error message displayed in the MPI when the private keys have expired is not intuitive.
The message states:
Login failed: The CA certificate is not valid: no chain found for cn=Cybertrust Common Issuer CA 1, ou=Cybertrust Managed Services,o=Cybertrust IdM Test
|
To verify if the digital certificate private keys have expired, enable the Java console in your IE browser.
This can be found under Tools -> Internet Options -> Advanced->Microsoft VM. The use of the Java console will require a restart of your computer to enable it.
The Java console will indicate "KEY_MANAGEMENT_FAILED - An error occurred while retrieving general information from the Security Manager"if your certificate has expired.
|
|
For version 1.5 of the CLS, when 'p12 export' is checked, there is no screen message that the certificate has rolled over.
The message does display correctly when just the EPF file is tested and 'p12 export' is not selected.
In both cases, the EPF (and P12 file) are updated properly - but the 'successful rollover' message only appears if 'p12 export' is not selected.
|
It is recommended that you test your EPF file by first leaving the export P12 box unchecked.
If a rollover notification is received perform another test immediately with the export P12 box checked.
This will update the P12 file for re-import into the browser.
Following the test you should check the modified dates of your P12 and EPF files to be sure that updates have been successful.
|
|
When testing an existing EPF file in CLSv1.5, if the password you enter is incorrect AND does not meet the rules for a strong password, no message is generated to indicate that the password entered is incorrect or "weak".
The password will only be compared to the one set for the EPF file if it meets all the rules for a strong password - in this case, an error message will be generated if the password is incorrect.
|
Ensure that when the EPF password is entered that it meets all of the rules for a strong password so that it can be properly compared to the password stored in the EPF file.
|
|
Rollover of certificates in the Portal is transparent - no message is generated and users do not know that they need to update their P12 File.
The EPF file rollover is transparent but if you are also using the MPI, you need to roll over your P12 file, otherwise it will expire without prior notice.
This situation will not happen very often as it only happens if a user goes into the Portal before going into the MPI when the certificate is ready to rollover. (At this time, only Transmission Rights Auction participants are using their certificates for both the Portal and the MPI.)
|
This situation can be alleviated by checking the EPF and P12 file time stamps on a periodic basis for V7 certificates that are used with both the Portal and MPI.
The time stamps can be compared to the digital certificate start and end dates shown in the certificate details for the certificate imported into the browser
|
|
When using the CLS v1.5, EPF file names must be in mixed case.
They cannot be all lower or upper case.
|
Ensure that EPF file names are in mixed case.
|
Resolution of these issues will be investigated as part of future releases.
About The IESO
