Android OAuth 클라이언트 ID는 특정 인증서/패키지 쌍에 연결됩니다. 앱의 사용자 수와 관계없이 인증서당 하나의 ID만 있으면 됩니다.
앱의 ID를 가져오려면 여러 단계를 거쳐야 합니다. 이 단계는 아래에 설명되어 있습니다.
앱의 인증서 정보를 찾습니다.
Google API 콘솔에서 프로젝트를 만들거나 수정합니다.
OAuth 2.0 클라이언트 ID를 요청합니다.
앱의 인증서 정보 찾기
API 키는 SHA-1 디지털 지문이라고 하는 간단한 형식의 앱 디지털 인증서를 기반으로 합니다. 인증서의 SHA-1 디지털 지문을 표시하려면 먼저 올바른 인증서를 사용하고 있는지 확인합니다. 2개의 인증서를 가질 수 있습니다.
디버그 인증서: 디버그 빌드를 실행할 때 Android SDK 도구에서
자동으로 생성하는 인증서입니다. 이 인증서는
테스트 중인 앱에만 사용하세요.
디버그 인증서로 서명된 앱은 게시하지 마세요.
디버그 인증서는 Android 개발자 문서의
디버그 모드에서 서명에
자세히 설명되어 있습니다.
출시 인증서: 출시 빌드를 실행할 때 Android SDK 도구에서
이 인증서를 생성합니다. keytool 프로그램을 사용하여
이 인증서를 생성할 수도 있습니다. 앱을 출시할 준비가 되면
이 인증서를 사용하세요.
아래의 단계에 따라 keytool 프로그램을 -v 매개변수와
함께 사용하여 인증서의 SHA-1 디지털 지문을 표시합니다. Keytool에 대한
자세한 내용은
Oracle 문서를 참고하세요.
디버그 인증서
디버그 인증서 디지털 지문 표시
디버그 키 저장소 파일을 찾습니다. 파일 이름은
debug.keystore이며 프로젝트를 처음 빌드할 때
생성됩니다. 기본적으로 파일은 Android Virtual Device(AVD) 파일과
동일한 디렉터리에 저장됩니다.
macOS 및 Linux: ~/.android/
Windows Vista 및 Windows 7: C:\Users\your_user_name\.android\
출시 인증서 키 저장소 파일을 찾습니다. 출시 키 저장소에는
기본 위치 또는 이름이 없습니다. 출시용 앱을 빌드할 때
이를 지정하지 않으면 빌드에서 .apk를 서명되지 않은 상태로
두며 여기에 먼저 서명해야 게시할 수
있습니다. 출시 인증서의 경우 인증서의 별칭 및
키 저장소와 인증서의 비밀번호도 필요합니다. 다음을 입력하면
키 저장소에 있는 모든 키의 별칭이 나열됩니다.
keytool-list-keystoreyour_keystore_name
your_keystore_name을 .keystore 확장자를 포함하여
키 저장소의 정규화된 경로와 이름으로
대체합니다. 키 저장소의 비밀번호를 입력하라는 메시지가 표시됩니다. 그런 다음
keytool에 키 저장소에 있는 모든 별칭이 표시됩니다.
[null,null,["최종 업데이트: 2025-08-31(UTC)"],[[["\u003cp\u003eTo use Google Fit for Android, you need an OAuth 2.0 client ID linked to your app's certificate and package name.\u003c/p\u003e\n"],["\u003cp\u003eBefore requesting a client ID, obtain your app's SHA-1 fingerprint from its debug or release certificate using the \u003ccode\u003ekeytool\u003c/code\u003e program.\u003c/p\u003e\n"],["\u003cp\u003eRequest an OAuth 2.0 client ID through the Google API Console by creating or selecting a project, enabling the Fitness API, and providing your app's SHA-1 fingerprint and package name.\u003c/p\u003e\n"]]],[],null,["# Get an OAuth 2.0 Client ID\n\nOverview\n--------\n\nTo use the Google Fit for Android, you need an OAuth 2.0 client ID for\nAndroid applications.\n\nAll Android apps are signed with a digital certificate for which you hold the\nprivate key. Refer to the [Android guide to signing your applications](//developer.android.com/tools/publishing/app-signing.html)\nfor more information about digital certificates.\n\nAndroid OAuth client IDs are linked to specific certificate/package pairs. You\nonly need one ID for each certificate, no matter how many users you have for\nthe app.\n\nGetting an ID for your app requires several steps. These steps are outlined\nbelow.\n\n1. Find your app's certificate information.\n2. Create or modify a project in the Google API Console.\n3. Request an OAuth 2.0 client ID.\n\nFind your app's certificate information\n---------------------------------------\n\nThe API key is based on a short form of your app's digital certificate,\nknown as its **SHA-1 fingerprint**. To display the SHA-1\nfingerprint for your certificate, first ensure that you are using the right\ncertificate. You may have two certificates:\n\n- **A debug certificate** : The Android SDK tools generate this certificate automatically when you do a debug build. Only use this certificate with apps that you're testing. Do not attempt to publish an app that's signed with a debug certificate. The debug certificate is described in more detail in [Signing\n in Debug Mode](https://developer.android.com/tools/publishing/app-signing.html#debug-mode) in the Android Developer Documentation.\n- **A release certificate** : The Android SDK tools generate this certificate when you do a release build. You can also generate this certificate using the `keytool` program. Use this certificate when you are ready to release your app to the world.\n\nFollow the steps below to display a certificate's SHA-1 fingerprint using\nthe `keytool` program with the `-v` parameter. For more\ninformation about Keytool, see the\n[Oracle documentation](http://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html).\nDebug certificate \n\n### Displaying the debug certificate fingerprint\n\n1. Locate your debug keystore file. The file name is\n `debug.keystore`, and is created the first time you build your\n project. By default, it is stored in the same directory as your Android\n Virtual Device (AVD) files:\n\n - **macOS and Linux** : `~/.android/`\n - **Windows Vista and Windows 7** : `C:\\Users\\your_user_name\\.android\\`\n2. List the SHA-1 fingerprint:\n\n - For Linux or macOS, open a terminal window and enter the following:\n\n ```gdscript\n keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android\n ```\n - For Windows Vista and Windows 7, run:\n\n ```gdscript\n keytool -list -v -keystore \"%USERPROFILE%\\.android\\debug.keystore\" -alias androiddebugkey -storepass android -keypass android\n ```\n\nYou should see output similar to this: \n\n```carbon\nAlias name: androiddebugkey\nCreation date: Jan 01, 2013\nEntry type: PrivateKeyEntry\nCertificate chain length: 1\nCertificate[1]:\nOwner: CN=Android Debug, O=Android, C=US\nIssuer: CN=Android Debug, O=Android, C=US\nSerial number: 4aa9b300\nValid from: Mon Jan 01 08:04:04 UTC 2013 until: Mon Jan 01 18:04:04 PST 2033\nCertificate fingerprints:\n MD5: AE:9F:95:D0:A6:86:89:BC:A8:70:BA:34:FF:6A:AC:F9\n SHA1: BB:0D:AC:74:D3:21:E1:43:07:71:9B:62:90:AF:A1:66:6E:44:5D:75\n Signature algorithm name: SHA1withRSA\n Version: 3\n```\nRelease certificate \n\n### Displaying the release certificate fingerprint\n\n1. Locate your release certificate keystore file. There is no default\n location or name for the release keystore. If you don't specify one when\n you build your app for release, the build will leave your\n `.apk` unsigned, and you'll have to sign it before you can\n publish it. For the release certificate, you also need the certificate's\n alias and the passwords for the keystore and the certificate. You can list\n the aliases for all the keys in a keystore by entering:\n\n ```gdscript\n keytool -list -keystore your_keystore_name\n ```\n\n Replace *`your_keystore_name`* with the fully-qualified\n path and name of the keystore, including the `.keystore`\n extension. You'll be prompted for the keystore's password. Then\n `keytool` displays all the aliases in the keystore.\n2. Enter the following at a terminal or command prompt:\n\n ```gdscript\n keytool -list -v -keystore your_keystore_name -alias your_alias_name\n ```\n\n Replace *`your_keystore_name`* with the fully-qualified\n path and name of the keystore, including the `.keystore`\n extension. Replace *`your_alias_name`* with the alias that\n you assigned to the certificate when you created it.\n\nYou should see output similar to this: \n\n```carbon\nAlias name: \u003calias_name\u003e\nCreation date: Feb 02, 2013\nEntry type: PrivateKeyEntry\nCertificate chain length: 1\nCertificate[1]:\nOwner: CN=Android Debug, O=Android, C=US\nIssuer: CN=Android Debug, O=Android, C=US\nSerial number: 4cc9b300\nValid from: Mon Feb 02 08:01:04 UTC 2013 until: Mon Feb 02 18:05:04 PST 2033\nCertificate fingerprints:\n MD5: AE:9F:95:D0:A6:86:89:BC:A8:70:BA:34:FF:6B:AC:F9\n SHA1: BB:0D:AC:74:D3:21:E1:43:67:71:9B:62:90:AF:A1:66:6E:44:5D:75\n Signature algorithm name: SHA1withRSA\n Version: 3\n```\n\nThe line that begins with `SHA1` contains the certificate's SHA-1\nfingerprint. The fingerprint is the sequence of 20 two-digit hexadecimal\nnumbers separated by colons.\n| **Caution:** To protect your keystore and key, don't enter the `storepass` or `keypass` arguments on the command line unless you're confident of your computer's security. For example, on a public computer, someone could look at your terminal window history or list of running processes, get the password, and then have write access to your signing certificate. This would allow that person to modify or replace your app with their own.\n\nRequest an OAuth 2.0 client ID in the Google API Console\n--------------------------------------------------------\n\nFollow these steps to create or modify a project for your app in the\nGoogle API Console, enable the Fitness API, and request an OAuth 2.0 client ID.\n\nIf you want to be guided through the process and activate the\nFitness API automatically, click\n\n[Get a Client ID](https://console.cloud.google.com/flows/enableapi?apiid=fitness)\n\nAlternatively, follow these steps to enable the Fitness API in the\nGoogle API Console and get an OAuth 2.0 client ID.\n\n1. Go to the [Google API Console](https://console.cloud.google.com/flows/enableapi?apiid=fitness).\n2. Select a project, or create a new one. Use the same project for the Android and REST versions of your app.\n3. Click **Continue** to enable the Fitness API.\n4. Click **Go to credentials**.\n5. Click **New credentials** , then select **OAuth Client ID**.\n6. Under **Application type** select **Android**.\n7. In the resulting dialog, enter your app's SHA-1 fingerprint and package\n name. For example:\n\n `BB:0D:AC:74:D3:21:E1:43:67:71:9B:62:91:AF:A1:66:6E:44:5D:75`\n\n `com.example.android.fit-example`\n8. Click **Create**. Your new Android OAuth 2.0 Client ID and secret appear in\n the list of IDs for your project. An OAuth 2.0 Client ID is a string of\n characters, something like this:\n\n `780816631155-gbvyo1o7r2pn95qc4ei9d61io4uh48hl.apps.googleusercontent.com`"]]
