3.16.2.X Hotfixes

This page containes the description of the hotfixes related to 3.16.2 version

DISCLAIMER

Product Information contained within this document, including technical information and functional specifications, is subject to change without notice. Naviga reserves the right to make any changes to the information in this document at any time without notice. Naviga makes no warranty, representation, or guarantee regarding the suitability of its products and services for any particular purpose.

Please note that all the 3.16.2.X hotfixes are by default included in both the next minor and major versions, which are 3.16.3 and above and 3.17.0, respectively.

If you want the fix to be applied, please input a Salesforce case.

.1

Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.

Note added on June 20th, 2023.

Lite Subscriptions Expiration Data & Status fix

Within Lite Subscriptions, the functionality to edit and update Expiration date from One CSR Portal UI was not working completely. The expiration date was being updated in one of the two dependent tables in the database and subscription status also remained Expired even if updated expiration date was set to a Future Date. This issue has been fixed by introducing new endpoints within One CSR Portal application.

Lite subscriptions: One CSR Portal tab renamed

When a user clicks on ‘Start call’ push button, the first tab displayed contains the selected account information. For Lite subscriptions, this tab name is renamed as ‘Lite Account Information’ to give it more clarity from this release.

Lite subscriptions: Currency field added

A new field Currency is introduced in Lite Account Information tab under Account Details section. By default, the field displays the value of the currency entered by the user/CSR while creating the Subscription through the Subscription Panel Presentations. The field is editable and provides the following options in a drop-down to choose from: 1) Euro 2) US Dollar 3) Swiss Franc and 4) Pound Sterling

The above UI changes and the corresponding functionality works in tandem with the following updates in the API side.

• A new endpoint is created api/startCall/Currencies/{CountryCode} to get the currencies list

• The /Billing/Currencies endpoint from SubscriptionsAPI is called to verify the validity of the currency being sent. Only valid currencies can be sent

• To the Update Subscription API endpoint, the Currency parameter is added

One CSR Portal: Registration search within Subscription

In Subscribe, there are corporate accounts where each account having almost 2000 users registered under it. With the new enhancement, it is possible to search for a specific user within a corporate account.

Within the Digital Tab of Start Call push button, a new section ‘Search Registrations’ is added now. It has three search fields: Login name, First name and Last name along with Clear and Search buttons.

A new column Full name is also added in the result grid which shows the combined value of First name & Last name that brings more clarity.

The CSR can now filter the data of registrations grid by entering the login name (usually email id), by combination of First Name & Last Name, or all of them. The search results will be based on partial or exact match of the names given in the search fields.

When the Search button is clicked without any data being entered in the search fields, the grid displays all data related to active registrations under the subscription, without applying any filters.

One CSR Portal: Subscription Search by First Name or Last Name only

The Subscription Search is enhanced to be able to search with just one search field compared to the prior three search fields. With this new development, it is possible to search for user account(s) by giving either First name and/or Last name in the respective search fields.

This enhancement is enabled by an MG2Control App setting (Client Components Permission) with the key ‘SubscriptionSearchBasedOnFirstAndLastName’. If this key value is set to 1(true), then ‘Search only by First name or only by Last name’ is permitted. Or else, the current behavior follows (i.e, the user should enter value in First name, Last name and Newspaper). By default, the key value is set to 0 (false).

While the key value is 1, if the user attempts to search with fields such as House number, Street or Zip/Postal code that do not work independently, then the following error message will be displayed:

“Either First Name or Last Name or Account number or Phone number or Email or Company name or three other fields are required.”

Configuration Notes:

• Created new App setting key (Support Viewer > Management > App Settings > Setting type - Client Components Permission, App type - SubCon Admin, Key - SubscriptionSearchBasedOnFirstAndLastName)

• When key value is set to 1, it is possible to search with First name and/or Last name. However, a search with only House number, Street or Zipcode will trigger an error message.

• By default, the key is set to 0.

One CSR Portal: User Accounts Search by First Name or Last Name only

Certain clients can have a large number of users and hence it might get difficult to search registrations only by Login Name i.e. Email Id. Hence this new development.

• The User Accounts → Search Module is enhanced with additional search criteria for First Name and Last Name. With this new feature, users can now search for user accounts either by giving First name and/or Last name in the respective fields. The search results will be based on partial or exact match of name given in the search fields with the only requirement being that the initial characters of the search text must match exactly. For instance, a search using the text "HE" will return a match for "HELLO", but not for "LLO".

• A new column ‘Full Name’ is added in the search results grid to provide users with more accurate search outcomes.

• In addition, the "Show only registrations" checkbox is removed from the user interface. The checkbox was previously checked and disabled in all cases, rendering it redundant. However, this change does not affect the backend logic.

The above enhancement is made possible with the following API changes in the backend.

• The SearchUserByEmail endpoint is renamed to SearchUser.

• The APIs are modified to include FirstName and LastName as parameters.

One CSR Portal: Capture Additional Registration Data when creating a New Registration

Certain clients have corporate accounts in which each account can have a large number of registrations under it. The registrations data can be used by the client for their external activities and campaigns but currently the system does not capture enough information to fulfill this purpose. From this release, the Subscribe system is enabled to capture extra information for each user Registration. However, this is an optional function and can be switched on/off with a MG2Control App setting, RegistrationAdditionalData.

When the MG2Control RegistrationAdditionalData is set to true, the following happens:

• When a user clicks Invite / Invite Without Registration, additional fields for Company Name, Position (Job Title), Phone, Address, City, Postal Code, Country are displayed. Data entry to these fields are optional.

• Data entry to these fields are free text except for the Country field, which will be a dropdown. The Country drop-down has the same options as that are available under Lite Account Information tab.

When the MG2Control RegistrationAdditionalData is set to false then the additional fields are hidden.

One CSR Portal: Additional user details available in Profile settings of User account

Once the additional user registration data is captured in the system, it will be available under the Profile settings of User accounts (User accounts > Search > Registration > Profile settings). The additional user data fetched from the database will be editable with a Submit button. This functionality also depends on the value of the MG2Control App setting key, RegistrationAdditionalData.

Configuration Notes: The additional fields will be available under Profile settings only if the key value of RegistrationAdditionalData is set to 1 in MG2Control > App settings.

One CSR Portal: Downloadable CSV Template

From this release, a CSV template file is available for download with extra fields such as Company Name, Position, Phone, Address, City, Postal Code, and Country, along with existing fields. A push button Download CSV Template will be displayed side by side with the Import from CSV button. The headers in the downloaded template are in sequence with the expected import order. This helps the end user to identify the sequence of columns to be maintained while importing the CSV for registration invites.

Clicking Import from CSV captures additional data columns and stores them in the Registration table without impacting existing import behavior. Country field values are validated from Subscribe Country Setup. Error messages are displayed if columns are missing or out of sequence.

Configuration Notes: The Download CSV Template button is displayed only if the MG2Control App setting key ImportRegistrationButton value is 1. The value of RegistrationAdditionalData MG2 Control App setting determines if extra fields are to be included in the template or not. If the value is 1, the template file will have all the extra fields and if the value is 0, the template will have only the default fields (Email, First name, Last name and User Type). When this setting is 1, the additional fields are also saved in the Invitation table at the time the Registration invitation is sent.

One CSR Portal: Append action added for Registration Import from CSV

In the Bulk Invitations Import window, when importing the uploaded file, all existing entries were deleted and replaced with the records in the file. It was difficult to handle the requirement to add a couple of entries to an existing list of over 500 entries. Enhancements have been made to add records to the existing list rather than totally replace the entries.

• The Bulk Invitations Import window now includes the option "Choose an action." By default, the action has been set to "Append." An alert message— “This action will add the new records without deleting the existing ones." for the selected action will be shown at the bottom.

• The "Upload" button that appeared after choosing a file has been replaced with an "Import" button. Only after a file has been chosen for upload will the "Import" button become enabled.

• If a record in the uploaded file matches an existing registration (Pending or Active), the log file generates the message “Record already exists” against the record.

Note: Since records are now appended rather than overwritten, the import limit will be defined by pending invitations rather than the total registration limit.

One CSR Portal: Add Address fields in Lite Account Information

• On the Lite Account Information tab, a new section called "Billing Address" has been added. This section consists the subscriber's Address, City, State, Postal Code, and Country.

  Note: The Country field, which was previously located under the Personal Details section, has now been moved under the Billing Address.

• The information in this section is already filled in based on the information given when the subscription was created. The values can be modified by clicking the Edit button at the bottom of the section.

  Note: All fields in this section are mandatory and cannot be left blank.

One CSR Portal: Change Resend Invitation endpoint

• One CSR Portal now uses the POST /Invitations/{invitationId}/Resend instead of PUT /Invitations/{invitationId} to resend the invitation email.

SubCon Site (Self-Service) - Change Resend Invitation endpoint

• The SubCon Site (Self-Service) now uses POST /Invitations/{invitationId}/Resend instead of PUT /Invitations/{invitationId} to resend the invitation email.

API - Modification in GET/User/{customerRegistractionId}/{type}, GET/User/{type}, and GET/User endpoints

• The above endpoints now include a new output parameter called "metadata" that returns the additional registration details that are added when creating a new registration (see the point above). Note: The metadata can contain any information in JSON format and is not restricted to the registration's additional fields.

API - Modification in POST User (Create User) and PUT User (Update User) endpoints

1. When a user is created using the POST /User endpoint, metadata information can now be added and stored in the database under the Registrations table.

2. When using the PUT /User endpoint to update the user details, the provided data will be used to update the user information in the Registrations table, including the metadata.

API - Modification in POST /Invitations and POST /Invitations/{Id} endpoints

1. When creating an invitation using the POST /Invitations endpoint, metadata information can now be added and stored in the database under the SubscriptionInvitations table.

2. Once the invitation has been accepted, the metadata details in the SubscriptionInvitations table will be copied to the Registrations table.

API - Modification in PUT /Invitations/{Id} endpoint

1. The PUT Invitations endpoint has been modified so that the API can only be used to change information about an invitation that is still pending registration.

2. The API modifies the information of an invitation in the SubscriptionInvitations table with the provided details, including the metadata.

API - New endpoint POST /Invitations/{invitationId}/Resend

• To resend the invitations email, a new endpoint POST /Invitations/{invitationId}/Resend was developed.

API - Modification in GET /Invitations and GET /Invitations/{Id} endpoints

• The above endpoints now include a new output parameter called "metadata" that returns the metadata details that are added when creating an invitation.

API - Modification in PUT /Subscriptions/{subscriptionId}/Address endpoint

1. The above endpoint has been updated so that the Billing and Delivery address details of offline subscribers who don't have a Circ system can now be modified.

2. Except for CircPro, the API modifies the address of the subscription in the repository (Subsvc) and the Lite Account Information tab with the provided details for all clients.

3. If the specified City and State do not match the provided Postal Code, the address will be standardized with Melissa, and the response will return the correct City and State based on the Postal Code. Melissa will fail address standardization if an invalid address is provided, resulting in an error in the response.

Missing First Name and Last name for Registered Users in Profile Settings - fix

When the CSR sends an invite to an end user to register an account or when invites were sent via bulk upload, the first name and last name were entered alongside the email and guest/owner fields. However, after registration, the First Name and Last Name fields were not populated in the user's profile settings in One CSR Portal.

The root cause of this issue was that the first name and last name of an invited user were getting saved only on the Subscriptioninvitations Table and not in the Registration table. This data was not getting stored or introduced in any other scenario of the entire Invitations flow.

To rectify this, we have added an extra step. When a user accepts an invitation, the site calls /Invitations API as always, and the /Invitations API also pass first name and last name information to /Users API (endpoint PUT /User). This results in an update of firstname and lastname in the Registration table (Subsvc DB of a specific client).

Thus, with this new release, the first name and last name fields are now correctly populated in the user's profile settings upon registration.

PayPal Braintree Autorenewal - fix

Paypal via Braintree Renewals have been getting declined in circulation. It was identified that the PaypalBAID parameter while purchasing the subscription on EzPay was not being sent accurately to Circ. The issue has been fixed by passing the appropriate parameter from payment vendor to circulation system.

This particular fix was also merged to 3.16.1.6 and 3.16.1.10

Areas covered:

API, One CSR Portal, SubCon Site (Self-Service)

.2

Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.

Note added on June 20th, 2023.

SubCon Site (Self-Service) - Incorrect Tip Payment processing in CircPro

For CircPro clients, when a signed in subscriber selects an offer and do the bill payment, the tip amount entered in the corresponding field was getting added twice to the subscription amount resulting in a high cost of subscription. This issue has been fixed now.

Subscription Panel - Added client-specific GTM script in layout pug

The client specific GoogleTagManager (GTM) script has been included in the Subscription Panel configuration.

Subscription Panel - User registration after third-party authentication

When a user was trying to buy a subscription after getting registered via a third party authentication system (e.g., a user on newspaper site clicks on a link ePaper-->Auth0-->Subscription Panel), even after the successful authentication by Auth0, the registration was not created in the Subscribe database. This issue has been resolved now.

The fix was also merged to 3.16.0.12 and 3.16.1.5.

API - Seamless flow failure

Within the Seamless presentation flow of Subscription Panel, there was an issue while completing the purchase flow that did not let the user purchase a subscription. The issue has been identified and fixed now.

API - Resend Invite button error

The issue of users getting error messages while clicking on the Resend Invite button under Pending Invites has been resolved.

.3

Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.

Note added on June 20th, 2023.

Activation of users from One CSR Portal

A CSR can now create and directly activate users from the One CSR Portal. When a CSR activates an invited user, a registration will be created for the user with a system-generated password. Additionally, it is possible to notify the newly created user of their username and password via email.

If the CSR attempts to activate a user who already exists in the Subscribe database (typically a registered user with a different subscription), the system will deny the activation and display a notification message.

• The display of the 'Activate' button and the drafting of the notification email can be configured in the Support Viewer using specific configuration settings (StartCallDigitalTabActivateUser, StartCallDigitalTabActivateUserEmailSend, StartCallDigitalTabActivateUserEmailTemplate).

• This feature is currently available only for Auth0 clients. Note added on October 27th, 2023.

Lite Subscriptions - Saving of Unstandardized Addresses

From this release, it is possible for the CSR to re-attempt and save the address in Lite Accounts even if the Melissa standardization of the entered address fails. The application will provide an option to update the unstandardized address only with the user’s consent. The user can consent in a pop-up asking “The address standardization failed. Do you want to retry and save the best available match?”. If the user confirms with a ‘Yes’, then the unstandardized address will be accepted and the success message “Address has been standardized to the best available match & updated“ will be displayed.

Note: The details are updated based on the address returned by Melissa. Hence if a CSR enters a partially incorrect address that Melissa would consider as Standardization failure but would also return a best available match, in this case, the best available match gets updated which could be partially different than what CSR had originally entered.

The UpdateSubscriptionAddress endpoint (PUT /Subscriptions/{subscriptionId}/Address) has now been updated so that address standardization is performed at every call irrespective of the value of the ValidAddress element. If standardization fails and the ValidAddress element value is true, the API will return an error.

The display of the pop-up depends on the value of the MG2 Control App setting key "StandardizationFailedPopup".

Captcha added to Newsletter Unsubscribe Links

reCAPTCHA V2 has now been implemented on requested client sites, ensuring that when a user goes to the site's Newsletter Unsubscribe Links and clicks on any of the unsubscribe options (either "Unsubscribe from this newsletter" or "Unsubscribe from all newsletters"), they must pass captcha verification to complete the unsubscribe request.

The captcha is configurable at client/publication level. This feature can be turned on/off by including or excluding the appropriate code in the configuration file, config.System.

One CSR Portal - Company name search results available on partial search

The GET /Subscriptions endpoint has been updated so that when a client searches for a subscription based on a partial name of the company, all records containing the keyword are returned if the keyword is present in the CompanyName column.

One CSR Portal - Partial search on User Search Screen by checking keywords with Contains logic

The GET /User endpoint has been updated such that the logic for searching for a user is now based on "Contains" rather than "Starts with". Searching for a user with a partial name under the FirstName, LastName, and Login Name fields will now return all records containing the keyword if the keyword is present in the relevant columns.

One CSR Portal - Description correction of the Pending invites grid

The grammatical error in the description of Pending invites grid has been corrected. The word being has been removed from the description of the Pending invites to make it accurate. Now the description for Pending invites grid is read as “These people have not accepted your invite”.

Solicitor Concierge - Timeout error when selecting a team member

The timeout error occurring in SolCon when selecting specific team members has been resolved.

The fix was also merged to 3.16.1.5.

CMS - Getting error message (Error400:) while selecting an Offer available under Presentation Properties V3

The error message "Error400:" that is displayed while selecting DefaultOfferGroupId from the 'Available Offer Groups' in the CMS module's Presentation Properties V3 due to the presence of an excessive number of offers on SolCon has now been resolved.

Subscription Panel - Confirmation page Login button not working for known users

Changes have been made to the Subscription Panel confirmation page such that:

• When creating a subscription for a new user, the user will be directed to the website after the subscription has been successfully purchased.

• Once an existing user's subscription has been successfully purchased, they must authenticate with Auth0 before being taken to the website.

• These changes do not impact clients using SSOR authentication.

Configuration Notes:

• Auth0 should be set up for the user.

• In config.System "AuthCookieDomain" key is mandatory.

The fix was also merged to 3.16.1.5.

Subscription Panel - Special characters related issues

Allow Special Characters in Presentation Fields

Users can now enter:

1. ' , - & / . in the First and Last name fields.

2. All special characters are allowed in the Email field.

3. ' - & / # . in the Card Holder Name field.

4. # - . / \ in the Address Line 1 field.

5. . - # in the Address Line 2 field.

• When purchasing a subscription, CreateSubscriber failed with the error message “Child Event: CREATESUBSCRIBER failed. Error: FirstName field contained invalid characters that were removed. (19) LastName field contained invalid characters that were removed. (19)" when special character “," was used in the cardholder's name field (First Name and Last Name) on the payment page. This issue has now been resolved. The issue has occurred since the comma (,) was not one of the earlier permitted special characters ('- & /.) for the name fields. The name fields now allow the usage of special characters: (' , - & / .).

• When creating a subscription, AddSubscription failed with the error message "The entered payment information was not accepted" when special characters (&/.,') were used in the Cardholder's name field (First Name and Last Name) on the payment page when using Cybersource gateway. This issue has now been resolved.

The fix was also merged to 3.16.1.5.

Self-Service - Users on vacation unable to raise complaints

For NCS Clients, the issue of the user on vacation, who has paused his subscription with a specific restart date, not being able to raise a complaint, has been resolved now.

Note: Please ensure that the Business Rule within the NCS application is set to allow a user to submit a complaint while on vacation.

The fix was also merged to 3.16.1.5.

Self-Service - Stalling of the My Account First Page

For clients using SSOR authentication, the issue of a logged-in user experiencing a prolonged loading time and the failure to open the dashboard or verified account page on the My Account page has been resolved, and the user can now access the page without the need for a refresh.

The fix was also merged to 3.16.1.5.

SolCon - Timeout error while selecting a team member

The timeout error occurring in SolCon when selecting specific team members has been resolved.

The fix was also merged to 3.16.1.5.

.4

Transport Layer Security (TLS) Upgrade to Version 1.2

The CMS Content module has been updated to support Transport Layer Security (TLS) version 1.2. The TLS version can now also be configured from the web.config file, and image uploads can now communicate with the AWS S3 bucket using the TLS 1.2 security protocol.

This update has been made as Amazon will no longer support TLS 1.1 for its S3 bucket.

Note: If the TLS version is not configured in the web.config file, CMS now uses the TLS 1.2 security protocol by default.

This fix was also merged to 2.39.1, 2.39.1.0, 3.15.3.1, 3.15.2.1, 3.16.0.13, 3.16.1.7, and 3.16.3.

Auth0 Client-Specific Custom Configuration for Social Login

Client specific custom configuration for social login has been added to the Subscription Panel config files so that subscribers can authenticate through Auth0 to the client's site using their social media login connections (Facebook, Google, and Apple) based on the respective client's custom configurations. Clients that have not opted for this method of authentication will be able to utilize the default method for subscribers to login to their sites.

Areas covered: Subscription Panel

This fix was also merged to 3.16.1.6

Subscription Panel - Error loading the offer group page

The error “Sorry, the page you requested was not found. See current offers.“ that was displayed when using the input parameter "ofrgp_id" to purchase a subscription in the Subscription Panel has now been resolved. There was an issue with the SolCon GetOffers logic, which has been reworked.

This fix was also merged to 3.16.1.7

Solicitor Concierge - Unable to add Division to a published offer

The user was not able to add a Division to a published offer in SolCon. An error message was displayed during this update. This issue has been resolved.

This fix was also merged to 3.16.1.7

API - Complaints

Previously, in SubCon Site (Self-Service), the GET /Complaints/{subscriptionId}/Problems endpoint was failing because the complaint problem codes retrieved from CircPro were not available in Subsvc, which resulted in an error. This issue has now been resolved.

This fix was also merged to 3.16.1.7

.5

One CSR Portal - Issue with 'Mark as processed' button

The issue with the 'Mark as processed' button in SubCon Admin has been resolved.

This fix is also merged to 3.16.0.14, 3.16.1.8 & 3.16.3.0.

Self-Service - Invalid Logout call on some flows and 500 error by Update user endpoint

The issue of an increased number of 500 and 404 errors found on clients' servers has been successfully resolved. This was an Authentication system-specific issue. For SSOR clients, even if the user was logged out while navigating to the SubCon site, the logout call was triggered and returned a 500 error. For MG2 Auth clients, the wrong login credentials triggered the logout action. After the fix, for SSOR clients, the logout call will be executed with a status 200 and for MG2 Auth clients, there will not be any logout call while entering the bad login credentials.

This fix is also merged to 3.16.1.9 & 3.16.3.0.

Self-Service - Delayed Login for Publications using SSOR Authentication

The issue of publications using SSOR authentication taking too long to load SubCon Sites has been resolved. This delay was primarily because of an additional API call triggered by an internal cookie with an empty value. With the issue resolved, it is now possible to log in to the My Account pages of publications using SSOR authentication without any delays.

This fix is also merged to 3.16.1.3 & 3.16.3.4.

API - Failure of Newstart due to Invalid Email Characters

In the Self-Service Portal, when creating a start with an email address that included the special character "+" (e.g., [e-mail]), the new start failed to create with the error message "Child Event: ADDSUBSCRIPTION failed. Error: EbillEmail field contained invalid characters that were removed." Since the special characters in the Query String Parameter had been removed, the FindAddressOccupant method failed to find the occupants with the specified email address and returned the error "No occupant record found."

The special character ‘+’ has now been encoded in the Query String Parameter when communicating between EventsAPI and CircAPI in the FindAddressOccupant method, so that when entering an email address with the special character "+," new starts will now be created and errors will no longer be displayed.

This fix is also merged to 3.16.3.1.

Seamless Flow updated for Credit Card Edgil Payment Method

In the seamless flow, if the Independent Address component for the payment page has been enabled, users can purchase or subscribe to a subscription with a single click after entering their credit card information. The issue occurs when the credit card details have been validated, the Submit button disappears, and the user is taken directly to the payment options, even if the fields, First and Last names, Phone, and Zip Code, have not been filled. This resulted in the AddSubscription call being triggered with incomplete information. Since the Submit iframe button is from a third-party payment site, it does not validate whether the aforementioned fields have been filled, resulting in no error warnings being displayed.

Changes have been made to allow the submission of incomplete fields if the credit card has already been validated in the seamless flow by introducing a delay time after each keystroke while filling the fields under the independent address component.

A key, "SeamlessInputDelayTime", must be added to the SP Config file with any numerical value. The value indicates the delay time in milliseconds, with the default value set at 1500 milliseconds (1.5 seconds).

For example, after entering the first name, it will wait 1.5 seconds and then call AddSubscription if no additional keystrokes have been detected. When the user starts entering the following fields, such as Last name, phone number, and zip code, the timer is reset after each keystroke, and the AddSubscription call is triggered only after a 1.5-second delay.

This fix is also merged to 3.16.0.14, 3.16.1.9, 3.16.3.1, 3.15.2.4, 3.15.3.5.

Areas Covered

API, Self-Service, Subscription Panel, One CSR Portal

.6

Attention: Enhancement

Self-Service - Auth0 changes to bypass Intelligent Tracking Prevention on Safari

Recent versions of the Safari browser introduced a new feature called Intelligent Tracking Prevention (ITP). ITP is designed to prevent websites from tracking user activity across multiple websites. By default, ITP is active or enabled on the Safari browser. These advancements in user privacy controls of browser adversely impact the user experience by preventing access to third-party cookies. Following this update, the Mac users on Safari browser were experiencing issues while logging into the self-service portal. Auth0 integration was not working on Safari browsers when Intelligent Tracking Prevention was enabled.

To overcome this issue, starting from this release, the Self-Service portal has successfully upgraded the Auth0 SDK from 1.8.0 to 2.1.3. Changes have been made in SS to accommodate Auth0 2.1.3 SDK.

After the enhancement users now have a smooth login process ensuring a better user experience even if the Intelligent Tracking Prevention is enabled on their Safari browsers of Mac systems.

Bug Fixes

API - ApplePay Integration Error

The issue with the Cybersource gateway rejecting payment authorization attempts due to ApplePay integration not sending CountryCode to CyberSource has now been resolved.

SP - User unable to redeem Coupon Codes

The issues with redeeming Coupon Codes (One-time and Multi-use) in the Subscription Panel have now been resolved.

This fix is also merged to 3.16.3.5.

Self-Service - Unable to maintain login state from .com to MyAccount when redirected

Post client upgrade to version 3.16.2.4, the logged-in user from .com site was unable to navigate to the Myaccount page in Self-Service portal in the logged-in state. The user could only login at the self-service portal when the value of cookies/cache was cleared. This critical issue has been resolved now.

This fix is also merged to 3.16.3.6.

Self-Service - Myaccount shows data of logged out user

When a logged-in user navigated to the Myaccount page in the Self-Service portal, they were unable to see their own account information. Instead, the Myaccount page displayed information from the previous logged-out user. This issue has been resolved now.

This fix is also merged to 3.16.3.6.

SolCon - Terms & Conditions exceptions not working

The Terms & Conditions content added under Exceptions (SolCon > Offer Group > Terms & Conditions > Exception) for publications was not displayed correctly wherever the offer was displayed through consumer applications (Subscription Panel and SubCon Site). Instead of the Exception Terms & Conditions content, the original Terms & Conditions content appeared on the checkout page. This issue has been resolved now.

This fix is also merged to 3.16.3.5.

Application Covered:

API, Subscription Panel, Self-Service, SolCon

.7

Attention: Enhancement

SS - Support tab selection on both Auth0 ULP Classic and New

The Identity provider Auth0 has introduced a new Universal login experience for its clients. Starting from this version, Subscribe clients will have access to this new Universal login experience through the Self-Service portal. However, there will be no visual changes for the user.

When a user hits the ‘Login’ button, the Self-Service portal will direct the user to the Sign-in page. Similarly, clicking the 'Register' button will still direct the user to the Sign-up page, as before. For those interested in learning more about the advantages of this new login experience, you may find additional information here: Universal Login Experience (auth0.com)

This enhancement is also merged to 3.16.3.9.

Application Covered:

SubCon Site

.8

This release is in its beta version now.

Attention - Enhancement

Enhanced Sign-In Mechanism of Landing Application

Recently, major browsers have introduced additional security measures and constraints related to third-party cookies, as well as cross-domain data transfer and communication. The latest release of Chrome no longer supports third-party cookies. These were impacting the functioning of the Landing application and user experience negatively. Despite the implementation of workarounds, users were encountering issues in the sign-in flow at times.

Therefore, the sign-in logic for the Landing application has been revised without significantly affecting the existing functionality and behavior. The previous dependency on local storage has been replaced, and a Redis caching approach is now implemented for the users to sign in on the Landing application for accessing consumer applications (SubCon Admin, SolCon & CMS).

• Following the new implementation, users can access any consumer application only through the Landing application.

• If a user has opened different consumer applications on different tabs in a browser, logging out from one application will force the user to log out from the other opened applications as well. The user will regain access to the application only by signing in through the Landing application.

• Page refresh will work as before and have no impact following the redesign.

• Multi-Factor Authentication (MFA) with Okta will also work as intended if the feature is turned ON for the specific client.

• There is no dependency on third-party cookies related to the Landing application, and the landing works perfectly fine on Safari, Firefox, Chrome, and Edge browsers.

• Consumer applications are no longer dependent on Local storage to fetch data.

• The CMS Idle Time functionality, which notifies the user if they have been inactive on a CMS page for an extended duration and provides the option to either continue or exit from the page, is working as before.

For a seamless user experience and as a best practice, please do not disable cookies in your browser.

This fix is also merged to 3.16.0.15, 3.16.1.10, 3.16.3.13 & 3.17.0.3 releases.