Connection

Settings → Connection is where Stratos finds your crew system and how your pilots sign in. Changes here never cut pilots off: a new address or OAuth set-up only takes over once it has been checked.

​

Change the Stratos endpoint URL

The Stratos endpoint URL under VA backend is where your bookings, pilots and PIREPs live. On phpVMS 7 it’s the Stratos Core module’s address (your site plus /api/stratos); on your own backend, wherever you implement the Stratos API. It must use https and be reachable from the internet.

1. Type the new address. Pilots keep using the old one until the new one is verified.
2. Click Verify. Console asks the address to identify itself as a Stratos endpoint.
3. Once it’s verified, pilots use the new address. Discard goes back to the address pilots use now.

​

Choose how pilots sign in

Pilots sign in one way at a time, shown under How pilots sign in:

• Username and password: pilots type their crew system username and password into Stratos, which checks them with your backend.
• OAuth 2.0: pilots sign in on your own site, which hands Stratos a token.

To move to OAuth, fill in OAuth set-up while pilots keep signing in with their username and password, then click Test sign-in. When every step passes, OAuth turns on and pilots use it from their next sign-in. Later edits stay unpublished until another test sign-in passes; Discard changes drops them. Switch back returns pilots to username and password, and keeps your OAuth set-up for later. The full set-up, including the redirect URIs to add to your OAuth provider, is in OAuth sign-in.

​

Require pilots to sign in again

Require pilots to sign in again, then Require sign-in, asks every pilot to sign in to your airline again. Pilots flying now are asked once their flight finishes, so no flight is interrupted. The line beside it says when you last did this.

​

Related

• OAuth sign-in
• How changes reach your pilots
• Stratos Core API