# Feature Request: Support JWT Authentication for N‑able N‑central Extension (Surface Command) **URL:** \ **Category:** Connectors\ **Tags:** plugin-requests\ **Created:** [March 18, 2026, 10:23am UTC](https://discuss.rapid7.com/t/feature-request-support-jwt-authentication-for-n-able-n-central-extension-surface-command/57120 "2026-03-18T10:23:06Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![bh1](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/b/f17d59/32.png) [@bh1](https://discuss.rapid7.com/u/bh1)\ **Post date:** [March 18, 2026, 10:23am UTC](https://discuss.rapid7.com/t/feature-request-support-jwt-authentication-for-n-able-n-central-extension-surface-command/57120/1 "2026-03-18T10:23:06Z")
**Extension:** N‑able N‑central **Use case:** Surface Command / InsightConnect ingestion **Extension page:** [Rapid7 Extensions](https://extensions.rapid7.com/extension/nable_ncentral_app) **Category:** Extensions / Surface Command ### Summary We are currently unable to use the **N‑able N‑central extension** with accounts that have **MFA enabled** , as the extension requires **username/password authentication**. This blocks integration in environments where MFA is enforced (which is increasingly non‑negotiable). N‑central **already supports JSON Web Token (JWT) authentication** for API access, including API‑only users. We are therefore requesting that the Rapid7 N‑central extension be enhanced to support **JWT‑based authentication** instead of (or in addition to) username/password. ### Current Issue - The N‑central extension authenticates using **username + password** - This **fails when MFA is enabled** on the account - Disabling MFA for service accounts is not acceptable from a security or audit perspective - This prevents use of the extension in security‑mature environments ### Supporting Documentation N‑able explicitly documents JWT authentication for N‑central API access, including: - API‑only users - Username + JWT or JWT‑only authentication - Role‑based permissions tied to the token Relevant documentation: - N‑central JWT / role‑based permissions: [https://documentation.n-able.com/N-central/userguide/Content/User\_Management/Role%20Based%20Permissions/role\_based\_permissions\_JSON\_webtoken.htm](https://documentation.n-able.com/N-central/userguide/Content/User_Management/Role%20Based%20Permissions/role_based_permissions_JSON_webtoken.htm) [[documentat...n-able.com]](https://documentation.n-able.com/N-central/CMMC/userguide/Content/User_Management/Role%20Based%20Permissions/role_based_permissions_JSON_webtoken.htm) - N‑central REST API authentication using JWT: [https://developer.n-able.com/n-central/docs/managing-authentication](https://developer.n-able.com/n-central/docs/managing-authentication) [[developer.n-able.com]](https://developer.n-able.com/n-central/docs/managing-authentication) This is a **first‑class, supported authentication mechanism** in N‑central and is specifically designed for automation and integrations. ### Requested Enhancement Update the **N‑able N‑central extension** to support: - Authentication via **JSON Web Token (JWT)** for API access - Ideally via an **API‑only user** - Either as: ### Benefits - Enables use of the extension **without weakening MFA controls** - Aligns with N‑able’s documented best practices - Improves security posture and audit defensibility - Removes the need for insecure workarounds (e.g. MFA exceptions) ### Impact Without this change, organisations enforcing MFA are effectively **blocked from using the N‑central → Surface Command integration** , despite both platforms supporting secure API‑based access. ---
**Author:** ![jee\_chung](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/j/d9b06d/32.png) [@jee\_chung](https://discuss.rapid7.com/u/jee_chung)\ **Post date:** [March 18, 2026, 1:30pm UTC](https://discuss.rapid7.com/t/feature-request-support-jwt-authentication-for-n-able-n-central-extension-surface-command/57120/2 "2026-03-18T13:30:59Z")
Ben, thank you for this post. I’ve booked an internal RFE ticket for the requested change. If you don’t mind, please book an “IDEA” support ticket also, so that we can link that request to the internal RFE ticket. ---
**Author:** ![bh1](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/b/f17d59/32.png) [@bh1](https://discuss.rapid7.com/u/bh1)\ **Post date:** [March 18, 2026, 1:50pm UTC](https://discuss.rapid7.com/t/feature-request-support-jwt-authentication-for-n-able-n-central-extension-surface-command/57120/3 "2026-03-18T13:50:48Z")
Done, thanks Jee ---
**Author:** ![jee\_chung](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/j/d9b06d/32.png) [@jee\_chung](https://discuss.rapid7.com/u/jee_chung)\ **Post date:** [July 14, 2026, 1:42pm UTC](https://discuss.rapid7.com/t/feature-request-support-jwt-authentication-for-n-able-n-central-extension-surface-command/57120/4 "2026-07-14T13:42:56Z")
Ben, we have a pre-release version of the N-Central connector. To try this connector, we will need to work with you to install it for you. Please, submit a support ticket mentioning this discussion and request that the support team escalate the ticket to me.