Original Publishing Date: 2022-10-26 Symptoms In Coudblue Commerce 20.5 and 21.0, change orders can get stuck in the "Waiting for acceptance of the Terms and Conditions" status. Cause This can occur in the following scenarios: After a platform upgrade, when enabling the default order flow, the related account does not accept the Terms and Conditions. After migrating a subscription, when the related service plan is switched, upgraded or downgraded. Resolution For BSS 21.11 and below: To get the change order unstuck, complete the following steps: Download the attached script Run the command /usr/local/bm/tools_py/patcher.py accept_multiple_terms.py Then, according to your instance: For classic deployment, run the script on the PBA node  For CNC deployment, run the script on any bss-worker pod No system restart is required. For BSS 21.12 and above: The script for version 21.12 is under review.

Original Publishing Date: 2022-10-26 In CloudBlue Commerce 21.7, the rules changed on how the next billing date is calculated for a subscription. This means that after the upgrade to 21.7 or later, the next billing date may change for some subscriptions. This change will occur when the next billing order is created for the subscription. When you run the precheck before the upgrade, you can see the list of subscriptions that will have their next billing date updated. If you wish to save the current next billing date for a subscription (for example, for subscriptions with a custom billing date), you need to manually update the next billing date for that subscription. To do that, complete the steps below: Ensure the subscription for which you wish to keep the next billing date is in the list provided by the precheck script. Make sure you have the next billing dates that are used now for those subscriptions before the next daily billing process starts after the upgrade. You can get the current dates in subscription details in your control panel. Right after the upgrade, update the next billing date for those subscriptions where needed. For instructions on how to update the next billing date, refer to this section. Note: Even if the desired next billing date is currently set for the subscription, make the update to re-apply the correct date.

Original Publishing Date: 2022-10-27 Symptoms We get the following errors when trying to change a password and use the system password generator. - The password should have more special characters. - Password is too short. Is it possible to adjust the password generator so it generates password according to the system policies? Cause Two causes are possible: 1. IDP password policy is not applied in password generator widget.  The issue has been fixed in CBC 21.2. Internal ID: #OA-23063  2. It might be that your password policy needs adjustment. Note: Once IDP is enabled it becomes in charge of password policy. Resolution 1. Upgrade your CBC platform to the the latest version or at least to 21.2. 2. Verify that the Minimum password length and Required character types settings are configured correctly in IDP settings: You may find more information about it in our documentation:  https://docs.cloudblue.com/cbc/20.5/premium/content/Identity-Provider/Configuring-a-Password-Policy.htm Note: You can configure a password policy for: Your own users: your direct child reseller or customer account users Child account users: your reseller or customer account users. Both on the same screen.

Original Publishing Date: 2022-10-29 Symptoms We have set some values for these system properties under Settings: - Maximum authentication attempts before locking user = 2 - Failed login attempts checking period (minutes) = 10 However they don't seem to work. Even if we input incorrect password 3 times within 10 minutes, they user does not get locked out. Cause IDP is enabled and the above behavior is controlled by its settings: Identity Service > Brute-force Protection >  - Period for failed login tracking (minutes) - User lockout threshold (attempts)  - User lockout period (minutes)  Example: You may find more information about it in our documentation: https://docs.cloudblue.com/cbc/20.5/premium/content/Identity-Provider/Configuring-Brute-Force-Attack-Protection.htm   Note: Even if a user is locked, you might still be getting an "Invalid username or password." error. Quote from https://www.keycloak.org/docs/latest/server_admin/ : This message is the same error message as the message displayed for an invalid username or invalid password to ensure the attacker is unaware the account is disabled.  Brute-force protection settings can be pronounced not working only if a user can still successfully log in to CP after 10 unsuccessful attempts made within a 10 minutes period (provided your settings are as in the above example). Resolution Make sure that IDP settings satisfy your requirements. Make sure you understand the definition of "locked", see Note above.

Original Publishing Date: 2022-11-02 Symptoms Vendor Google Inc reject a purchase request PR-XXXX-XXXX-XXX-001 in CB connect side with the following statement: The purchase request PR-XXXX-XXXX-XXX-001 has not been completed. The vendor has rejected the request with following reason: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Message from the Vendor: GOOG_000: CONDITION_NOT_MET: The resold Test Customer that you are trying to add to your Reseller Developer Customer does not follow the correct domain naming convention. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Cause On the provisioning parameters the key domain looks like: {key=domain, value=akshay.cloudtest.store} The domain format should be the following: "goog-test.your_sub_domain_for_test.domain.tld" and "your_sub_domain_for_test" cannot contains "test" or "goog".   Resolution However we do not have any information if this format is still accepted by google or not. Therefore, please check with Google support's themselves on the format of accepted domain name for test environment. Once you've received the correct format, you will need to create new order, as the previous order will not be able to be completed as we cannot modify the provisioning parameters, which means the domain name will always be incorrect for the previous subscription.

Original Publishing Date: 2022-11-11 Symptoms Sales order for domains fails with the following error after stuck in "Provisioning in Progress" for some time: Service Creation Timeout Exceeded Service Creation Started On the Sales Order's Provisioning Order service Props, domain status is "Acquiring Name Server" and Last Operation Status is "Name Server not acquired". On OA side, there is an update nameserver task that is in failed status with the following error in the execution log: 2022-11-04 07:51:38,525 DEBUG [task:4517048:50 task:4517048:50 Thread-49-(ActiveMQ-client-global-threads)] c.p.p.s.d.e.DnsPluginManagerBean got success zone update result: DnsZoneChangeResult{changeType=ADD, changeId='1666180798546:0000000173', zoneId=11250, nameservers=null, status=SUCCESS, resultMessage='null'} 2022-11-04 07:51:38,527 ERROR [task:4517048:50 task:4517048:50 Thread-49-(ActiveMQ-client-global-threads)] c.p.p.s.j.a.JobBase task 4517048 completed with exception:  javax.ejb.EJBException: java.lang.IllegalStateException: Failed to update nameservers for newly added zone using returned data from DNS service #19: null Checking the related domain in the error log, it will show that the related domain is currently on External Hosting: Cause Bug #OA-29286 where DNS update failing after DNS hosting was switched to External just after creation Resolution For workaround, please change the affected domain's Hosting type to Internal, then re-run the failed update nameserver task. Wait for the task to complete before changing the Hosting type back to External.

Original Publishing Date: 2022-11-15 Question Let's suppose that user is locked using the IdP module. If user is locked, we need to understand where can we check the status and how do we unlock the user, without waiting for the specified timeframe? Answer Log in to the Keycloak administration panel using the instructions from  https://docs.cloudblue.com/cbc/20.5/premium/content/Identity-Provider/Accessing-the-Keycloak-Administration-Panel.htm?Highlight=keycloak Note: Check documentation page for your platform version. If the password is already set, for CBC 20.5 the steps are: ===================================================================== Log in to the Keycloak administration panel using the following URL: https:///auth/admin, for example: https://cidbe.brndff4f8cdb-f6d6cf.aqa.int.zone/auth/admin with the credentials: admin/. ===================================================================== If you forgot the password, you may get it from the Management Node with: # helm get values idp-backend | grep keyc Once logged in: 1. Select the needed realm (the ID of the realm should match the ID of the corresponding brand in CBC) in the top-left corner. 2. Go to Users and search for the needed user (e.g. using its login) 3. Click on the found user. If it is locked, you will see a button to unlock it: Note: You may also unlock all users that are temporarily locked by pressing Unlock users button: If you have more questions, you may try to find answers at the general Keycloak documentation page - https://www.keycloak.org/docs/latest/server_admin/

Original Publishing Date: 2022-11-17 Symptoms Billing Order was generated for a Connect based or PAYG subscription without SKU. Cause 1. Ensure that this is not due to: https://cbportal.freshservice.com/support/solutions/articles/23000098242. 2. Verify that the subscription is rated by VRDM (i.e. not switched to Rating Engine yet, the affected subscriptions charges exist in Logs > Vendor Rated Data). If so, unfortunately, VRDM component cannot assign SKU to charges that were imported from external systems (in this case - from Connect). There is an existing feature request to implement such functionality - #PFR-4355 - Ability to assign SKU to charges imported via VRD Manager. Resolution At the moment, there are no available workaround available. A feature to support SKU for PAYG products will be implemented in scope of feature request #PFR-4355, please contact Technical Account Manager, to know the status of this request.

Original Publishing Date:  2022-11-30 Official documentation for End of life versions: Odin Automation 5.5 Odin Automation 6.0 Odin Automation 7.0 Odin Automation 7.1 Odin Automation 7.2 Odin Automation 7.3 Odin Automation 7.4 Odin Automation 8.0 Odin Automation 8.2 Odin Automation 8.3 CloudBlue Commerce 20.4 Documentation CloudBlue Commerce 20.5 Documentation

Original Publishing Date: 2022-12-15 Symptoms You can get frequent alerts from CloudBlue Commerce monitoring system (for example, Prometheus) similar to these: re_adapter_bill value exceeds threshold (> 5) re_adapter_rate value exceeds threshold (> 5) Cause This happens when processing an order in Rating Engine takes more than 5 seconds, which can happen pretty often. If you get such alerts, you may want to increase the time threshold. Resolution To increase the threshold, complete these steps: From a computer with access to Kubernetes cluster with a monitoring solution deployed, run the following command: $kubectl -n NAMESPACE edit prometheusrule oss   In the opened editor, locate the lines related to the re_adapter_rate and re_adapter_bill alerts. Change the values highlighted in the picture above from 5 to 30 and save the changes. After that, Rating Engine will have more time to process an order and you will get fewer alerts of such a kind. Internal