Introduction

The following pages explain the core concepts of the SDK:

• Client concepts
• Using identity-based licensing

See also the official 10Duke Enterprise documentation.

Getting started

The following are some central items from the API:

• The 10Duke Enterprise client is in namespace tenduke::ee
• To create the client, use the factory function tenduke::ee::createClientUsingAutodiscovery(const std::string &,const tenduke::ee::ClientProperties &,const std::string &,const tenduke::oidc::osbrowser::BrowserAuthenticationConfig &,const std::string &,const tenduke::ServiceConfiguration &)
• The client itself: tenduke::ee::TendukeClient
• Licensing client (aggregated in the main client) tenduke::ee::licensing::LicensingClient
• Service for managing the user login session: tenduke::oidc::OIDCSession
• Service for managing leases: tenduke::ee::licensing::LicenseTokens

Examples

The client has the following working examples:

• ./examples/identity_based_client: A simple client using identity-based licensing that uses the default OS browser to authenticate users. Performs some common operations.
• ./examples/oauth_device_auth: A simple client using identity-based licensing that uses OAuth Device Authorization to authenticate users. Performs some common operations.
• ./examples/bring-your-own-browser: Demonstrates how a custom browser integration can be implemented.

Features

The following features are currently supported:

• Transparent user login with the default OS browser (no manual start required). Login is initiated when the first API call (for example, a license checkout) is performed or when a user session has expired
• Automatic session refresh
• User session management
• License checkouts
• License releases
• Serialization of leases to JSON for offline storage and deserialization of JSON to leases