> ## 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.07 - Release Note
Release Date: July 21, 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 enhancements in this release:
### Federate to External OIDC Based IdP Feature
From this release, Connect supports federation to an external or third party OIDC based IdP. In some cases, your organization may have an OIDC based IdP but need to extend the IdP functionality by integrating with Connect. Examples of extended functionality include leveraging Storefront Gateway capabilities (such as purchasing a subscription, refunding, and changing payment method), Custom Data capabilities (such as storing additional user data/attributes to maximize personalization), or other user lifecycle management capabilities.
Connect supports two cases of federation to an external OIDC based IdP:
* **IdP initiated** - IdP starts the OIDC flow against our ULM-ID, which then redirects Connect to the configured external IdP. Since the IdP initiated the flow, Connect returns the code back to the IdP in the callback URL and allows the IdP to perform the post token call.
* **Relying Party (RP) initiated** - RP starts the OIDC flow against our ULM-ID, which then redirects Connect to a configured external IdP. Since the RP started the flow, Connect returns the code back to the RP in the callback URL and allows the RP to perform the post token call.
**Note:** Documentation and Admin console controls to configure federation are coming soon.
Federation to External IdP is an advanced capability. [Contact us](connect@vindicia.com) to learn more and enable this capability for your organization.
### Impersonation and Delegation Feature
From this release, Connect supports impersonation and delegation as described in the OAuth 2.0 Token Exchange [RFC 8693](https://datatracker.ietf.org/doc/html/rfc8693). One of the common use cases implemented is to allow a resource server to make calls to a backend service on behalf of the requesting user. For example, a customer support representative impersonates an end user to perform calls on their behalf.
Impersonation and delegation is an advanced capability. [Contact us](connect@vindicia.com) to learn more and enable this capability for your organization.
### Banned Password Premium Service Feature
Connect now offers a new premium service called **Banned Password**. Once enabled, the premium service checks the current user's password against a database of over five million passwords that are weak, insecure or previously compromised. For example, passwords like 123456 or superman, are not allowed to be used as a password when the service is enabled. This database is managed and maintained by Connect on a regular basis.
Connect already supports a configurable list of 1,500 banned passwords that is available for all organizations. The premium service is an add-on that can be enabled for improved security and password protection.
**Note:** Documentation and Admin console controls to configure the Banned Password Premium Service are coming soon.
[Contact us](connect@vindicia.com) to learn more and to enable this capability for your organization.
### Mobile Country Code in Identity App Enhancement
From this release, the Identity App supports a country code entry when onboarding or authenticating an end user with a mobile number.
### Device Authorization Grant (DAG) - Approval Screen in Identity App Enhancement
The Device Authorization Flow is used to obtain tokens for applications running on a 10 foot/3 meter (10'/3m) devices (such as Apple TV, Smart TV, Set Top Boxes). Connect already supports this flow and recommends (DAG) for these types of devices.
From this release, the Connect Identity App supports approval related screens. When the device requests user activation on their desktop/laptop or smartphone, the device provides the user with a code and request that directs the user to a specific URL and/or to scan a QR code. To complete the activation, the user enters the provided code in the Connect Identity App. Throughout this process the device polls for an access token and continues polling until the user completes the flow or the code expires.
The following images show some examples of the approval related screens used for Device Authorization Grant on a desktop/laptop/smartphone.
### Storefront Gateway - Update Subscription API Enhancement
From this release, the Storefront Gateway Update Subscription API has been enhanced to handle upgrade/downgrade use cases. For example, a user that upgrades from a Basic to Gold package, or a user that replaces SubscriptionX with SubscriptionY. The user initiates an Open API call /subscription/updatePurchaseSubscription to the Storefront Gateway. Once the user's subscription ownership is verifed, the REST API POST /subscription/\{autobillId}/update executes using the new product Id and replaces the user's current subscription.
See the[Storefront Gateway APIs](https://docs.vindicia.com/bundle/Amdocs_Media-Storefront-Gateway/page/index.html) for more details.
## Bug Fixes
The following bugs have been fixed in this release:
| **Summary** | **Description** |
| - | - |
| Incorrect error code when using PLM outbound gateway. | When using the PLM outbound gateway, Connect throws an exception error that is handled by ULM-ID. Connect throws a 400 unauthorized\_device\_id error code, however the Connect regression results showed Connect throwing a 500 server error code instead. The regression issue has been resolved. |
| When account gets terminated, Connect does not remove the entry in the appropriate column. | When an account is terminated, Connect does not remove the entry in the ext\_account\_atr.AccountNumber column. This behavior may result in a duplicate exception error if/when the same account number is reassigned to another mobile number. The issue has been resolved. |
## 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.