In an ideal world, all end user access to Canto Cumulus is controlled via Active Directory. Even better are single sign-on (SSO) integrations as the one mentioned in one of my previous blog posts. But what if …
- All of your external endusers are not part of your internal Active Directory?
- Your Cumulus solution is hosted in the Cloud?
- Your IT team does not want to deal with managing your ever-changing list of external endusers, but also requires you to manage all access through AD?
As you can see in the diagram, internal users are still managed by the IT team of our customer. Their connection to Sites and Web Client is handled by an SSO integration. However, internal Cumulus administrators can use Softerra Adaxes’ web-based “User Manager” to create and manage their external end users in a secondary Active Directory hosted in the cloud. This includes assigning users to Active Directory groups which are mapped to Cumulus application roles. This “User Manager” is completely customizable. This is how we designed the look for our customer’s Cumulus administrators:
Each of these so-called “home page actions” can be defined down to the finest detail: It is for example possible to allow admins to create users in very defined organizational units (OUs) and assign them to a very defined group (or: groups) within very defined OUs, so that they can only grant access or modify parts of the Active Directory they are allowed to. The configuration can be as close or as open as needed.
To a Cumulus administrator, the “Create new user” dialog could appear like this in their browser:
However, in the backend, we (as the solution providers) configured this web-based “User Manager” to be restricted as follows:
If you are interested in a similar solution, please get in touch Nextware Professional Services at contact@nextwaretech.com today.
No comments:
Post a Comment