Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Account Security #1325

Closed
2 of 3 tasks
Tracked by #1258
Biuwa opened this issue Feb 11, 2023 · 3 comments
Closed
2 of 3 tasks
Tracked by #1258

Azure Account Security #1325

Biuwa opened this issue Feb 11, 2023 · 3 comments

Comments

@Biuwa
Copy link
Member

Biuwa commented Feb 11, 2023

Overview

We need additional security (password change) for the Azure account as discussed with the stakeholders.

Action Items

Resources/Instructions

@Biuwa
Copy link
Member Author

Biuwa commented Apr 5, 2023

2023-04-04 STAKEHOLDER MEETING NOTES:

Alexander will convey a meeting between Leon and the HfLA Engineering team to discuss the Account setup and access to the city's Azure Account.

@entrotech
Copy link
Member

We had a meeting today with Lon Soh, Alexander Wikstrom, Johnny Voong, Bonnie and myself. At the moment, the credentials stored in the "tdm shared vault with city" 1Password vault called "TDM Production Azure Account" uses the username ladot.tdm@lacity.org work, and are able to access the Production SQL Server virtual machine, SQL server database, and App Service - which is sufficient for us to support deployment to the production environment. However, that email is used for LADOT and City Planning communication with end users, and credentials for access to production environments are supposed to be associated with individual people (vs a generic service email), so we requested that two new email addresses be created, one for john.darragh@lacity.org and one for a fictitious user jacob.rodes@lacity.org for us to use, and to have these account granted access to the Azure portal.

Previously they had granted access to a different account, tdm@hackforla.org to the TDM Azure resource groups, and that account had access to the UAT and Production account resources. Since that time, this account no longer has access to the production resources, but does have access to the UAT resources, though Lon thought the UAT resources had been decommissioned - however I am still able to access the UAT environment with these credentials.

I believe the action items coming from this meeting are:

  • City personnel are to create two new email accounts: john.darragh@lacity.org and jacob.rodes@lacity.org and grant them access to the City's Azure portal and the production resources.
  • Once these accounts are set up and verified to have the required access, the ladot.tdm@lacity account no longer needs Azure access and can be removed from Azure.
  • The UAT environment is working, but no one seems to use it. We need to decide if we want to have a UAT environment at all.
  • If so, city personnel are to re-create resources for the UAT environment as desired, and grant the two new accounts access to these resources as well, so HFLA personnel can re-create the UAT environment. If re-created we can either initialize with a copy of the production environment database, or a clean-empty database (with no user accounts or projects).

@Biuwa
Copy link
Member Author

Biuwa commented May 6, 2023

Two email accounts have been created.

@Biuwa Biuwa closed this as completed May 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants