cloudfoundry / cloudfoundry/uaa

Paging for retrieval of all identity zones

Open
#3,144 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.6k
Forks
844
Avg merge
2d 5h
Merged PRs (30d)
27

Description

What version of UAA are you running?

77.18.0

How are you deploying the UAA?

I am deploying the UAA

  • using cf-deployment
What did you do?

Retrieval of all identity zones via endpoint /identity-zones.

What did you expect to see? What goal are you trying to achieve with the UAA?

Expectation is that the API applies paging by default, similar to the SCIM API (/Users, /Groups). With regards to the page size, the API should define a default (e.g. 100) and a maximum value (e.g. 500).

The goals are:

  • Avoid high DB load issues if the UAA has a high number of identity zones
  • Ensure an appropriate response time if the UAA has a high number of identity zones
What did you see instead?

No paging mechanism supported for endpoint /identity-zones.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the /identity-zones API alongside the documented SCIM /Users and /Groups list behavior. Define appropriate default and maximum page sizes, then verify that the endpoint supports paging and avoids unbounded retrieval; done means the behavior is implemented and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend-api-design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.