Identity/BrowserID/IntranetPhonebook: Difference between revisions

Line 1: Line 1:
Feature enhancement to the MoCo internal phonebook.
Feature enhancement to the MoCo internal phonebook.


= IT Plans and Concerns =
= IT Constraints and Assumptions =
Our entire corp ldap infrastructure is going through an overhaul this quarter, and this will tie in closely with that. As part of that, phonebook will move to the generic cluster in Phoenix. As part of that, it'll get a dev and stage environment, although that particular part will be sometime in q4, since it involves some additional planning to be done after the full LDAP overhaul.  
 
Our entire corp LDAP infrastructure is going through an overhaul this quarter, and this will tie in closely with that. As part of that, phonebook will move to the generic cluster in Phoenix. As part of that, it'll get a dev and stage environment, although that particular part will be sometime in q4, since it involves some additional planning to be done after the full LDAP overhaul.  


LDAP is a central source of truth for many many systems at Mozilla, and phonebook is just a way to gain a small window into certain parts of that information. So any changes to the backend are very difficult to test and change, so this won't be a rapid change. Every part has to be thought through fully. Like will adding an attribute to the phonebook break e-mail list generation in zimbra? Will changing an attribute in phonebook change the way a user connects to wi-fi in an office? Etc.  
LDAP is a central source of truth for many many systems at Mozilla, and phonebook is just a way to gain a small window into certain parts of that information. So any changes to the backend are very difficult to test and change, so this won't be a rapid change. Every part has to be thought through fully. Like will adding an attribute to the phonebook break e-mail list generation in zimbra? Will changing an attribute in phonebook change the way a user connects to wi-fi in an office? Etc.  
Confirmed users
1,052

edits