We’re currently evaluating a solution deployed on Anaplan for our company and we have some questions regarding authorization considering that we’ll be using SAML2 for the authentication part. More specifically,
I'm a functional user, so I'm pretty sure I don't understand your question... but figured I'd chime in to learn.
Here's what I do know:
User settings can be imported and exported via the API in the same way any other Anaplan data can be imported & exported (i.e. via the calling of Anaplan import/export definitions).
With the above in mind, we can accomplish the following via automated (integration) processes:
The only interaction SAML will have (from a security administration standpoint) is authenticating into Anaplan. Once logged into Anaplan, user access within the Anaplan Application itself is defined within Anaplan (not via single sign-on). In this context, I don't think there's any way to influence security otherwise via SAML.
Let's see if we get some other replies.
Thank you Paul.
As it is a technical question, I have just create a ticket to the Anaplan's support.
I'm just following-up on this topic... Did you receive the information from Anaplan Support that you needed?
Functionally speaking Paul is correct. At present, we typically configure Anaplan Modules, Actions, and Processes to inherit changes from a customer's identity management systems. There is a design example on the App Hub.
Please do head over to the Idea Exchange on Community and let us know if this is a feature/capability that would be useful to you.