이 페이지에서는 reCAPTCHA Enterprise 제공자를 사용하여 웹 앱에서 App Check를 사용 설정하는 방법을 보여줍니다. App Check를 사용 설정하면 사용자의 앱만 프로젝트의 Firebase 리소스에 액세스할 수 있습니다. 이 기능의 개요를 참조하세요.
App Check는 사용자에게 표시되지 않도록 하는 reCAPTCHA Enterprise 점수 기반 사이트 키를 사용합니다. reCAPTCHA Enterprise 제공자는 사용자에게 보안 확인을 요구하지 않습니다.
App Check에 앱을 등록한 후 App Check가 일반적으로 유효한 것으로 분류하지 않는 환경에서 앱을 실행하려는 경우(예: 개발 중 로컬에서 또는 지속적 통합(CI) 환경에서) 실제 증명 제공자 대신 App Check 디버그 제공자를 사용하는 앱의 디버그 빌드를 만들 수 있습니다.
App Check는 웹 앱을 실행하는 브라우저가 App Check 토큰을 새로고침할 때마다 사용자의 응답 토큰의 유효성을 검증하는 평가를 만듭니다. 무료 할당량을 초과하여 생성된 각 평가에 대한 요금이 프로젝트에 청구됩니다. 자세한 내용은 reCAPTCHA 가격 책정을 참조하세요.
기본적으로 웹 앱은 1시간마다 토큰을 두 번 새로고침합니다. 앱이 App Check 토큰을 새로고침하는 빈도(및 새로운 평가가 생성되는 빈도)를 제어하려면 TTL을 구성하세요.
[null,null,["최종 업데이트: 2025-08-16(UTC)"],[],[],null,["This page shows you how to enable App Check in a web app, using the\nreCAPTCHA Enterprise provider. When you enable App Check, you help ensure\nthat only your app can access your project's Firebase resources. See an\n[Overview](/docs/app-check) of this feature.\n\nNote that App Check uses reCAPTCHA Enterprise score-based site keys, which\nmake it invisible to users. The reCAPTCHA Enterprise provider will not require\nusers to solve a challenge at any time.\n\nIf you want to use App Check with your own custom provider, see\n[Implement a custom App Check provider](/docs/app-check/web/custom-provider).\n\n1. Set up your Firebase project\n\n1. [Add Firebase to your JavaScript project](/docs/web/setup) if you haven't\n already done so.\n\n2. Open the [reCAPTCHA Enterprise](https://console.cloud.google.com/security/recaptcha?project=_)\n section of the Cloud console and do the following:\n\n 1. If you're prompted to enable the reCAPTCHA Enterprise API, do so.\n 2. Create a **Website** -type key. You will need to specify domains on which you host your web app. Leave the \"Use checkbox challenge\" option **unselected**.\n3. Register your apps to use App Check with the reCAPTCHA Enterprise\n provider in the\n [**App Check**](//console.firebase.google.com/project/_/appcheck) section of the\n Firebase console. You will need to provide the site key you got in the\n previous step.\n\n You usually need to register all of your project's apps, because once you\n enable enforcement for a Firebase product, only registered apps will be able\n to access the product's backend resources.\n4. \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n **Optional** : In the app registration settings, set a custom time-to-live\n (TTL) for App Check tokens issued by the provider. You can set the TTL\n to any value between 30 minutes and 7 days. When changing this value, be\n aware of the following tradeoffs:\n - Security: Shorter TTLs provide stronger security, because it reduces the window in which a leaked or intercepted token can be abused by an attacker.\n - Performance: Shorter TTLs mean your app will perform attestation more frequently. Because the app attestation process adds latency to network requests every time it's performed, a short TTL can impact the performance of your app.\n - Quota and cost: Shorter TTLs and frequent re-attestation deplete your quota faster, and for paid services, potentially cost more. See [Quotas \\& limits](/docs/app-check#quotas_limits).\n\n The default TTL of\n **1 hour**\n is reasonable for most apps. Note that the App Check library refreshes\n tokens at approximately half the TTL duration.\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n2. Add the App Check library to your app\n\n[Add Firebase to your web app](/docs/web/setup) if you haven't already. Be sure\nto import the App Check library.\n\n3. Initialize App Check\n\nAdd the following initialization code to your application, before you access any\nFirebase services. You will need to pass your reCAPTCHA Enterprise site key,\nwhich you created in the Cloud console, to `activate()`. \n\nWeb [Learn more](/docs/web/learn-more#modular-version) about the tree-shakeable modular Web API and [upgrade](/docs/web/modular-upgrade) from the namespaced API. \n\n```python\nimport { initializeApp } from \"firebase/app\";\nimport { initializeAppCheck, ReCaptchaEnterpriseProvider } from \"firebase/app-check\";\n\nconst app = initializeApp({\n // Your Firebase configuration object.\n});\n\n// Create a ReCaptchaEnterpriseProvider instance using your reCAPTCHA Enterprise\n// site key and pass it to initializeAppCheck().\nconst appCheck = initializeAppCheck(app, {\n provider: new ReCaptchaEnterpriseProvider(/* reCAPTCHA Enterprise site key */),\n isTokenAutoRefreshEnabled: true // Set to true to allow auto-refresh.\n});\n```\n\nWeb \n\n```gdscript\nfirebase.initializeApp({\n // Your Firebase configuration object.\n});\n\n// Create a ReCaptchaEnterpriseProvider instance using your reCAPTCHA Enterprise\n// site key and pass it to activate().\nconst appCheck = firebase.appCheck();\nappCheck.activate(\n new firebase.appCheck.ReCaptchaEnterpriseProvider(\n /* reCAPTCHA Enterprise site key */\n ),\n true // Set to true to allow auto-refresh.\n);\n```\n| **Note:** The SDK will not automatically refresh App Check tokens by default. That functionality must be explicitly enabled by providing `true` as a second argument to `activate()` or by calling `firebase.appCheck().setTokenAutoRefreshEnabled(true)`. For more, see [the App Check reference docs](/docs/reference/js/firebase.appcheck.AppCheck).\n\nNext steps\n\nOnce the App Check library is installed in your app, deploy it.\n\nThe updated client app will begin sending App Check tokens along with every\nrequest it makes to Firebase, but Firebase products will not require the tokens\nto be valid until you enable enforcement in the App Check section of the\nFirebase console.\n\nMonitor metrics and enable enforcement\n\nBefore you enable enforcement, however, you should make sure that doing so won't\ndisrupt your existing legitimate users. On the other hand, if you're seeing\nsuspicious use of your app resources, you might want to enable enforcement\nsooner.\n\nTo help make this decision, you can look at App Check metrics for the\nservices you use:\n\n- [Monitor App Check request metrics](/docs/app-check/monitor-metrics) for Firebase AI Logic, Data Connect, Realtime Database, Cloud Firestore, Cloud Storage, Authentication, Google Identity for iOS, Maps JavaScript API, and Places API (New).\n- [Monitor App Check request metrics for Cloud Functions](/docs/app-check/monitor-functions-metrics).\n\nEnable App Check enforcement\n\nWhen you understand how App Check will affect your users and you're ready to\nproceed, you can enable App Check enforcement:\n\n- [Enable App Check enforcement](/docs/app-check/enable-enforcement) for Firebase AI Logic, Data Connect, Realtime Database, Cloud Firestore, Cloud Storage, Authentication, Google Identity for iOS, Maps JavaScript API, and Places API (New).\n- [Enable App Check enforcement for Cloud Functions](/docs/app-check/cloud-functions).\n\nUse App Check in debug environments\n\nIf, after you have registered your app for App Check, you want to run your\napp in an environment that App Check would normally not classify as valid,\nsuch as locally during development, or from a continuous integration (CI)\nenvironment, you can create a debug build of your app that uses the\nApp Check debug provider instead of a real attestation provider.\n\nSee [Use App Check with the debug provider in web apps](/docs/app-check/web/debug-provider).\n\nNote on cost\n\nApp Check creates an assessment on your behalf to validate the user's\nresponse token each time a browser running your web app refreshes its\nApp Check token. Your project will be charged for each assessment created\nabove the no-cost quota. See [reCAPTCHA pricing](https://cloud.google.com/security/products/recaptcha#pricing)\nfor details.\n\nBy default, your web app will refresh this token twice every **1 hour** . To\ncontrol how frequently your app refreshes App Check tokens (and thus how\nfrequently new assessments are created), [configure their TTL](#set-ttl)."]]
