Resolved an issue where SoftLayer_Brand::createObject requests coming in from the API were not creating an associated SoftLayer_Policy_Brand record. This bug resulted in user accounts created under the new brand to be unable to log in to the customer portal.
Corrected an issue on the Bluemix order forms where the order form content appear in a different language based on the www.softlayer.com language cookie. The order forms are set to English until all language translations have been completed.
Increased the space allowed for addresses when making payments via PayPal. The shorter space was causing PayPal transactions to fail when an account used a bunch of unicode characters.
Fixed an issue where users might be immediately logged out after navigating to the order forms due to a non-public API call.
When a user’s password expired, we are no longer automatically sending the password reset email. Instead, the user will be informed that their password has expired and that they need to use the Reset Password link on the login page to change it.
Updated automatically generated customer emails to reflect new branding.
Updated the page title and icon on the control portal compute order forms to reflect IBM Bluemix.
Resolved an issue with the getMappedAccounts method not correctly displaying the accountLinks section of the output.
When any sub-brand is created by a brand master account it now automatically has the brand attribute ALLOW_ACCOUNT_CREATION set to 1.This resolves an issue what required Sales Operations to manually set the ALLOW_ACCOUNT_CREATION to 1 on sub-branded accounts.
Allowed the IAM token service to indicate that 2 factor authentication has been fulfilled in the case it has been performed recently. This will be done by including a flag in IAM token to indicate that 2FA is not needed. This is for the getPortalLoginTokenOpenIdConnect method.
Rolled out code to limit the number of combined manual and scheduled snapshots that are supported on Block and File Storage. Going forward the limit is 50 snapshots per volume. The portal and API will now display a warning if there are 50 snapshots on the system for a particular volume, and the user tries to create the 51st snapshot manually. The scheduled snapshots are auto deleted per retention policy when their limit is reached.