GITKRAKEN GIT FLOW FULL

The OAuth app can access our API with the user's access token.

Users are redirected back to the OAuth application.

Users are redirected to GitKraken to authorize access to the OAuth application.

If you can't host a web service, please ask users to create a Personal Access Token instead. You must have a hosted backend performing the auth code exchange and delivering the access token to the user's device. For example, do not use the auth code exchange inside a mobile app. You cannot ship your client secret to users.

Do not ship the client secret in code that will be delivered to your users' devices.

Do not store the client secret in a public git repo.

If you need to, we provide an easy way to reset your client secret

The Client Secret is sensitive information that you should protect accordingly.

You now have credentials that can be used in an OAuth application.

The callback url is the url that will be used in step 2 of the Web Application Flow.

The Homepage and Authorization callback must be valid URLs.

App name can be anything but will be displayed to your users when they login to your app via OAuth.

To create an OAuth app, visit the OAuth Apps tab under your email on the account page. OAuth applications used in conjunction with our API and/or webhooks can be a powerful way to create amazing experiences with GitKraken Boards. OAuth 2.0 is a standard that allows applications to access user data on their behalf.

GITKRAKEN GIT FLOW FULL

Please read our full announcement and FAQ to learn more.

GitKraken Boards and GitKraken Timelines will sunset at the end of 2022. Users are redirected back to your site by GitKraken Usage with mobile apps, Chrome extensions, and other client-side code

Gitkraken git flow