feat: support api access even if access to org is not allowed #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @DinoChiesa we've been using your lib now for almost a year and are pretty happy! We've moved to a little different and more locked down setup now, where our api users do have access to only a subset of APIs.
What is not allowed anymore, is access to the actual organization API.
Thus with current implementation we cannot use the library at all. I'm proposing a small change to the
apigee.jsand a new flagoptions.no_organization_loginthat would allow us and others to bypass the initial fetching of the Organization. The change is backwards compatible and therefore not breaking.Would be great if you could also release it soon-ish, to prevent us from using a private fork 😊