What's New in Administration

Release dates

Release summary

Developer Center now supports Portuguese (Brazil) and defaults to Portuguese (Brazil) instead of Portuguese (Portugal) when the default language is set to Portuguese.

Users affected

All users

Action required

None

Roll-Out Dates

Sandbox: Thursday, August 18, 2022

Production:

Enhancements

Restricted Access Tokens

Developer Center now offers the ability to create restricted access tokens that are scoped to specific applications. This provides you with greater control and the means to improve your organization’s approach to security.

Previously, access tokens were exclusively global, meaning they could be used with any developer API in a given environment.

Now, you can create access tokens that work with specific applications’ APIs. When granting access to applications, you can now grant read access to one application while permitting read or write permission for another application.

No action is required following this release. All existing tokens will continue to work with the same level of access.

While not required, it is highly recommended to replace existing coarsely-grained tokens with more narrowly scoped access tokens.

Limiting the scope of your access tokens strengthens your organization’s security posture. It will also positively impact your compliance efforts because it allows you to demonstrate that protected data cannot be exposed to third-party integrations.

A developer working on an integration using a tightly scoped access token can generate significantly less damage (maliciously or accidentally) if they only have access to a subset of the APIs available within your organization’s environment.

Using tightly scoped access tokens also limits the blast radius if one of your tokens is leaked in the wild.

Example:

Let’s say you create a token to grant access to an editorial email newsletter integration and the access token is compromised when a developer accidentally checks the token into GitHub.

If you created an access token that only permits read access to the Content API, an attacker could not use the access token to gain access to your organization’s data within Arc Subscriptions. This safeguard dramatically limits the impact of said breach.

Once created, the scope of a token cannot be adjusted. If you’d like a token with a different scope, create a new token and swap it out.

How to create a restricted access token

Navigate to Developer Center

Click “New Access Token”

Select “Restricted Access” and click “Create Token”

Provide a token description and select the relevant access

Click “Generate Token” and securely store the provided token information.

Token Limit Counter

This release also adds a token counter so that you can see how many tokens you’ve created as well as how many have been created within your organization. You can also see how many more tokens can be created before the cap is reached. The cap is not new but was previously not listed in the UI.

Roll-Out Dates

Enhancements

Content API Integration

The POST /Urls endpoint in Content API is now allowed for all read-only tokens and PageBuilder tokens. For a complete breakdown of the differences between token types, see Types Of Access Tokens.

Search on Token Description

The search box now searches against both the token description and owner email address.

Hotfixes

2020-08-24: Fixed an issue where read-only access tokens could not POST to /content/v4/urls if query parameters were included

Roll-Out Dates

Enhancements

Design Refresh

Developer Center has a new look, with updated fonts, colors and spacing for better accessibility and consistency with Arc design patterns.

PageBuilder Local Development Setup

Developer Center now auto-generates the text needed for you to paste into your .env file when setting up development in PageBuilder Engine.

Token Pagination

You can now page through large numbers of access tokens.

Token Sorting

You can sort tokens by created date, last used date, token type, description or user.

Roll-Out Dates

Enhancements

Developer Center is now available in Korean.

Fixes

Roll-Out Dates

Deploy to All Sandbox and Prod Environments: Thursday, Dec 12, 2018

Introducing Developer Center

Developer Center is a new entry point for developers to begin building integrations and new products on top of the Arc platform. In this initial release, we include a more secure form of access token for individual access to the Arc API.

You may access Developer Center by finding its tile in the Administration section of your Arc dashboard. The tile is currently available to all users who also have access to the Permissions tile, but it can be opened to all members of your organization upon request. Contact Arc XP Customer Support to request the tile be added for more users.

New Features

In developer center, users with appropriate access can provision and revoke their own API access tokens. Each user can have up to 20 tokens, and each organization can have up to 300 tokens.

Administrators with the appropriate permission can also see who created each access token and revoke them individually.

For more information on provisioning, revoking and using the new API access tokens, see Managing access tokens.

How are API Access Tokens Different from Basic Auth Credentials?

Until now, most organizations have accessed the Arc API using Basic Auth Credentials. The new access tokens are a big improvement over the old credentials in a couple of important ways:

What’s Happening to the Basic Auth Credentials?

Basic Auth credentials for all organizations will continue to function as they always have for the immediate future. They will be deactivated sometime in 2019. Expect more details to come on the deprecation timeline in Q1 2019.

In the meantime, we encourage all API users to switch their applications to using the new access tokens as soon as possible to ensure a seamless transition.

Release dates

Release summary

Now, when you select the Allow on all websites check box on a distributor, the system removes any underlying restriction and applies the distributor to all websites. Previously, the system defaulted to the restriction unless you manually removed it.

Users affected

All users

Action required

None

Release dates

Release summary

Arc XP Home now supports Portuguese (Brazil) and defaults to Portuguese (Brazil) instead of Portuguese (Portugal) when the default language is set to Portuguese.

Users affected

All users

Action required

None