Skip to content

BCU 3.3.0

Choose a tag to compare

View all tags
@jawheelr jawheelr released this 05 Oct 20:10
· 6 commits to main since this release
3.3.0
0049825
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Blueprint Conversion Utility 3.3.0

🚀 What's New

Blueprint Conversion Utility 3.3.0 introduces the first public command-line interface (CLI), enhanced enterprise deployment capabilities, Developer ID code signing support, and a fully notarized macOS release.

This release focuses on automation, security, deployment readiness, and platform administration workflows.

Still a work in progress - do not judge this too heavily.

✅ Signed and Notarized Release

Blueprint Conversion Utility is now distributed as a:

  • ✅ Developer ID signed application
  • ✅ Developer ID signed installer package
  • ✅ Apple notarized application
  • ✅ Apple notarized installer package
  • ✅ Gatekeeper-approved distribution

Users should no longer receive unidentified developer warnings when installing or launching the application.

🖥️ New Command-Line Interface (CLI)

Added the new:

bcu

command-line utility.

The CLI shares configuration and credentials with the graphical application and allows administrators to perform common operations directly from Terminal.

Supported Commands

Version Information

bcu version

Platform Connection Status

bcu connection status

Platform Connection Testing

bcu connection test

Credential Expiration Status

bcu credentials status

Configuration Profile Discovery

bcu profiles list --type computer
bcu profiles list --type mobile

Device Group Discovery

bcu groups list --type computer
bcu groups list --type mobile

Unified Log Viewing

bcu logs show
bcu logs stream

Application Management

bcu app open
bcu app check-for-updates

🔐 Platform Credential Expiration Tracking

Added API credential expiration awareness directly within the application.

Status Indicator

The footer now displays API credential health.

🟢 Green

Credentials valid and not nearing expiration.

Platform credentials expire Mar 29, 2027
177 days remaining

🟡 Yellow

Credentials approaching expiration.

Platform credentials expire soon
21 days remaining

🔴 Red

Credentials expired or authentication failed.

Platform credentials expired

or

Platform credentials invalid
Authentication failed

⚪ Gray

Expiration date not configured.

🌐 Platform Environment Architecture

Blueprint Conversion Utility now uses:

Platform Environment ID

as the sole scope identifier.

Removed:

Tenant ID

throughout the application.

Benefits include:

  • Simplified configuration
  • Reduced user confusion
  • Consistent Platform API behavior
  • Standardized request headers

All Platform API requests now use:

X-Environment-Id

🧭 Connections Improvements

The Platform API connection screen now incorporates:

Platform API URL
Client ID
Client Secret
Platform Environment ID
API Client Expiration Date
Expiration Warning Period

Additional improvements include:

  • Date-picker based expiration tracking
  • Configurable warning thresholds
  • Improved connection testing
  • Better validation messaging

🔒 Security Improvements

Enhanced handling of sensitive authentication information.

Client Secret Protection

Client Secrets are:

  • Stored in macOS Keychain
  • Excluded from Unified Logging
  • Excluded from exports
  • Never written to plain-text settings
  • Hidden after entry

CLI Security

The new CLI:

  • Reads existing application settings
  • Uses Keychain-stored secrets
  • Never displays Client Secrets
  • Supports automation-friendly JSON output

🧰 Developer Experience Improvements

Enhanced Build System

build.sh now supports:

--sign-app
--sign-installer
--notary-profile
--skip-notarization
--version
--arch

Example:

./build.sh \
  --sign-app "Developer ID Application: Your Name (TEAMID)" \
  --sign-installer "Developer ID Installer: Your Name (TEAMID)" \
  --notary-profile blueprint-notary

Automatic Release Pipeline

The build system now supports:

  • Building application bundles
  • Signing helper binaries
  • Signing CLI binaries
  • Signing application bundles
  • Signing installer packages
  • Notarizing packages
  • Notarizing disk images
  • Stapling notarization tickets
  • Performing Gatekeeper validation

📦 Packaging Improvements

The installer package now deploys:

/Applications/Blueprint Conversion Utility.app

and

/usr/local/bin/bcu

allowing CLI access immediately after installation.

📚 Documentation Updates

Updated documentation now includes:

  • Platform Environment setup
  • API Client requirements
  • Required Jamf permissions
  • Credential security guidance
  • CLI usage documentation
  • Developer ID signing guidance
  • Notarization procedures
  • Build and release workflows

🛠️ Fixes and Stability Improvements

Fixed

  • Platform API credential validation workflow
  • Environment ID configuration workflow
  • Multiple scope identifier confusion
  • CLI configuration sharing
  • Build-signing compatibility issues
  • Developer ID signing support
  • Release packaging workflows

Improved

  • Platform API onboarding experience
  • Footer status visibility
  • Connection validation
  • Enterprise deployment readiness
  • Build automation
  • macOS distribution compatibility

💡 Upgrade Recommendation

This is a recommended upgrade for all users.

Version 3.3.0 provides:

  • Enterprise-ready signed distribution
  • Apple notarization
  • Automated deployment tooling
  • Terminal automation support
  • Improved credential lifecycle management
  • Simplified Platform API configuration

🙏 Thank You

Thank you for using Blueprint Conversion Utility!

The addition of the CLI, Developer ID signing, Apple notarization, and enterprise-focused deployment enhancements mark a significant step toward enterprise-scale automation and deployment workflows.

Assets 4
Loading