SSO integration with Okta failing after update
#4505 · zendesk · opened 2/2/2026
pendingurgent
Requester
david.lee@wayne.co
Assignee
pat.oconnor
Updated
2/18/2026, 9:30:19 AM
Tags
apimobileenterprisebilling
Conversation (6 messages)
D
David Lee
2/2/2026, 2:26:34 AM
#1
After updating our Okta integration to use the new OIDC connector, none of our 200 agents can log in. This is a P1 for us.
P
pat.oconnor
2/2/2026, 3:26:34 AM
#2
This is critical — I'm looping in our integrations team right now. Can you share your Okta tenant URL and the error message you're seeing?
D
David Lee
2/2/2026, 4:26:34 AM
#3
Tenant: acme.okta.com. Error: 'invalid_client — The client_id is not valid.' We triple-checked the client ID.
P
pat.oconnor
2/2/2026, 5:26:34 AM
#4
Our integrations engineer found it — the new OIDC connector requires the client ID to be URL-encoded when it contains special characters. Your client ID has a '+' character. We're pushing a hotfix that handles this automatically. ETA 30 minutes.
D
David Lee
2/2/2026, 6:26:34 AM
#5
Hotfix is live. Can you try logging in again?
P
pat.oconnor
2/2/2026, 7:26:34 AM
#6
Working! All 200 agents are back online. Please add URL-encoding to your setup docs.
CLI Actions
cliaas draft reply --ticket demo-4505 # generate AI reply
cliaas kb suggest --ticket demo-4505 # find relevant KB articles
cliaas triage --limit 1 # AI priority suggestion