Introduction

Following pages discuss the core concepts of the client:

• Client concepts
• Using identity-based-licensing

You might also want to read official 10Duke Enterprise documentation.

Getting started

Some central items from API:

• The 10Duke Enterprise client is in namespace tenduke::ee
• To create the client, use 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 user login session: tenduke::oidc::OIDCSession
• Service for managing leases: tenduke::ee::licensing::LicenseTokens

Examples

The client has following working examples:

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

Features

Following features are currently supported:

• Transparent (meaning application developer does not need manually start) user login with defalt OS-browser. Login is initiated when first API-call (e.g. license checkout) is done or when user session has expired
• Automatic session refresh
• User session management
• License checkouts
• License releases
• Serialization of leases into a JSON for offline storage / deserialization of JSON to leases