-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
chore: auth on api-v2 with api-key #15455
Merged
Merged
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Ignored Deployments
|
keithwillcode
added
core
area: core, team members only
platform
Anything related to our platform plan
labels
Jun 17, 2024
dosubot
bot
added
api
area: API, enterprise API, access token, OAuth
authentication
area: authentication, auth, google sign in, password, SAML, password reset, can't log in
labels
Jun 17, 2024
Graphite Automations"Add foundation team as reviewer" took an action on this PR • (06/17/24)1 reviewer was added to this PR based on Keith Williams's automation. "Add platform team as reviewer" took an action on this PR • (06/17/24)1 reviewer was added to this PR based on Keith Williams's automation. |
…into chore-apiv2-auth-api-key
e2e and self review coming soon |
…al.com into chore-apiv2-auth-api-key
supalarry
previously approved these changes
Jun 19, 2024
…alcom/cal.com into chore-apiv2-auth-api-key
Ready for merge |
…b.com:calcom/cal.com into chore-apiv2-auth-api-key
…into chore-apiv2-auth-api-key
supalarry
approved these changes
Jun 19, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Jun 19, 2024
p6l-richard
pushed a commit
to p6l-richard/cal.com-fork
that referenced
this pull request
Jul 22, 2024
* chore: enable apiv2 auth with api keys * chore: enable apiv2 auth with api keys * chore: enable apiv2 auth with api keys * chore: enable apiv2 auth with api keys * chore: enable apiv2 auth with api keys * fixup! chore: enable apiv2 auth with api keys * fixup! Merge branch 'chore-apiv2-auth-api-key' of github.com:calcom/cal.com into chore-apiv2-auth-api-key * fixup! fixup! Merge branch 'chore-apiv2-auth-api-key' of github.com:calcom/cal.com into chore-apiv2-auth-api-key * fixup! fixup! fixup! Merge branch 'chore-apiv2-auth-api-key' of github.com:calcom/cal.com into chore-apiv2-auth-api-key
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api
area: API, enterprise API, access token, OAuth
authentication
area: authentication, auth, google sign in, password, SAML, password reset, can't log in
core
area: core, team members only
platform
Anything related to our platform plan
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.
What does this PR do?
Enables api calls to api-v2 to use api-key as authentication token
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
yarn test api-auth.strategy.spec.ts