SSO integration with Okta failing after update (#3)
#4529 · zendesk · opened 2/18/2026
solvedurgent
Requester
henry.patel@globex.com
Assignee
alex.kumar
Updated
2/15/2026, 3:41:43 PM
Tags
billingenterpriseurgent
Conversation (6 messages)
H
Henry Patel
2/18/2026, 8:57:51 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.
A
alex.kumar
2/18/2026, 9:57:51 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?
H
Henry Patel
2/18/2026, 10:57:51 AM
#3
Tenant: acme.okta.com. Error: 'invalid_client — The client_id is not valid.' We triple-checked the client ID.
A
alex.kumar
2/18/2026, 11:57:51 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.
H
Henry Patel
2/18/2026, 12:57:51 PM
#5
Hotfix is live. Can you try logging in again?
A
alex.kumar
2/18/2026, 1:57:51 PM
#6
Working! All 200 agents are back online. Please add URL-encoding to your setup docs.
CLI Actions
cliaas draft reply --ticket demo-4529 # generate AI reply
cliaas kb suggest --ticket demo-4529 # find relevant KB articles
cliaas triage --limit 1 # AI priority suggestion