IAM Automation

“Did you remember to export the updated Login journey before leaving on Friday?” This Slack message used to haunt our team. Someone would make changes in dev, forget to export, and by Monday we’d be scratching our heads about what changed. Sound familiar? The fix: wire up Frodo CLI with GitHub Actions and never worry about manual exports again. Here’s exactly how we set it up. Clone the companion repo: IAMDevBox/frodo-cli-cicd-pipelines — production-ready GitHub Actions workflow templates for ForgeRock/PingOne AIC (export, staging deploy, prod deploy with approval gate, multi-env matrix). ...

If you’ve ever spent an afternoon clicking through the ForgeRock admin console to export journeys one by one, or copy-pasted JSON between browser tabs to migrate configurations—you know the pain. I’ve been there, and it’s exactly why Frodo CLI exists. Frodo (ForgeRock DO) is the CLI that ForgeRock should have shipped from day one. It handles PingOne Advanced Identity Cloud, ForgeOps, and classic AM deployments. Once you start using it, you’ll wonder how you ever lived without it. ...