Curate a service offering

This topic describes how you expose an AuthServer as a ready-to-claim service offering using a ClusterWorkloadRegistrationClass.

ClusterWorkloadRegistrationClass creates resources so that application operators can discover and claim credentials for an Application Single Sign-On service offering. A ClusterWorkloadRegistrationClass has a description that is shown when application operators discover services by running tanzu service class list. This allows you identify the offering as an Application Single Sign-On service.

Furthermore, ClusterWorkloadRegistrationClass carries a base WorkloadRegistration, which is the blueprint for claims against this service. This base selects the target AuthServer. It can optionally receive a custom domain template, labels, and annotations that all WorkloadRegistration inherit.

Prerequisites

Before you create a service offering, you must create and configure an AuthServer. For instructions, see the topics in the service operator guide.

Create a ClusterWorkloadRegistrationClass

For an AuthServer with the following labels:

---
apiVersion: sso.apps.tanzu.vmware.com/v1alpha1
kind: AuthServer
metadata:
  labels:
    sso.apps.tanzu.vmware.com/env: staging
    sso.apps.tanzu.vmware.com/ldap: ""
#! ...

You can expose it as a claimable service offering by configuring a ClusterWorkloadRegistrationClass as follows:

apiVersion: sso.apps.tanzu.vmware.com/v1alpha1
kind: ClusterWorkloadRegistrationClass
metadata:
  name: demo
spec:
  base:
    authServerSelector:
      matchLabels:
        sso.apps.tanzu.vmware.com/env: staging
        sso.apps.tanzu.vmware.com/ldap: ""

After you apply this resource, application operators can discover it by running tanzu service class list, for example:

$ tanzu service class list
  NAME  DESCRIPTION
  demo  Login by AppSSO

Application operators can claim credentials for this service either by running the command tanzu service class-claim create or with a ClassClaim resource.

When a claim is created, a WorkloadRegistration is created from the base and it targets the AuthServer.

Customize the ClusterWorkloadRegistrationClass

Each WorkloadRegistration has https:// redirect URIs templated. The default template is configured with default_workload_domain_template. If spec.workloadDomainTemplate is omitted, the default template is used. For more information, see default_workload_domain_template. Otherwise, you can customize it by setting a template on the base, for example, "{{.Name}}-{{.Namespace}}.demo.{{.Domain}}".

You can further customize each WorkloadRegistration by setting labels and annotations for them.

The default description of an Application Single Sign-On service offering is "Login by AppSSO", but you can customize this. Consider using a good name and description. For more information, see Names and descriptions later in this topic.

For example, if you want the WorkloadRegistration to template redirect URIs from a custom template and with both https:// and http://, and you want to say that in the service’s description, edit the ClusterWorkloadRegistrationClass as follows:

apiVersion: sso.apps.tanzu.vmware.com/v1alpha1
kind: ClusterWorkloadRegistrationClass
metadata:
  name: demo
spec:
  description:
    short: Login by AppSSO with LDAP for apps in the "demo" subdomain
  base:
    metadata:
      annotations:
        sso.apps.tanzu.vmware.com/template-unsafe-redirect-uris: ""
    spec:
      workloadDomainTemplate: "{{.Name}}-{{.Namespace}}.demo.{{.Domain}}"
      authServerSelector:
        matchLabels:
          sso.apps.tanzu.vmware.com/env: staging
          sso.apps.tanzu.vmware.com/ldap: ""

Names and descriptions

When choosing a name and a description for a ClusterWorkloadRegistrationClass consider the following:

• When the name of a service is stable across environments, for example, from dev to production, application operators can use the same ClassClaim in all environments.

• The description of a service must clearly communicate its flavor and provider. The default description of a ClusterWorkloadRegistrationClass is "Login by AppSSO".

  If there is a single Application Single Sign-On service offering the default description is usually good enough.

  To customize the description for your ClusterWorkloadRegistrationClass, consider prefixing it with "Login by AppSSO - ", for example, "Login by AppSSO - LDAP and GitHub.