Skip to main content
Connect Gcore with a permanent API token to sync Customer Portal users with their two-step verification status, API tokens, DNS zones and CDN resources, and the portal login history, and run access and MFA reviews. Read-only. Data feeds into your Access accounts, Inventory and Changes pages.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists the Customer Portal users of the one Gcore account the token belongs to — the account is implicit in the token. Each row shows the user’s name (or their email address when Gcore reports no name), their email, and the portal groups they belong to as their roles (for example Administrators, or Member when Gcore reports none). Users who have not yet confirmed their invitation, deleted users and reseller principals are left out; API tokens are separate objects and never appear as users. A user the portal marks as inactive is shown as Inactive; everyone else is shown as Active, and each row is stamped with the date of the sync. Gcore does report per-user two-step verification, so the MFA column shows Yes or No, and is blank (a dash) for a user whose record carries no value.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the Customer Portal user roster — names, emails, groups, active state and two-step verification status — which appears on your Access page; the account’s API tokens (name, creation date, expiry, whether it has expired, last use, and the issuing user’s email and role — never the token itself), DNS zones (status, DNSSEC state and record-set count), CDN resources (CNAME, origin group and status), CDN origin groups (origin count) and SSL certificates (issuer and validity — never key material), which appear on your Inventory page; and the portal login history, which appears on your Changes page. Each login arrives as a change that has already happened — status Deployed, titled Portal login by (or Failed portal login by) the user’s email, with the authentication type, IP address and browser user agent in the description, priority Low for a successful login and Medium for a failed one because Gcore attaches no severity to a login event, type login, and Customer Portal as the environment. Up to 1,000 login events are read per sync, in the order Gcore returns them, with no date window. CDN resources, origin groups and certificates appear once the CDN service is activated on the account — until then Gcore answers that the service is stopped and that part of the Inventory page stays empty — and DNS zones appear once the account has one. The API-token list always includes the token used for this connection. Users’ last-login times are not shown on the Access page.It calls these Gcore endpoints on api.gcore.com:
  • /iam/clients/me
  • /iam/users
  • /iam/activity_log/logins
  • /iam/v2/clients/{clientId}/tokens
  • /dns/v2/zones
  • /cdn/resources
  • /cdn/origin_groups
  • /cdn/sslData
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Gcore environment.

​
Troubleshooting

The token is in the legacy $-separated format, which Gcore retired — DSALTA rejects it before any request is made; create a new permanent API token under Profile → API tokens. Or the token’s IAM/CDN role is not Administrators: such a token can authenticate but return no users, and DSALTA treats an empty user list as a rejected connection. The Cloud role selector in the same dialog is a separate role system and does not unlock the user list. A token can never carry a role higher than its creator’s, and a reseller account cannot create API tokens at all.
A token with an expiration date stops the sync on that day without warning; Gcore emails the issuer and the account’s Administrators 7 days and 1 day before. Create a new token with Expiration set to Never expire, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Gcore.
Everything beyond the user roster is read best-effort: a failure on one of those calls leaves that part of the page empty without failing the sync. CDN resources, origin groups and certificates stay empty until CDN is activated in the portal (Get started for free; no card is needed), and DNS zones appear once the account has one. Do not activate Cloud, which asks for a card and adds nothing DSALTA reads. Click Sync from integrations on the Integrations page to retry.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.