| | | |
|---|
| Welcome |
| |
| Vacations |
|
|
| Contractor needs |
| |
| Splunk |
| Dec 17, 2020 Christian and Thomas enabled Splunk calls. Thomas promised the separate splunk instance by end of the year. Mar 4, 2021 Diana and Christian met with Tom. He will set up the new instance without moving the history as this is challenging.
|
| Developer Portal Migration to Drupal 8 | @Steven Maglio | Notes: Drupal 8 Migration Notes Links: Feb 4, 2021 Navodit - Working on the workflow transitions. Learning/using the the original Workflow modules code to pull in the transitions data and filter it. Still needing to determine how to get the correct filtering for display. During the week, we also discussed that Diana, Navodit and Steven met. During their meeting they decided: Feb 18, 2021 Custom module is pushed to dev instance. Tested with the different roles. Will start to work on the API Publishing view. The workflow status is not showing in the view. Navodit will check all business rules for both workflows and send Diana an email to begin testing. Mar 4, 2021 working on workflow status migration automation. created a feature branch. Roles will be next after the workflow status script.
Mar 18, 2021 Migration Process (update new site with data from the current/old site) Updated to include the API Access / API Publishing Request Workflow History (ie. Audit History) Updated to include the API Access / API Publishing Request Status values (they changed the format what data is stored in the database between versions)
Updated the workflow processes to better replicate the logic of when to send emails (it looks to be exactly matching the original sites logic now) Currently looking into a discrepancy in the emails that are sent. In the new system the url to the API Access / API Publishing requests that are included in the email looks like “/node/234”, where it should be “/some-application-name”. Merged the latest upstream changes into the dev environment. We changed the workflow for Jira tickets. We are now creating a new multidev environment for each ticket. The multidev environment get’s reviewed and approved before being merged back into the main line. Navodit will be out on Mar 29, 2021 Steven will be out Mar 22, 2021 - Mar 26, 2021, Ian will meet with Navodit during the week (Monday - Thursday, Friday is Caesar Chavez Day) Apr 8, 2021 Navodit finished the Swagger documentation. Yaml file issue - pantheon is not accepting .yml files. It has to be .yaml extension. Pantheon is fixing it but not sure when. We will need to change the extension any time we publish a new API. Navodit is working on ticket 88 - to recreate the API menu. Navodit will be out 4/30.
Apr 15, 2021 Workflow fixes have been completed and are ready for final sign-off. We are struggling with a password storing problem for the Apigee drupal portal account. The default storage system is not working so Navodit is troubleshooting it. Unfortunately, he doesn’t have access to the drupal portal account password in order to verify his testing. If Navodit complete’s the Apigee configuration setup over the next week, he will start work on re-adding the Register and Login buttons. Our roadmap shows we still have to do: Apigee configuration/integration, Login functionality, conversation about site look & feel redesign, and then the implementation of look & feel.
|
| graphql APIs | @Kevin Wu | Employee Job API - they have had multiple requests from campus. Created a GraphQL version of it. it is a simpler query language. Implemented a solution for security. client id and secret. get back a job token. can apply row level security. can do column level security as well. As of Mar 18, 2021, Kevin is looking to build out the Proof-of-Concept around Apigee OAuth for usage on the endpoint by the end of April. This will include: An authentication endpoint (which will return JWTs) .wellknown/openid-configuration endpoint Certificates creation and management Documentation Reusable Shared Flow for authentication/authorization in Apigee The expectation is that the standard OAuth/JWT libraries for service providers will be able to use this
|
| Apigee accounts needs |
|
|
| API Security | @Kevin Wu / @Steven Maglio / @christian.montecino (Unlicensed) | The team wants to come up with a unified solution for API security Kevin is experimenting options without using CAS 2 options using access token, using custom attributes in the gateway JWT token, using key value maps, can be encrypted
Christian researched 3rd party oath - OKTA Apigee cannot communicate with CAS because of a firewall issue
Mar 18, 2021 |
| Student Developed Applications |
| Jun 4, 2020 Steven and Seth met with the students. They are continuing to grow the sites. Two new members of the team are taking over. Henry is graduating, Jimmy is staying. |
| Meeting and group focus year 2020 |
| Project focus In progress - Drupal 8 (see also Drupal 8 Migration High Level Requirements) Pending - AWS - migrate the Heroku code and the sql server database Pending - Account cleanup automation Pending - Identity integration and automation
Apigee Support 1 FTE on the apigee team to help with student development oversight and support Now the students have to contact so many groups to have their accounts setup, an FTE can really help with that. Adding the functionality to developer.ucsb.edu to create accounts.
|