← Course Home
Okta Certified Workflows - Specialty · Part I

Building Flows

43% of Part I — the exam's largest section, split across 4 modules.

Building Flows · Module 1

Sub-topic: OAuth Authentication

this deck covers 1 of 2 sub-topics in this module

↑ Module 1 Overview

The Task

"Authenticate your Okta account with Okta Workflows OAuth"

This is the very first thing you do in the Workflows Console — before you build anything. "Authenticate your Okta account before you do anything else in the Workflows Console. You only need to do it once."

The Mechanism

This task requires copying information from the Admin Console into the Workflows Console, so both need to stay open at the same time:

1. In Admin Console: Applications → Applications, select the Okta Workflows OAuth app, open its Sign On tab, and keep that page open.

2. In Admin Console: go to Workflow → Workflows Console, then in the Workflows Console click New Connection.

The Fields

Connection Nickname — display name for your connector list
Domain — your org's domain, without http:// and -admin (e.g. organization-admin.okta.com → organization.okta.com)
Client ID — copied from the Okta Workflows OAuth app
Client Secret — copied from the Okta Workflows OAuth app
Click Create

The Domain field is the one people get wrong: it's the plain org domain, stripped of the protocol and the -admin suffix.

A Related, Separate Concept

Don't confuse this org-level OAuth authentication with basic authentication in Connector Builder — a different, advanced task for people building a custom connector, not connecting to Okta itself.

There, an author defines an Auth Type of Basic with configurable Username/Password field labels, optional Parameters (Text, Password, or Dropdown List type), and optional Config Values that can be static or sourced from a helper flow.

The Angle — What Trips People Up

Watch for this in your own sandbox run:

→ Entering the domain with http:// or the -admin suffix still attached — the field wants the plain org domain only.

→ Treating "authenticate your Okta account" and "Connector Builder basic authentication" as the same step — one authenticates your org to Workflows itself; the other configures how a custom connector authenticates to a third-party service.

One Line To Remember

Authenticate your Okta account once, via New Connection in the Workflows Console, using the Connection Nickname, Domain (no http://, no -admin), Client ID, and Client Secret copied from the Okta Workflows OAuth app's Sign On tab in Admin Console. Connector Builder's Basic auth type is a separate, advanced concept for custom connector authors.

Sources: help.okta.com — Connect your applications (ext-connect-your-apps); Build basic authentication (ext-connectorbuilder-auth-basic)