> ## Documentation Index > Fetch the complete documentation index at: https://docs.ulm.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # MarketONE Connect 2022.08 - Release Note Release Date: August 25, 2022 ## Announcements The following are MarketONE Connect Announcements: * We are migrating documentation from MarketONE Developer site at [https://developer.m1amdocs.com/documentation/](https://developer.m1amdocs.com/documentation/) to our Knowledge Center at [https://docs.vindicia.com/](https://docs.vindicia.com/). New documentation updates will only be available in the [Knowledge Center](https://docs.vindicia.com/). * We are in the process of updating documentation and UIs to reflect new product names for the following: * IdP UI renamed to Identity app * Admin app renamed to Admin console * Care app renamed to Care console ## Connect Features This section describes the key features in this release: ### Enforce Minimum Multi-Factor Authentication (MFA) Limit From this release, in order to achieve multi-factor authentication, the organization can define the minimal number of factors required from a user. This is in addition to the initial email identifier provided for authentication. For example if in addition to the the email identifier , one additional factor is required to meet multi-factor authentication, the user can provide one of the following: mobile number, address, or authentication application. If a user wants to remove an entry of the multi-factor authentication factor, they will first need to add a new entry. A setting was added to define the minimal numbers of factors. By default the minimal number of MFA factors is set to 0, so that multi-factor authentication is not required. The maximum multi-factor authentication factors allowed is 3.As of this release, Connect supports multi-factor authentication (MFA) with a minimum MFA limit setting. This setting defines the minimal number of factors required to complete multi-factor authentication. To achieve multi-factor authentication, the organization defines the minimum number of factors required from a user. This is in addition to the initial email identifier provided for authentication. By default, this setting is set to 0, so that multi-factor authentication is not required. The maximum number of multi-factor authentication factors allowed is 3. For example, by setting the MFA minimum limit to 1, in addition to the email identifier provided for authentication, one more factor is required to complete multi-factor authentication. The user can supply one of the following: mobile number, email address, or authentication application. If a user wants to remove one of their multi-factor authentication factors, they will first need to add a new entry. Coming Soon: controllable settings in Admin console to enforce a user to register second factor during onboarding or authentication if a limit of 1 or more is set. ### Onboard and Authenticate with Email and One-Time Password (OTP) From this release, Connect supports user onboarding and authentication with email address and one-time password (OTP). The onboarding flow is as follows: 1. User enters their email address 2. User receives a notification email with an OTP 3. User enters OTP 4. User confirms additional details, if any, such as first name, last name, etc. 5. User is onboarded The authentication flow is as follows: 1. User enters their email address 2. User receives a notification email with an OTP 3. User enters OTP 4. User is authenticated See below image of mobile view demonstrating step 3 where user enters OTP they received via email notification: Mobile view of Sign in page with OTP ### Storefront Gateway Notifications The MarketONE Storefront Gateway API includes a set of APIs that enable clients to perform identity-driven purchase and payment method management operations. The Storefront Gateway is used as part of the communication channel between Connect (user management) and Subscribe (subscription management) to process/fulfill API requests and exchange information. The APIs require a user access token, this is provided to the user by Connect when successfully authenticating. From this release, the Storefront Gateway provides Connect with the following new notifications: | Notification Name | Description | | - | - | | Subscription Created | The user has purchased a new subscription and is notified of the purchase details. | | Subscription Canceled | The user has canceled a subscription and is notified of the cancellation details. | | Subscription Modified | The user has modified a subscription and is notified of the modification details. | As an organization, you can save time/money by leveraging this ready-to-use optional feature without having to build your own notification mechanism for purchase and payment method operations. Similar to all notification templates in Connect, these new notifications are configurable and editable. ## Connect Enhancements This section describes the enhancements in this release: ### Additional Settings in Admin Console From this release the Admin console includes additional settings to manage your instance of Connect. The additional settings are: | Setting Name | Description | | - | - | | Verification required for MFA registration | During registration of the MFA method, the user is prompted to validate the selected channel. | | Time zone | The local system's default time zone. | | Threshold for preventing password reuse | The threshold value (seconds) used for the time interval that must lapse to prevent the reuse of a password from a certain date onward. | | Reusing the current password | Whether the current password can be reused as the new password. | | Prompt captcha | Enable reCAPTCHA. | | Pin length | Required length of the pin code. | | Password expiration period | Sets a time limit in seconds for the password expiration. If the password expires, then the user must change it. | | Passcode min unique chars | Minimum number of unique numerical characters in the user passcode. | | Passcode max consecutive numbers | Maximum allowed consecutive numerical characters in the user passcode. | | Passcode length | Require passcodes to include a minimum number of numerical characters. | | Optional password prompt | During onboarding via social accounts (Google, Facebook, etc.), users are prompted to set a password. | | Number of last passwords can't be reused | Sets the number of previous passwords that can't be reused by the user. | | Max number of users per runtime | Maximum number of Connect users per runtime. **Note:** Runtime represents the software/device on which Connect is being accessed (e.g. web browser, mobile device, firmware in embedded devices). | | Lockout | Enforces lockout if user inputs incorrect password too many times. | | Immediate verification notification for an unverified mobile | Sends an immediate verification notification for an unverified mobile. | | Blocklisted email domains | Prohibited email domains that can't be accessed by the user. | | Allow postponed verification | Allow the user to add their email or mobile number and verify ownership later. | | Allow authentication from an unverified email | Allow the user to login with email, even if the email is unverified. | | 2FA max retry verification | Maximum retries allowed for 2FA verification. | | Coming soon: Documentation for Admin console additional settings. | | ### Device Authorization Grant Support with Access Token Enhancement Forapplications running on a 10 foot/3 meter (10'/3m) device (e.g. Apple TV, Smart TV, Set Top Boxes), use the Device Authorization Grant (DAG) recommended flow to obtain tokens on the device. Connect already supports this flow. Previously, the/oidc/device/verify and /oidc/device/approve APIs required a user to have a valid session based on cookies. From this release, access token support allows a user to have a valid session based on an access token. This secure method is beneficial for applications that prefer to use access tokens instead of cookies. ### Impersonation Request Confirmation Notification Enhancement In 2022.07 release, Connect provided support for impersonation as described in the OAuth 2.0 Token Exchange [RFC 8693](https://datatracker.ietf.org/doc/html/rfc8693). With impersonation, an impersonator sends a notification request to impersonate a user. The user receives a notification to accept/decline the request. From this release, once the user responds to the request, the impersonator receives a notification email/sms confirming the user's choice to accept/decline the request. ## Bug Fixes There are no bug fixes in this release. ## Known Issues There are no known issues in this release. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.