Skip to main content
nx1-deployer image v1.11.0
The March 2026 release for web portal users introduces new catalog and metastore API endpoints, and an identity provider feature.

​
Catalog and metastore management

New API endpoints for managing the following across NexusOne is now available:
  • Schemas and tables
  • Catalogs
  • DataHub metadata
NexusOne converts the REST API calls into Trino SQL requests and returns the Trino response as an API response. The new API endpoints includes the following:
bash
# Alter table
PATCH /api/metastore/catalogs/{catalog_name}/schemas/{schema_name}/tables/{table_name}

# Create schema
POST  /api/metastore/catalogs/{catalog_name}/schema

# Create table
POST  /api/metastore/catalogs/{catalog_name}/schemas/{schema_name}/tables

# Delete schema
DELETE  /api/metastore/catalogs/{catalog_name}/schemas/{schema_name}

# Delete table
DELETE  /api/metastore/catalogs/{catalog_name}/schemas/{schema_name}/tables/{table_name}

# Get catalogs details
GET  /api/metastore/catalogs/details

# Get catalog schemas details
GET  /api/metastore/catalogs/{catalog_name}/schemas/details

# Get schema tables details
GET  /api/metastore/catalogs/{catalog_name}/schemas/{schema_name}/tables/details

# Get table details from Trino
GET  /api/metastore/catalogs/{catalog_name}/schemas/{schema_name}/tables/{table_name}/details

# Get table metadata from DataHub
GET  /api/metastore/catalogs/{catalog_name}/schemas/{schema_name}/tables/{table_name}/metadata

# Get table preview
GET  /api/metastore/catalogs/{catalog_name}/schemas/{schema_name}/tables/{table_name}/preview
As a web portal user, you can browse and inspect catalog metadata, and perform managed schema and table operations through the UI. Specifically, at Govern > Catalog.

​
Identity provider management

Using a single NX1 interface, you can now configure and manage external identity providers, such as:
  • Auth0
  • GitHub
  • Google Workspace
  • Microsoft Entra ID
  • Okta
  • OneLogin by One Identity
  • PingIdentity
  • Other custom OIDCs providers
  • Other custom SAMLs providers
Each identity provider still uses Keycloak as the authoritative configuration store via the Keycloak Admin API. NexusOne doesn’t store any IdP configuration locally. This new feature also comes with the following:
  • New API endpoints via the /api/identity-providers/ path
  • New UI wizard at Govern > Identity Provider to connect and manage an external identity provider.