---
title: Platform Update - New Crypto and Certificate Nodes
description: Today’s update adds security-focused features around cryptographic signing and generating certificates for service authentication. Read more!
---

[All Things IoT | Losant Blog ](https://www.losant.com/blog)

# [Platform Update - New Crypto and Certificate Nodes](https://www.losant.com/blog/platform-update-new-crypto-and-certificate-nodes)

 Written by [Dylan Schuster](https://www.losant.com/blog/author/dylan-schuster) | Wed, Apr 8, 2026

Today’s platform update adds several new workflow nodes for handling cryptographically signed data, and for implementing certificate-based authentication.

## Crypto Workflow Nodes

First, we’ve added the [Crypto: Sign Node](https://docs.losant.com/workflows/logic/crypto-sign/) for cryptographically signing data strings with a private key – and that key can be pulled from a new [Certificate / Key Pair service credential](https://docs.losant.com/applications/credentials/#certificate--key-pair) for cloud-based usages.

As a companion to that, we’ve also added a [Crypto: Verify Node](https://docs.losant.com/workflows/logic/crypto-verify/) that can verify a signature applied to data using a public key, a certificate, or – for cloud-based uses – the original private key used to sign the data as pulled from the service credential.

Together, these workflow nodes bring a new security dimension to Losant’s workflow engine that can be applied when creating [signed URLs](https://docs.cloud.google.com/storage/docs/access-control/signed-urls) or authenticating requests to and/or from Losant’s [Gateway Edge Agent](https://docs.losant.com/edge-compute/gateway-edge-agent/overview/).

## Certificate Workflow Nodes

Additionally, we’ve added features to assist with [certificate-based authentication](https://www.onelogin.com/learn/what-is-certificate-based-authentication), a feature that Losant has long supported but has been rarely utilized to date.

The [Certificate: Create Node](https://docs.losant.com/workflows/logic/certificate-create/) takes a [certificate signing request (CSR)](https://en.wikipedia.org/wiki/Certificate_signing_request) and a certificate / key pair – stored in the [new service credential](https://docs.losant.com/applications/credentials/#certificate--key-pair) for cloud-based uses – and returns a signed certificate. This certificate can then be used to authenticate requests to various services.

The [Certificate: Read Node](https://docs.losant.com/workflows/logic/certificate-read/) takes an existing certificate and returns its public key and metadata. This can be useful when receiving requests that include the certificate in the request body and parsing the value.

By registering created [certificates](https://docs.losant.com/rest-api/application-certificates/#post) and [certificate authorities](https://docs.losant.com/rest-api/application-certificate-authorities/#post) in the Losant API, you can use these new features in support of device authentication against [Losant’s MQTT broker](https://docs.losant.com/mqtt/overview/#the-losant-message-broker).

## Other Updates

As always, this release comes with other features and improvements, including:

- We’ve added [YAML: Encode](https://docs.losant.com/workflows/logic/yaml-encode/) and [YAML: Decode](https://docs.losant.com/workflows/logic/yaml-decode/) Nodes for working with the popular [YAML Ain’t Markup Language](https://yaml.org/) data serialization format. YAML is widely used in configuration files (including the [Gateway Edge Agent](https://docs.losant.com/edge-compute/gateway-edge-agent/overview/)) as well as DevOps tools like [Docker](https://www.docker.com/) and [Kubernetes](https://kubernetes.io/).
- We’ve updated our list pagination to allow users to change the number of items displayed per page and to navigate directly to specific pages. This improves the usability of browsing Losant resource collections, especially those with thousands of items.
- Finally, workflow and custom node lists are now broken out into separate pages based on their flow class. Given the different contexts and capabilities of each workflow type, it made sense to treat each class as a separate tab instead of combining all of the lists in a single page.

## What’s Next?

With every new release, we listen to your feedback. By combining your suggestions with our roadmap, we can continue to improve the platform while maintaining its ease of use. Let us know what you think in the [Losant Forums](https://forums.losant.com/).

[View full post](https://www.losant.com/blog/platform-update-new-crypto-and-certificate-nodes)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Dylan Schuster"
  },
  "dateModified" : "2026-04-08T17:13:33.070Z",
  "datePublished" : "2026-04-08T17:13:33Z",
  "headline" : "Platform Update - New Crypto and Certificate Nodes",
  "image" : {
    "@type" : "ImageObject",
    "height" : 1024,
    "url" : "https://742943.fs1.hubspotusercontent-na1.net/hubfs/742943/Blog/platform-updates/platformUpdate-Twitter.jpg",
    "width" : 2048
  },
  "mainEntityOfPage" : "https://www.losant.com/blog/platform-update-new-crypto-and-certificate-nodes",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "All Things IoT"
  }
}
```