HTML5 Viewer Login and Authentication Sequence

Arbiter/HTML5 Login/Authentication sequence

• Halcyon JWT auth backend built into the user server

• Get a user login scope token from user server (valid for 48 hrs)

• Sends token to the arbiter for new connection

• Set up websocket connection to arbiter

  • Send token with initial login message
  • Arbiter checks token, success/fail

• Presence is set to last location

• Arbiter connects to region if a connection doesn't already exist

  • Arbiter sends auth request to JWT arbiter auth gateway
  • JWT arbiter auth gateway checks the arbiter shared password
  • Arbiter login message sent to simulator which contains a JWT token to auth against

• Set up and log in user presence

• In the initial connection case, client requests initial flatbuffer update stream from simulator:

  • Update stream contains base object data such as:
    • Object ID (UUID and LocalId)
    • Parent ID (local)
    • Mesh information (UUID of mesh/sculpt for Arbiter gateway request)

• Initial scene is optimized and rendered

• User presence data for all avatars on the region is downloaded