rs.
Résumé
Back to selected work
03 / Developer Identity Sync / 2026

Keeping developer identities in sync.

Replacing a legacy integration with a focused Go service for secure account synchronization.

Cisco · Software Engineer (contractual)Cisco API Console

Related platformThe account synchronization webhook was configured in Cisco API Console.

AT A GLANCE

1,000+developer accounts

My role
Software Engineer
Focus
Backend engineering
Read my contribution

THE SYSTEM AT A GLANCE

How the pieces fit.

  • 01Mashery accounts
  • 02Go synchronization
  • 03Okta identities
  • 04Grafana monitoring
01 / CONTEXT

The problem to work through.

Developer accounts needed to remain synchronized between Mashery and Okta. The integration also had to handle authentication, token renewal, deployment, and monitoring as part of a production platform.

02 / MY CONTRIBUTION

What I worked on.

  1. Replaced a legacy Flogo integration with a custom Go application.
  2. Implemented synchronization for more than 1,000 developer accounts between Mashery and Okta.
  3. Connected the account synchronization workflow to a webhook configured in Cisco API Console.
  4. Added OAuth2/JWT authentication with automatic token refresh, mTLS, and IP whitelisting.
  5. Deployed on OpenShift with Grafana monitoring and VictoriaMetrics.
03 / OUTCOME

What the work made possible.

Moved the integration into a focused Go service with explicit authentication and operational concerns.

Supported the synchronization of more than 1,000 developer accounts.

NEXT CASE STUDY

Turning a few words into a new image.