GX Technology : Dynamic Account Management V2

 

NOTE: This document is not complete as moving to GAE will drastically change things and we still have not figured out end to end encryption and what the resposne/requests will look like when communicating with external partners. Some documentation on action buttons still has yet to be finalized.

Checklist

NameAxis Dynamic Account Management V2
Owner

Jacquie Armstrong

Product ManagerDavid Sohnchen
Developers

Unknown User (jonac003) (Security Review, Back End)

Darryl Dekok (Architecture)

Curtis Dodd (Front End, Integration Support)

Darlesson Oliveira (Front End)

Unknown User (moye002) (Back End)

 

JiraDIWCPCT Jira
Documentation
LinkDescription
Dynamic Account Management v2 ComponentsMain overview of the Dynamic Account Management Components
Source Code
Running Environments

Dev:

Environment Summary and AID

Incoming Connections

    • SSH/22
    • HTTPS/443

Outgoing Connections

    • HTTPS/443

Third Party Software (on dev01, other environments may vary)

    • Apache2
    • Apache Tomcat 7.0.32
    • java version "1.8.0_121"

    • MySQL 5.6.15-63.0

Flow

  1. Client Support Representative requests account information
  2. Request is sent to one of the servers which adds cellophane credentials
  3. Request is passed through the cellophane proxy and a response is sent back from the game server
  4. Response is sent back through the flow and received by the support rep software

 

Operational Summary

Deployment Process

    • Deployments in pre prod use Jenkins, prod uses tech ops to deploy artifacts built in jenkins.
    • Configuration is performed manually by Tech Ops and DBAs

Logging

    • Java server uses SLF4J for logging, with default configuration
    • Log files are written to the local file system and pulled by Splunk
    • Stage and Production environments have debug messages suppressed
    • Java: Splunk Logs
Threat Model

 

Attachments:

Axis in GAE (future).png (image/png)
Axis in GAE (future) (application/gliffy+json)