Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document what type of Auth can be in each endpoint #171

Closed
hunterowens opened this issue Nov 8, 2018 · 2 comments
Closed

Document what type of Auth can be in each endpoint #171

hunterowens opened this issue Nov 8, 2018 · 2 comments
Labels
Provider Specific to the Provider API
Milestone
0.3.0

Comments

@hunterowens
Copy link
Collaborator

Currently, provider/auth.md doesn't show what endpoints can be covered with what types of limits / auth.

Proposal:

provider/auth.md show that GBFS endpoints should be open to the public, while /trips/ and /status_changes can be restricted to a municipality.

For open to the public, there is a question of allowing companies to rate limit queries to that endpoint.
@hunterowens hunterowens added the Provider Specific to the Provider API label Nov 9, 2018
@black-tea
Copy link
Contributor

black-tea commented Nov 9, 2018 •
edited
Loading

I like this suggestion, though I'm curious the extent to which we would be setting policies on the GBFS endpoint. I think that that question falls into the same territory as imposing pagination restrictions, which @thekaveman has suggested should be left to NABSA

@hunterowens hunterowens added this to the 0.3.0 milestone Nov 18, 2018
@hunterowens
Copy link
Collaborator Author

I think NABSA is fairly clear that GBFS should be made open, IIRC.

@thekaveman thekaveman mentioned this issue Dec 3, 2018
Closed
hunterowens added a commit that referenced this issue Feb 4, 2019
@hunterowens
Document Auth requirements. fixes #171
f557b5e
hunterowens added a commit that referenced this issue Feb 4, 2019
@hunterowens
Auth requirements. Fixes #171
4dbc3fb 
Update `auth.md` with authentication requirements.
hunterowens added a commit that referenced this issue Feb 4, 2019
@hunterowens
Authentication Requirements. Fixes #171
51c585a 
Update `auth.md` with authentication requirements.
hunterowens added a commit that referenced this issue Feb 14, 2019
@hunterowens
Merge branch 'dev' of https://github.com/CityOfLosAngeles/mobility-da…
7352119 
…ta-standard into dev

* 'dev' of https://github.com/CityOfLosAngeles/mobility-data-standard: (33 commits)
  Update definition of timestamp to match provider Also replacer "UUIDv4" with "UUID4", as is convention
  Update README.md
  Update README.md
  Clarify that the time-based-filtering query parameters should be stackable.
  fix cloud line.
  add mds-agency-cli project
  Adding Cloud as Provider, mds, and gbfs
  language cleanup, link to GPS articles
  truncate -> round
  switch to round, fix typo.
  Update provider to allow precision based truncate. fixes #209
  Cleaning up service_areas endpoint
  Add versioning requirement to Provider API
  Fixing two missing initial event states.
  Update provider/auth.md
  Authentication Requirements. Fixes #171
  Update README.md
  Update README.md
  generate full schemas
  clean up and fix the schema
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Provider Specific to the Provider API
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
2 participants
@hunterowens @black-tea