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.

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

Security Api Key functionality #3684

Merged
merged 10 commits into from
May 7, 2019
Merged

Conversation

codebrain
Copy link
Contributor

No description provided.

@codebrain codebrain added the WIP label Apr 18, 2019
@codebrain codebrain self-assigned this Apr 18, 2019
Copy link
Contributor

@russcam russcam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 I left some questions about the high level API naming, Security* which apply to the request/response types and API methods.

Security is the API spec namespace for methods, but the 6.x client does not have API namespaces. Should Security be removed, or moved to before ApiKey e.g.

SecurityCreateApiKey() -> CreateSecurityApiKey

or

SecurityCreateApiKey() -> CreateApiKey

@codebrain
Copy link
Contributor Author

I've renamed everything to drop the "Security*" prefix from the beginning, looks much better.

@codebrain codebrain merged commit 4ecdfa8 into 6.7 May 7, 2019
russcam pushed a commit that referenced this pull request May 8, 2019
russcam added a commit that referenced this pull request May 9, 2019
@russcam russcam deleted the feature/security-invalidate-token branch May 10, 2019 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants