Skip to content
IdentitéTrust starts here
English
EnglishEspañolPortuguês
Contact

On-Premises Passwordless Authentication: NoPass Deployment Options

Hosting an authentication service inside your environment and delivering notifications without external push are two separate deployment choices. NoPass™ was designed for fully self-hosted authentication. Current builds use external push. For a customer requiring independence from those services, a local notification channel can be implemented as part of the deployment. A complete local-delivery build is a customer integration option, rather than a currently released build.

Two notification paths

  1. Current: customer-hosted service → external push delivery → enrolled app.
  2. Customer integration option: customer-hosted service → local notification channel → reachable enrolled app.
  3. In both: the configured authentication flow returns a result to the calling application.

Choose the topology around the access path

DecisionCurrent customer-hosted pathFully local deployment option
Authentication service and application integrationHosted in the customer environment, according to edition and configurationHosted in the customer environment
App notificationCurrent builds use external push; define permitted connectivity and device reachabilityIntegrate a local signaling or notification channel and validate the clients that will receive it
Network boundaryMap authentication endpoints and external push dependenciesMap reachable endpoints, segmented networks and any approved route for remote devices
Release acceptanceVerify configured connectivity, enrollment, recovery and operationAccept only after customer-specific build and delivery, including outage, recovery and device tests

The application initiates the authentication request. The NoPass service handles the configured exchange with the enrolled app. Notification tells the person that there is a request to inspect; the authentication result comes from the configured authentication flow. Plan both paths explicitly. Confirm which flows still function if notifications are delayed, a mobile device moves to a different network, or a site loses connectivity.

Dependencies to map before procurement

  1. Identify the protected application, user groups and devices. Draw where the application, authentication service, directory and devices sit.
  2. Determine how a device reaches the service from the corporate network and from an approved remote path. Agree DNS, certificates, trust and proxy ownership for each route.
  3. Define the notification delivery requirement. If external push is allowed, document approved dependencies and outage expectations. If local delivery is required, identify the local channel owner and the client integration that must be built and verified.
  4. Assign enrollment, device revocation, recovery and account lifecycle responsibilities. Exercise a lost-device scenario before pilot expansion.
  5. Establish a support boundary. The service team owns authentication operations; the application team owns permissions and sessions; the network and device teams own the paths that keep the service reachable.

Troubleshooting and pilot acceptance

A missing notification can reflect delivery reachability while the authentication service remains healthy. Start with a request ID and timestamp, check whether the application created the request and then check delivery and the device’s network context. A delivered request followed by a failed authentication belongs to a different branch. Check enrollment status, service configuration and the integration’s handling of the result.

For local delivery, define reachability separately for managed on-site devices, remote devices and a disconnected site. Measure the workflows the customer actually needs. Include a change to enrollment, delayed delivery and an unavailable device. Availability and recovery under network isolation must be demonstrated for that topology.

Bring your proposed network boundaries and one workforce workflow to an integration discussion. Review NoPass workforce authentication, Desktop Unlock and the FDA architecture.