Account and User Management Issues Resolved
The following issue involving the management of accounts was resolved in the 2024 R1 release.
| • | Resolved Missing Accounts Issue in End-User Portal |
| • | Dots in Email Address |
| • | Producer Portal Rejecting Email Format Without Top-Level Domain |
| • | View Expiring Entitlements Permission Now Enforced For Users Sharing Accounts |
| • | New Option to Control Entitlements Listed on Map Entitlements Page in End-User Portal |
| • | “Trusted Activation Requests” Page Accessible Only With Adequate Permission |
| • | Restricting Role Type Change |
Resolved Missing Accounts Issue in End-User Portal
In this release, accounts are no longer missing from the Accounts dropdown list in the End-User Portal. The issue of missing accounts occurred if a user was linked to more than one end-customer account that all have the same account name, and the user expired for one of these accounts. In this case none of the accounts for which the user was still active was displayed in the Accounts dropdown list.
The same issue occurred on other pages (for example, Recent Releases, Recent Files Added and Downloads), where it has also been resolved.
Previously, email validation failed when a user was created through the Producer Portal and the email address contained more than one dot. For example, the email address my..name@company.com was not allowed.
In this release, multiple dots are allowed in the email address when creating a user through the Producer Portal.
This fix creates parity in behavior between the Producer Portal and web services when creating a user (see also Special Characters in Email Address).
Producer Portal Rejecting Email Format Without Top-Level Domain
Previously, it was possible to create a user in the Producer Portal with an invalid email address of the format abcd@ef (that is, an email address consisting of a recipient name, @ symbol and domain name but without top-level domain). This invalid email address format is no longer accepted.
Email addresses with the following invalid formats are now rejected:
| • | @domain.com |
| • | name@domain |
| • | @.com |
| • | name@.com |
| • | name@@@domain.com |
| • | name@domain..com |
View Expiring Entitlements Permission Now Enforced For Users Sharing Accounts
Previously, if a user was associated with multiple accounts, and one of the accounts had the View Expiring Entitlements permission, the user could see the expiring entitlements for all accounts.
This has been fixed. In the 2024 R1 release, the user can only see the expiring entitlements for the account that has the View Expiring Entitlements permission.
New Option to Control Entitlements Listed on Map Entitlements Page in End-User Portal
In the End-User Portal, the Map Entitlements page for a device shows all the entitlements of the logged-in user belonging to multiple accounts, irrespective of whether the Skip Account Check configuration option is selected or unselected.
A new configuration option has been introduced which enables producers to specify that the Map Entitlements page should only list entitlements that belong to the owner of the device. The configuration option applies to Producer Portal users and End-User Portal users when they are logged in at the End-User Portal.
The configuration option is called Show entitlements owned by the Device Owner Account (under System > Configure > End-User Portal Setup > Devices Page).
By default, the option is unselected, meaning that all entitlements belonging to all accounts of the logged-in user are displayed (existing behavior).
“Trusted Activation Requests” Page Accessible Only With Adequate Permission
Users who do not have the permission “Trusted Activation Requests” can no longer erroneously access the Trusted Activation Requests page when navigating directly to the page via its URL.
Changing the role type—from Portal to Publisher or from Publisher to Portal—of a role is now only allowed if the role whose type is being changed is not currently assigned to a user.