Dev teams working on seemingly unrelated projects (e.g., website, mobile apps, APIs, intranet, etc.) may sooner or later need to communicate with APIs, or their clients need to go through a gateway for authentication. Often, they need to contact the identity team to ask for help, adding time to the project. Developers can set up new OAuth clients, change existing ones, manage scopes, and view claims by themselves with the DevOps Dashboard’s self-service features.
DevOps or other operators can view system alarms without full access to the Curity Identity Server. Allowing them to see information relating to the warning, such as impact analysis, without gaining complete access to the server. The service impact analysis also includes other impacted components. For instance, a database becomes unresponsive, so an alarm will trigger for all the components that directly or indirectly rely on this database. The DevOps Dashboard gives operators only the information and access they require to quickly identify and remediate the problem.Explore Alarms
Server A is experiencing issues
The DevOps Dashboard is easy to set up with multi-factor authentication (MFA). It utilizes the Curity Authentication Service to authenticate users stored in any data source, use authentication actions to trigger MFA, blocks access if in a new country, and so on. It also supports federated authentication via social providers like GitHub or standard OpenID Connect or SAML.
You can configure it for large-scale deployments, where certain teams can view and modify specific clients and alarms. This is enabled through the delegated administration supporting role and group-based access control.