Research Sharepoint OAuth conversion

[TylerMatteo]

Research spike for determining the impact of updating the ZAP Search and Applicant Portal APIs to authenticate to the Sharepoint API with OAuth and new credentials. The output of this spike will either be:

• Scoped out work in the form of Issues ready for engineers
• Documentation outlining further questions to be answered in subsequent spikes

[TylerMatteo]

Assigning to myself for now. Next steps will be a meeting with Ella to ask some questions about why this change is happening and what all is being deprecated.

[TylerMatteo]

Tracking initial discussions and research for this in this discussion

[TylerMatteo]

@TangoYankee @AmandaDoyle I'm closing this as completed because, after a productive conversation with Ella and Bujji, we are in a bit of a holding pattern.

Summary of meeting with CRM team

After we showed how our code uses Sharepoint APIs, Ella and Bujji sounded reasonably confident that we may not have to make any changes to our code at all. Because client ids and secrets will be generated in Azure App Registration instead of Sharepoint Pages, Ella put in a request to the Citywide Service Desk to get our app registered. Once OTI registers the app, Ella can generate new keys for us. Once we have UAT keys, we can create an Issue for someone on AE to test that they slot into our applications without needing to change any code. If that works, we can do the same for prod and be done with this. If it doesn't, we would have to embark on migrating to the newer MS Graph APIs, but we'll cross that bridge if/when we come to it.