Purpose

The off-boarding instruction below walk through how to remove and disable all access to EOSDIS tools and operational environments in the cloud for Earthdata Search members who are leaving the team and/or contract. Also see New Developer Onboarding for reverse instructions.

____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

1.    NASA Logins

• AUID (Launchpad username)
• NASA email
• NDC account

Please call the Enterprise Service desk to disable the accounts of the person of interest who is leaving the team. This step may only be needed if the person of interest plans to leave the EOSDIS contract entirely.

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

2.    EOSDIS Community Tools

1.   Earthdata Login

      Many of our systems require an Earthdata Login profile to login.  This is what our end-users use to access our systems and therefore as developers, we use it for many things ourselves.

• Contact Emeka Agha to delete  Earthdata Login (URS) profile. 

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

2.   Earthdata Code Collaborative (ECC)

     We use many Atlassian tools such as JIRA, Confluence, BitBucket and Bamboo.  The EDL profile from above this used o sign-up with the Earthdata Code Collaborative (ECC), which acts as a gateway to the Atlassian tool suite. 

• Login to Earthdata Code Collaborative (ECC)
• Search for groups user of interest is a member of
• Reach out to an administrator to remove user

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

3.   Atlassian Groups

      Simply being registered in the ECC and having selected your team's project in the step above will get you access to probably 90% of what you need.  To avoid complications and possible compromised information , please remove user Atlassian permission group they have been assigned to. 

      For DAACs, there is normally a representative at each DAAC who controls access to these groups, so please ask your team who to contact.  If all else fails, email Ross Bagwell who can help guide you:

• ESDIS_ALL_ACCESS
• ESEC-esec-viewers (EED program folks)
• daac_asdc
• daac_asf
• daac_cddis
• daac_gesdisc
• daac_ghrc
• daac_laads
• daac_lpdaac
• daac_nsidc
• daac_obdaac
• daac_ornl
• daac_sedac
• daac_podaac
• GIBS_team
• daac_managers
• worldview
• ens-team

      For EED developers, please submit a Service Desk Ticket, noting that the EED developer needs to be removed from the following group:

• ESEC-esec-viewers

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

4.     EOSDIS Slack

     Inside EOSDIS, we primarily use slack to communicate with each other.  To remove access, simply email the contact noted below based on which organization you are a part of.  That contact will then handle everything after that including removal from funds, license reallocation when applicable, NAMS submission, and NAMS provisioning.

• DAAC Staff -> DAAC Manager***
• SIPS Staff → SIPS Managers (Jeanne Behnke, Evelyn Ho) 
• EED folks → Barri Rubel (who will send to Steve Berrick)
• EISOC folks and any other security folks → ESDIS Security (Chris Mishaga, Jay Herford)
• ESDIS Network  → Kevin Kranacs
• IMPACT → Sara Lubkin, Alfreda Hall
• CSDA → Alfreda Hall
• HQ → Andy Mitchell

*** Some organizations, like NSIDC, ORNL and OPeNDAP have their own Slack accounts.  Please work with your DAAC staff to know your DAAC specific procedures.

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

5.     Listservs

After slack, listservs are the next most important communication vehicle in EOSDIS.  The user should be removed from the mailing list once their NASA email has been disabled. If not, please remove user from your SAFe train's listserv if you are on a SAFe train. by reaching out to train lead of specified train below: 

Search & Discovery Train - Cheryl Curtis ***

                 https://lists.nasa.gov/mailman3/lists/search-discovery-train.lists.nasa.gov/

Ingest & Archive Train - Shae Gibson

                https://lists.nasa.gov/mailman3/lists/ingest-archive-train.lists.nasa.gov/

Platform Train - Bob Gac

                https://lists.nasa.gov/mailman3/lists/esdis-platform-train.lists.nasa.gov/

Transformation Train - Dana Shum

               https://lists.nasa.gov/mailman3/lists/transformation-train.lists.nasa.gov/

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

6.    Jama Requirements Management Tool (Optional)

We primarily use a tool called Jama for Requirements Management.  The Jama tool also has built-in document review functionality which is used by many teams to review both requirements and other technical documents.  Not all developers need access to Jama but if the user does follow the step below:

• Create a service desk ticket https://bugs.earthdata.nasa.gov/servicedesk/customer/portal/5/create/16. 
  • Provide name and team
  • Request account be removed

3.    Cloud, Code, Build, and Deployment Tools

Please remove the user from the following applications:

7.  Github

8. Bamboo

9.  Snyk (if applicable)

10. AWS Kion (Cloudtamer)