2018-10-05 Apigee Overview with Registrar Meeting notes

Owned by Diana Antova
Last updated: Oct 05, 2018
1 min read

Date

Oct 5, 2018

Attendees

  • @Diana Antova

  • @Steven Maglio

  • @Seth Northrop

  • @Leesa Beck (Unlicensed)

  • @Anthony Schmid

  • @Marsha Bankston (Unlicensed)

Goals

  • Review the Apigee implementation

  • Review the API publish workflow and the approval process

  • Discuss the proposed API access request workflow and the approval process

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

20 min

Demo of Apigee portal

@Diana Antova @Steven Maglio

  • https://developer.ucsb.edu

  • Demo site

  • Account creation

    • ucsb accounts approved always

    • non-ucsb accounts - only with a valid need to have access

    • other accounts are deleted

  • Security implementation

    • Apigee keys

    • SIST security

  • API products

20 min

API Publish Process

@Diana Antova

  • Publishing developer submits a form that goes thru a workflow

  • Workflow states

    • Initial review - Developer

    • Pending More Info Initial - API Admin

    • Business Review - API Admin, Business Approver

    • Pending More Info Business - Business Approver

    • Business Approved/ In Technical Review - API Admin, Business Approver

    • Pending More Info Admin - API Admin, Business Approver

    • Published- API Admin

    • Cancelled - Developer, API Admin

    • Business Denied - Business Approver

    • Admin Denied - API Admin

    • Retired - API Admin

20 min

Application API Request Process

@Diana Antova

  • Developer creates application and requests access to API products (standard Apigee functionality)

  • Proposal: to develop an approval workflow process within the portal

    • Have a record of each application, contact information, description, and the API approval. Currently he approval is in email only.

    • All information is kept in the portal and easily accessible.

    • The form can be saved as a pdf and emailed to Registrar for their records

    • Visibility of the documents - can we show them to everyone with an account? keep private

    • Access Request Workflow Requirements

  • Alternative: we continue to use the registrar access request form and save copies in Box

    • Pros: already established method

    • Cons:

      • documentation is not easily accessible

      • not everyone campus has access to the Box folder

      • there will be other approvers for non-student APIs

Action items

Decisions