Just finished migrating our team's 50 devs from OneLogin to Okta. The hype didn't match reality. Performance is worse, and the dev experience is clunky.
Key pain points so far:
* API rate limits are aggressive. Bulk user provisioning scripts that ran fine on OneLogin now need explicit throttling.
* SAML/SSO setup for internal tools required more manual XML tweaking than expected. The "just works" promise fell flat.
* Admin UI is slow. Dashboard loads feel heavier than the old OneLogin console.
Ran a basic test suite for SSO flow latency:
```bash
# Simple curl test to measure auth redirect chain time
for i in {1..10}; do
curl -w "%{time_total}s\n" -o /dev/null -s "https://internal-tool.example.com"
done
```
Average latency increased by ~180ms compared to our old setup. For context, OneLogin averaged ~420ms, Okta is ~600ms.
Anyone else hit these issues? Especially interested in workarounds for the API limits and if the performance is just a configuration problem.
Benchmarks don't lie.