For the complete documentation index, see llms.txt. This page is also available as Markdown.
Use Air Gap
Security and best practices for Air Gap for OneSite Patch
Designate Security Roles
When setting up the air-gapped server, you should set up an Air Gap Admin and Air Gap Operator on both servers:
Super Admin Role: admin permissions for any Adaptiva product.
Air Gap Admin Role: only admin permissions for the Air Gap add-on.
Air Gap Operator Role: can export/import patches, but can’t change settings.
Click the gear icon > Settings > Security > Roles.
Click Air Gap Roles.
For each role, select it, and then in the Details view, use the Role Membership section to designate either an individual or an AD Group.
Be sure to click Save once you have added an individual or group to a role.
Repeat this process for the other Air Gap role.
Air Gap Roles
Best Practices and Import History
The Overview screen has some useful information in addition to being the place where you create requests and upload payloads. Here you'll find a Zone Status and Zone Overview section.
Import History
The Patch Sync Response Import History section shows a history of imports.
Keep Paired Servers in Synch
If you upgrade a server, you must also upgrade the paired server, i.e., if you upgrade the online server, you must also upgrade the air-gapped server. You cannot synch server versions across the Air Gap system of request and response as the incompatible server versions will create an error. Instead, you must use the on-prem installer on all servers you need to upgrade.
Note: server versions must be an exact match, down to the final revision number. For example, 10.2.973.9 and 10.2.973.6 do not match. This is by design to prevent incompatible code from potentially breaking the system.
Security Scans
All Patch response files can be scanned using standard corporate practices and remediation techniques.
