0.1.51

NSOF-9189 certificates: support configuring BYO certificates

BYO certificates are CA certificates the admin configures and can be used
in AAC rules in order to validate that the user has a device certificate
signed by those CAs.

In our API certificates are managed via our v1/certificates endpoints.
Originally only "managed" certificates were supported, which means the
caller provided a list of SANs and the service would create and manage
respective certificates used by the service.

With the introduction of AAC the certificates API was extended to support
providing BYO CA certificates.

Add a "certificate" string field - which is mutually exclusive with the
"sans" field - to allow providing a certificate in PEM format.

For implementation simplicity, two shortcuts are taken:

- the certificate field uses a "ForceNew" attribute, which means the
  certificate cannot be changed on an existing object. This means that for
  now, if an AAC rule points to an existing certificate, and that
  certificate PEM needs to be changed, the AAC rule needs to be changed
  as well.

- no support for BYO certificates in the certificate data source

0.1.50

NSOF-8836 aac_rules: remove suspicious_login field

0.1.49

NSOF-7985 dlp/fsr: remove all

Scan rules are replacing fsr and dlp rules, so need to remove.

0.1.48

NSOF-7985 dlp/file_scanning_rule: disallow create/update of fsr/dlp r…

0.1.47

NSOF-8280 provider: remove deprecated ufr catalog_app_risk field

0.1.46

NSOF-8150 url_filtering_rule: modify ufr ISOLATION action to ISOLATE

0.1.45

NSOF-8039 app: add domain_federation sub resource

0.1.44

NSOF-7972 idp: introduce resource and data-source

0.1.43

NSOF-6622 pac_file_test.go: vary priority values to reduce conflicts

0.1.42

NSOF-7538 ssl_bypass_rules: fix action description