Summary and recommendation
Mediaocean supports SCIM provisioning, but only through a specific integration pathway that limits your identity provider options. While the platform accepts SAML SSO from any IdP (Okta, Entra, Google Workspace), SCIM provisioning is exclusively available through OneLogin's connector. This creates a problematic vendor lock-in scenario where your SSO and provisioning must be split across different systems, or you're forced to migrate your entire identity stack to OneLogin just to enable automated user management.
This fragmented approach creates operational complexity and potential security gaps. IT teams must either manually provision users in Mediaocean (defeating the purpose of automated provisioning) or maintain dual identity systems. For organizations standardized on Okta or Entra, this means accepting manual user lifecycle management for a critical advertising operations platform, increasing administrative overhead and compliance risk.
The strategic alternative
Mediaocean gates SCIM behind Custom. Skip the Custom plan upgrade and automate complete outcomes across your stack. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Custom |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ❌ | SSO only |
| Google Workspace | ✓ | JIT only | SAML SSO with just-in-time provisioning |
| OneLogin | ✓ | ✓ | Supported |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Mediaocean accounts manually. Here's what that costs:
The Mediaocean pricing problem
Mediaocean gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Standard | Custom | ||
| Professional | Custom | ||
| Enterprise | Custom |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Standard | Custom | ❌ |
| Professional | Custom | ❌ |
| Enterprise | Custom | ✓ (via OneLogin) |
Note: All Mediaocean pricing is custom quote-based. SCIM provisioning is only available on Enterprise plans and requires coordination with OneLogin's connector system.
What this means in practice
The custom pricing model creates several challenges:
Additional constraints
Summary of challenges
- Mediaocean supports SCIM but only at Custom tier (Custom)
- Google Workspace users get JIT provisioning only, not full SCIM
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What the upgrade actually includes
Mediaocean doesn't sell SCIM à la carte. It's bundled with Enterprise features and requires custom pricing:
The catch: Mediaocean's SCIM is primarily designed to work through OneLogin's connector. While they support SAML SSO with any IdP, the automated provisioning path is limited to organizations using OneLogin as their identity provider.
Stitchflow Insight
If you need enterprise media planning capabilities anyway, the upgrade may make sense. If you just want automated user provisioning with Okta, Entra, or Google Workspace, you're constrained by their OneLogin-centric approach and paying custom enterprise rates for advertising workflow features you may not need. We estimate ~80% of Enterprise features are irrelevant for teams that only need SCIM provisioning.
What IT admins are saying
Community sentiment on Mediaocean's SCIM implementation reveals significant frustration with vendor lock-in and limited IdP support. Common complaints:
- Being locked into OneLogin for user provisioning when already using Okta or Entra
- Having to maintain multiple IdP relationships just for one application
- Custom enterprise pricing with no transparency on SCIM costs
- Limited documentation and support for non-OneLogin environments
We're an Okta shop but had to set up a separate OneLogin instance just for Mediaocean provisioning. It's messy and adds another vendor relationship we don't want.
The fact that they only support SCIM through OneLogin is incredibly limiting. We can do SSO with any SAML provider but provisioning is locked to one vendor.
The recurring theme
SCIM functionality is artificially constrained to a single IdP vendor, forcing organizations into unwanted vendor relationships or manual user management.
The decision
| Your Situation | Recommendation |
|---|---|
| Need SCIM but not on Enterprise tier | Use Stitchflow: avoid custom pricing negotiations |
| Using Entra ID or Google Workspace | Use Stitchflow: no native provisioning support |
| Want provisioning without OneLogin dependency | Use Stitchflow: works with any IdP |
| Already on Enterprise with OneLogin | Use native SCIM: you're paying for it |
| Small team, infrequent user changes | Manual may work: but watch for access creep |
The bottom line
Mediaocean's SCIM support is locked behind custom Enterprise pricing and primarily works through OneLogin, creating barriers for teams using other identity providers. Stitchflow delivers the same provisioning capabilities at a predictable cost regardless of your Mediaocean plan or IdP choice.
Make Mediaocean workflows AI-native
Mediaocean gates SCIM behind Custom. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Custom
Prerequisites
None
Key limitations
- User provisioning primarily via OneLogin
- SSO supported with any SAML IdP
- Custom enterprise pricing
Documentation not available.
Unlock SCIM for
Mediaocean
Mediaocean gates SCIM behind Custom plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.
See how it works
