Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Objective

To describe all areas required to support the API Management platform Apigee at UCSB, and the responsible people for each area. The platform consists of two main tools - the developer portal, and the gateway, both described below. 

Developer Portal (https://developer.ucsb.edu/): used for API discovery, and requests. API users sign up for the developer portal, create an App, and request access to APIs for their app. An API key is given to them to be able to access the APIs. The API team has developed access request forms to manage the API publishing and API access requests and record the decisions. The API team has developed standards and guidelines for API use by employees, and by students. 

Gateway (https://login.apigee.com/login): used for API publishing, execution, and statistics. Gateway accounts require Apigee license. Users publish APIs, grant API access to Apps, have access to Apigee reports in the gateway to troubleshoot errors and to view API usage statistics. 

Apigee Responsibility Matrix

AreaDutiesPrimary Responsible PersonOther Responsible PeopleDocumentation Links

Developer Portal Account Approval

  • Verify a valid ucsb affiliation.
  • Verify student or employee affiliation.
  • Approve/deny account.
  • Add to google groups.
Diana AntovaSteven MaglioAPI team has access to approve/deny accountshttps://developer.ucsb.edu/docs/accounts/developer-portal

Governance - API Access Requests

  • Review API access requests
  • Request access approval form submission.
  • Review provided information on access request form is sufficient.
  • Route requests through the workflow.
  • Meet with the developer to understand the need and the best way to serve their need.
  • Approve API access request form.
Diana AntovaSteven Magliohttps://developer.ucsb.edu/docs/applications/application-approval-request
Governance - API Publishing Requests
  • Review API publishing requests.
  • Route request through the workflow.
  • Review that API meets the development standards.
  • Publish the API in the gateway.
  • Create API documentation in developer portal to make it available for access requests.
Steven MaglioKevin WuGary Scott https://developer.ucsb.edu/api-publishing-request
Governance - Gateway admin 
  • Review technical information on API access requests, including security information.
  • Approve API access request in gateway. 
Steven Maglio

Diana AntovaKevin Wuchristian.montecino (Unlicensed)


Application Development Support
  • Provide guidance on LDAP account creation
  • API usage guidelines


https://developer.ucsb.edu/docs/accounts/ldap-accounts



Student Development Support


Steven MaglioSeth NorthropDiana Antovahttps://developer.ucsb.edu/docs/applications/student-developed-applications





  • No labels