Permissions to only allow Logged In users to see some API Documentation (APIGEE-117)
Ian Lessing (Unlicensed) did get ahold of Denise, and she is used a different authentication module. Ian is thinking about installing the module Denise suggested and trying it out.
Brought up by Ann Crawford with the following questions:
How do we request a use case for and API
What is the work flow? Possible status are : received, rejected (with reason ie duplicate), closed ( with deploy date), in test, in code
How do we search what's in the works?
Who will mange requests?
Specific use case from Ann Crawford:
Here is the API use case that I sent to housing for the photos.
Our use case is to get all new or changed photos for Type graduate or undergraduate with the perm (university ID)
New photos are perms we don't have a photo in the student health database.
Changed photos are those where the saved photo hash <> current photo hash for a given perm. Currently the sproc returns a hash of the photo so we can compare and save, along with a perm (university ID), Type, first name, last name. We don't use the first name or last name but it is good for testing.
Should we turn the feature off?