Frodo CLI

“Should we use Frodo or Amster?” This question comes up in almost every ForgeRock project. The short answer: it depends on your deployment type. The longer answer involves Identity Cloud support, ESV management, and whether you’re willing to deal with Java. Here’s the breakdown to help you decide. The Quick Answer Feature Frodo CLI Amster Platform Support Identity Cloud, ForgeOps, Classic ForgeOps, Classic AM Identity Cloud ✅ Full support ❌ Not supported Installation npm, Homebrew, binary Java-based, bundled with AM Journey Export ✅ With dependencies ✅ Basic export ESV Management ✅ Full support ❌ Not available Script Management ✅ Full support ✅ Full support OAuth2 Management ✅ Full support ✅ Full support Realm Management ✅ Full support ✅ Full support Token Caching ✅ (v2.0+) ✅ Built-in Active Development ✅ Very active ⚠️ Maintenance mode When to Use Frodo ✅ Use Frodo CLI For: 1. PingOne Advanced Identity Cloud (SaaS) ...

Hardcoded API URLs in scripts. Production passwords in environment configs. If you’ve inherited a ForgeRock deployment, you’ve probably seen these anti-patterns. ESVs (Environment Secrets and Variables) are how PingOne Advanced Identity Cloud wants you to handle this—externalize configuration so the same journey works in dev, staging, and prod without code changes. The trick is managing ESVs at scale without losing your mind. Here’s how to do it with Frodo CLI. ...

Ever tried to figure out which version of a script is running in production? Or spent 20 minutes recreating a script you accidentally overwrote in the admin console? Yeah, me too. ForgeRock’s browser-based script editor is fine for quick edits, but it falls apart when you need version history, code review, or deployments across multiple environments. That’s where Frodo CLI comes in—it lets you treat scripts like actual code. The Script Management Problem ForgeRock AM scripts power critical authentication logic: ...

“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. Why Bother with CI/CD for ForgeRock? Manual Process CI/CD with Frodo Export from admin console git push triggers export Copy JSON files manually Automated version control Import one-by-one Batch import with validation No audit trail Full Git history Human errors Consistent, repeatable CI/CD Pipeline Flow: ...

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. ...