Software redistribution

Your software. Their environment. Your identity platform.

Deliver ProAuth as part of software installed in your customers’ environments. This specialist delivery model uses an agreed redistribution licence, with identity configured to suit each installation.

Plan your implementation

01Integrate
Application, identity and installer
02Deliver
Within the agreed licence scope
03Operate
Agree responsibilities with the customer

The business situation

Identity becomes part of what you deliver

A software vendor installs its product in customer-owned environments. Each customer chooses local accounts, enterprise federation or a combination. The vendor needs that choice to fit its installer.

01 / Working model

Make identity part of the installation

Your applications connect to ProAuth through OpenID Connect and OAuth. Within each customer environment, a single ProAuth deployment can combine local user stores and multiple OIDC identity providers.

Your deployment tooling can generate YAML configuration or call the Management API. That lets the installer apply identity settings alongside the rest of your product. An enterprise connection still needs the customer's identity administrator to configure their side of the relationship.

For disconnected operation, keep the required services and authentication methods local. A locally hosted ProAuth instance does not make an external identity provider or messaging service available during an internet outage.

Your product in the customer environment.

Software delivery and customer operation have distinct responsibilities.

DELIVERY CONTEXT

Software vendor

Package and deliver the software
Maintain your own product updates
Arrange redistribution and licensing

OPERATING CONTEXT

Customer

Operate the customer environment
Configure and operate ProAuth for the deployment model
Own application integration and operational responsibilities

HANDOFFSoftware package & operating agreement

Your application + ProAuth in the customer environment. Agree responsibilities and support for the deployment model.

What your team gains

Deliver a maintained identity product: Integrate ProAuth into your software under an agreed redistribution licence.
Adapt within each customer installation: Configure multiple identity sources in the same deployment instead of rebuilding authentication.
Keep one product experience: Integrate user administration and customise authentication views around your software.

Keep the experience within your product

ProAuth's user and group APIs let you build administration into your application's interface. Custom authentication views can follow your product's visual identity. Your users can experience one product while your team integrates a separately maintained identity component.

In customer implementations, installation automation and integrated administration have been important parts of this approach. ProAuth engineering assistance can cover application clients, human and technical identities, token usage and deployment configuration.

Define ownership for the product lifecycle

Your team owns application permissions, the installer and validation of ProAuth updates within your complete solution. You and your customer agree who deploys updates, monitors services and tests recovery. ProAuth supplies product updates and product support; integration consultancy can support the work around them.

Agree redistribution rights and support arrangements for your delivery model. Product support can work with your own support organisation so identity issues have a defined escalation path.

Details for your decision.

Let’s plan your implementation.

Take one representative installation and trace sign-in, user administration, update delivery and recovery. Identify the local services and enterprise connections it needs.

Discuss identity in your software delivery