RESTlet and integration authentication readiness

Why it matters

An authentication change can interrupt an otherwise working integration.

First step

List how each integration signs in and ask vendors about their transition plans.

Suggested owner

Integration owner

Who should check?

Integration owners using NLAuth, planning new TBA connections, or creating OAuth authorization-code integrations.

2027.1NLAuth integrations stop, subject to the documented exception; new TBA integrations are restricted.
2027.1PKCE is required for new authorization-code integrations.
2028.2 — tentativeOracle’s target for final TBA end of support, not a fixed deadline.

Check your Oracle account notice before scheduling an update.

Identify exact authentication flows rather than infer them from application names.
Select an appropriate OAuth design and coordinate the external application.
Test permissions, token lifecycle and business transactions before cutover.

Authentication methods and grant types for each integration, with secrets excluded from the inventory.

See the approach

Sources and updates

Authentication release notes ↗Oracle document date: 2026-09-21 · Source checked: 2026-10-20

Preparing for TBA end of support ↗Oracle publication/update date not stated on this page. · Source checked: 2026-11-05

Before the next deadline

Earlier changes to this product

2026-10-17 — Added this guide using existing Oracle documentation.
2026-10-17 — Added the documented SuiteAnalytics Connect ODBC/JDBC exclusion to the tentative final TBA retirement guidance.

Tell us what you need help with.

This form sends us a message. It does not connect to NetSuite or sign you up for marketing emails.