aviowiki
  • Introduction
  • Authentication
    • Users
    • API Tokens
    • Authorisation
  • Conventions
    • Data format
    • aviowiki IDs
    • Pagination
  • Errors
  • Reward Points
  • Open Data
    • Introduction
    • Definition
  • Data Models
    • Airport
    • Authority
    • Availability
    • Aircraft Position
    • Coordinates
    • Region
    • Country
    • Governing District
    • Runway
    • Provider
    • Generic Product
    • Fuel Product
    • Fuel Fee
    • Webhook
    • Error
    • Operational Note
      • Airport Operational Note
      • Country Operational Note
  • Free Endpoints
    • Limitations
    • Free airport endpoints
      • Airport data
      • Searching airports
  • Authenticated Endpoints
    • Airport endpoints
      • Searching airports
      • Airport data
      • Authorities at an airport
      • Availability of an airport
        • Aerodrome Rescue and Fire Fighting availaibility
        • Air Traffic Control availability
        • Customs, Immigration and Quarantine facilities availability
        • Movement availability
      • Runways at an airport
      • Providers at an airport
      • Weather at an airport
      • Sun times at an airport
      • Operational notes at an airport
    • Aircraft endpoints
    • Aircraft position endpoints
    • Flight endpoints
    • Runway endpoints
      • Runway data
    • Provider endpoints
      • Provider data
      • Availability of a provider
      • Country of a provider
      • Pictures of a provider
      • Logo of a provider
      • Products of a provider
      • Fuel products of a provider
    • Operational Note endpoints
      • Operational Note data
    • Retrieve aircraft position
  • Release log
Powered by GitBook
On this page

Was this helpful?

  1. Authentication

Users

PreviousAuthenticationNextAPI Tokens

Last updated 4 years ago

Was this helpful?

aviowiki has an internal User management system that performs the functions of Authentication and Authorisation, as well as other administrative functions.

are issued for and assigned to a specific User, and follow the same rules as the User who owns them.

Users are identified internally by their User , with namespace USR. For example USR-AA11-22BB.

When creating an account, users are required to provide a login and password .

login should be in the form of an email address.

password doesn't have any specific level of complexity required, however we strongly encourage people to be responsible with their passwords. If you need to have a memorable password (one you can remember without the help of a , consider using a which is . However the cases in which you really need to use a memorable password are nowadays quite limited. We always recommend to use a where possible.

User object

When retrieving information about a user from the API, you will receive a user object which follows the structure shown below:

{
  "aid": "USR-AA11-22BB",
  "name": "Demo User",
  "login": "demo@example.com",
  "password": null,
  "roles": [
    "USER"
  ],
  "reward": 0
}

name is a plaintext name that the user chose at the time of sign-up.

login the login credential to authenticate the user.

password is always returned null in all responses.

For more user actions see:

aid indicates the of the user.

roles is a list of assigned to the user.

reward is the total count of collected by the user.

API Tokens
Authorisation
AID
Password Manager
passphrase
easy to remember, but difficult to guess
Password Manager
AID
Authorisation roles
reward points