Pratik Bhatt

Pratik Bhatt

Senior Identity Engineer · Founder, Sangyaa Consulting · Triple-certified Okta SME

Gandhinagar, India

Actions

Pratik Bhatt is a Senior Identity Engineer with 15+ years in enterprise IAM, currently embedded with a UK energy retailer where he built and shipped Okta Genie — a Gemini-powered identity agent on Google Cloud serving ~8,400 users in production.

He is triple-certified by Okta (Consultant, Developer, Workflows Specialist), has delivered 350+ SSO integrations across his career, and maintains an open-source PowerShell automation library for Okta administrators that was peer-reviewed by Okta engineering and is used in 10+ countries.

He was an invited speaker at IIMA Ventures' inaugural Claude Code for Everyone: Ahmedabad Edition (3,000+ registrations for 100 seats). Through Sangyaa Consulting he works on agentic AI for identity operations, and he co-runs an AI practitioner meetup community in Ahmedabad.

Badges

Area of Expertise

  • Arts
  • Information & Communications Technology
  • Region & Country

Topics

  • IAM
  • CIAM
  • IAM Strategy
  • Identity & Access Management (IAM)
  • AI-Enhanced Identity and Access Management (IAM)
  • IAM Procurement
  • IAM Program Management
  • IAM-DevSecOps
  • AI-Agents
  • AI-Assisted Development
  • AI-Powered Solutions

The Integration That Didn't Exist: Bridging Google Chat and Okta with a Gemini Agent

Every enterprise has the same silent tax: someone locked out of their account, waiting on a helpdesk ticket for a password reset that a machine could have done in six seconds.

This session walks through a production AI agent that closed that gap for a UK energy retailer with ~8,400 users — built entirely on Google Cloud, and shipped by a two-person effort inside an existing IAM team.

There was no native Google Chat → Okta integration. We built the bridge ourselves: a Python service on Cloud Run (europe-west2), Vertex AI Gemini Flash for intent resolution, Firestore for conversation state, Pub/Sub and Secret Manager underneath, and a self-hosted static OIDC issuer feeding Workload Identity Federation so the whole thing runs keyless — no long-lived service account keys anywhere.

We'll cover:

1. The architecture, end to end
2. Guardrails for irreversible actions
3. Keyless auth on GCP via a self-hosted OIDC issuer and Workload Identity Federation
4. Observability that survives an audit
5. The honest numbers (What is improves)

Pratik Bhatt

Senior Identity Engineer · Founder, Sangyaa Consulting · Triple-certified Okta SME

Gandhinagar, India

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top