In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
Anaplan API Requirements:
- Account should be Non-SSO account, that means account type should be native in Anaplan.
- All available authentication mechanism (OAuth/API Keys/Basic/etc.) requires Non-SSO account for Anaplan API execution.
- By saying so, It does not matter what authentication mechanism (OAuth/API Keys/Basic/etc.) you use, if the account type is SSO Anaplan API does not work.
How often is this impacting your users?
Non-Compliance of Non-SSO service accounts
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
- Non-Compliance of service (generic) accounts.
- As per Organizational Security Policy, SaaS native accounts (Non-SSO) are treated as non-compliant accounts and as they might have higher privileges, hence could have higher risk.
- This creates additional operational overhead over admins and integration experts.
What would your ideal solution be? How would it add value to your current experience?
- As a part of compliance all account should be SSO authenticated including service accounts.
- SSO account should be able to execute all the API using any authentication mechanism i.e. OAuth, API keys, Basic etc.
- By saying so authentication mechanism (i.e. OAuth, API keys, Basic etc.) should be independent of account type.
Please include any images to help illustrate your experience.
