Why Use Delegated Authentication

Opmantek has built its application suite with a few core principles shaping the decision making. Having an Open-Source core is very important, the ability to generate large amounts of data for customers, allowing for customisation to the programs and most relevant to the current article, the ability to integrate with as much as possible.

Integration into custom applications or reporting can be done with our RESTful API; there is an ability to create anything that is required personally. Open-AudIT, for instance, has its API outlined in the community documentation.

A critical feature that often gets overlooked, however, is the ability to create a dashboard for a client or custom group and allow access to view the dashboard without directly logging in to our system. This can be achieved using a generated token that is embedded into a URL that can be followed. The setup process for this can seem initially complex, but there is a detailed article on how to implement this in the community documentation.

This is a useful feature to give users access to the system without giving them direct control, for example, to managers who only want to see that SLAs are met or customers who only need to view their own data.

Using a combination of Delegated Authentication and RBAC, Managed Service Providers have been able to build out customer portals with relatively easy authentication protocols.

To find out more about our products, request a demo where we take you on a live tour of all our solutions.

Related reading: What is Open-AudIT?