Announcements
There are no announcements for this release.Connect Features
This section describes the key updates in this release.Runtime-to-OIDC Token Association to Support DAG-based Service Revocation
The 2020.09 release included support for OAuth 2.0 Device Authorization Grant (DAG) flows (in accordance with RFC 8628). DAG functionality enables users to onboard and authenticate with an associated devices (for example, set-top-box) before they access services through that device. During the onboarding and authentication flow, Connect creates (among other entities) a Runtime entity that represents the device. The system also issues an access token against the device for authentication. As of this release, access tokens are associated directly to the Runtime entity (aka. device) within the MarketONE datastore. This change enables MarketONE tenants to notify MarketONE when an end user’s subscription status changes and, as a result, remove any access to services through the device itself. If the end user’s subscription status changes with the tenant, then the tenant’s back-end system (for example, Billing/Operations Support System, or B/OSS) can send this to MarketONE as a system event. MarketONE then removes any existing tokens from the Runtime, and this prevents any further access to the subscription-based service through the device. MarketONE tenants can leverage the MarketONEPOST /runtime/event API to send updates to MarketONE.
Multi-Factor Authentication - Unregister Notification
Multi-factor Authentication (MFA) enables an end user to register an email address, mobile number, or RFC 6238-compliant third-party application to their MarketONE Connect ID as an MFA option, as an optional extra layer of login security. The User can also unregister these options at their discretion. Amdocs officially released this feature in the 2020.09 release. As of this release, MarketONE now sends a notification message to all of a user’s registered contact channels when the end user unregisters an MFA method from their Connect ID. This provides a clear record of the action to the end user.API Enhancement - Serialize Entity Attributes as JSON Object
MarketONE data model consists of primary entities, and each entity is composed of properties. These resources are returned to client applications through Connect API (for example, aGET /user API returns the currently authenticated user’s corresponding User entity properties and attributes to the client).
Previously, Connect APIs serialize attributes as a list of simple objects with distinct name and value strings. As of this release, entity attributes are now serialized as a proper JSON object.
Process Enhancement - Accept / Decline Process Includes Onboard New User Flow
When an end user opts to share their account or service with another end user (that is, when they opt to associate their Account / Subscription to another User entity), they submit the invitee’s email address or mobile number to the Invite User to Share A/S/F Process. This Process then sends the invitation out to that channel with a Action Token. Once the token is received, this invokes the User Accepts or Declines Invitation Process. As of this release, the User Accepts or Declines Process now provides a proper onboarding flow consistent with the Onboard User with Email/Mobile Process (without needing to end the current Process). This streamlines onboarding for prospective new users, so that invitees can quickly and seamlessly onboard, accept, and gain access to shared accounts and services.Notification and Messaging Enhancements
User friendly messaging updates for:- Email subject lines
- Unregister MFA message body
- Email notification when user is invited to platform
- Notification templates use display names, but if display name does not exist, then a generic greeting is used