| | | |
---|
| Welcome |
| |
| Vacations |
| |
| Drupal Maintenance | | |
| Apigee Support → Google Support | | Apigee Support is ending, and Google has reached out to say that support is now going to be through them. Unfortunately, it looks like there can only be one account setup with the support contract. We can meet with them:
|
| FMM | | Deliotte is developing an app called TOE (Transfer of Expense), replacing a legacy app. This is being developed in VBC (Visual Build Cloud service in Oracle, Low Code/No Code). Oracles services are going to be making calls out of Oracle Cloud and into Mulesoft. So, the FMM team is looking to use Apigee as an intermediary between the two. Oracle’s supported client security protocols are (these would run on Apigee’s servers): JWT (signed by Oracle), which would require importing their public key and maintaining/rotating their JWT public keys. Basic Auth (magic string) - Which seems like the lowest maintenance long term approach.
The security on the Mulesoft side is handled by headers client_id/client_secret This setup is going to be documented in the Mulesoft documentation at … (Kevin will create a page for this and add the link here )
|
| Billing | | Billing is setup with Steven as the owner in the Procurement Gateway. (I think there might be a Cloud & Identity ownership around Apigee?) But, Diana is the one that handles the billing. Diana and Steven will talk about this on Thursday, after meeting with Google support.
|