Skip to main content

Patterns Overview

The Nevis Identity Suite comes with an extensive set of Patterns to configure Nevis.

Check the Configuration Patterns Reference for detailed information about each pattern.

Patterns are associated with the following categories:

  • Add-ons: Patterns that can be assigned to other patterns to add optional features.
  • Application Protection: Patterns to set up reverse proxy and WAF features.
  • Applications: Patterns to expose backend applications via nevisProxy.
  • Authentication: Patterns to build authentication and self-admin flows using nevisAuth.
  • Authentication Cloud: Patterns to integrate with Nevis Authentication Cloud.
  • Connector: alternative to instance patterns. Use to connect to existing instances.
  • Database: integration of the database for a Nevis component.
  • Experimental: Patterns that may change in future releases.
  • FIDO2: Patterns for passwordless authentication using FIDO2 protocol.
  • Federation: Patterns for SAML, OAuth, and OpenID Connect.
  • Generic: Patterns that allow for arbitrary configuration at the component level.
  • Identity Management: Patterns to configure identity management and authentication using nevisIDM.
  • Instances: Patterns that set up instances of nevisProxy, nevisAuth, nevisIDM, and other Nevis components.
  • Key Management: Patterns to configure key material and certificates.
  • Kubernetes: Patterns to configure Kubernetes related aspects (e.g. Ingress).
  • Logging: Set log levels of Nevis components.
  • Mobile Authentication: Patterns to set up mobile authentication use cases.
  • Onboarding: Patterns to configure onboarding use cases.
  • OAuth: Use for OAuth federation.
  • OpenID Connect: Use for OpenID Connect.
  • Realms: Realms provide single-sign-on for applications.
  • SAML: Set up a SAML Service Provider or Identity Provider.
  • Tokens: Patterns to define application access tokens.
  • User Behavior Analytics: Patterns to set up nevisDetect and nevisAdapt.

In case your use case is not supported directly, you can often use Generic patterns instead. Generic patterns allow for arbitrary configuration at the component level. For instance, you can set low-level properties, configure nevisAuth AuthState elements using their XML syntax, or add a Lua or Groovy script.

Generic patterns also support generation time expressions, which allow for environment-specific generation. For instance, you can use the ${var.name} syntax to reference variables from your nevisAdmin 4 inventory.

User Interface​

Patterns are used in nevisAdmin 4. See Working with Patterns for details.

Detailed settings and help for the individual patterns can be found in the Help section of the nevisAdmin 4 UI.

nevisAdmin 4 UI - Help panel