Access Control

Warrior has role-based access control (RBAC) to restrict system access. To authenticate, a client application must provide a unique API key. This key should be kept secure and rotated often. Users can login to the dashboard UI with their username and password. Alternatively, the dashboard also supports SAML 2.0 authentication if your organization has an Identity Provider (IdP).

• Authentication
  • API Keys
  • Single Sign-On SSO Authentication
    • SAML 2.0 Authentication
    • Open ID Connect (OIDC) Authentication (On-Prem Only)
      • OIDC YAML Configuration
        • OIDC Example YAML Configuration
      • OIDC with Identity Providers that do not support CORS (Microsoft Azure AD)
• Authorization
  • Standard RBAC
  • Standard RBAC for OIDC users.
  • Custom RBAC for OIDC users
  • Managing Roles and Permissions
    • Understanding Permissions
    • Create Custom Roles
    • Get Custom Roles
    • Delete Custom Roles
    • Example Role Configuration JSON
• Deep Linking