|
| 1 | +Project: /docs/reference/js/_project.yaml |
| 2 | +Book: /docs/reference/_book.yaml |
| 3 | +page_type: reference |
| 4 | + |
| 5 | +{% comment %} |
| 6 | +DO NOT EDIT THIS FILE! |
| 7 | +This is generated by the JS SDK team, and any local changes will be |
| 8 | +overwritten. Changes should be made in the source code at |
| 9 | +https://github.com/firebase/firebase-js-sdk |
| 10 | +{% endcomment %} |
| 11 | + |
| 12 | +# FirebaseServerAppSettings interface |
| 13 | +Configuration options given to [initializeServerApp()](./app.md#initializeserverapp_30ab697) |
| 14 | + |
| 15 | +<b>Signature:</b> |
| 16 | + |
| 17 | +```typescript |
| 18 | +export interface FirebaseServerAppSettings extends FirebaseAppSettings |
| 19 | +``` |
| 20 | +<b>Extends:</b> [FirebaseAppSettings](./app.firebaseappsettings.md#firebaseappsettings_interface) |
| 21 | +
|
| 22 | +## Properties |
| 23 | +
|
| 24 | +| Property | Type | Description | |
| 25 | +| --- | --- | --- | |
| 26 | +| [appCheckToken](./app.firebaseserverappsettings.md#firebaseserverappsettingsappchecktoken) | string | An optional AppCheck token.<!-- -->If provided, the FirebaseServerApp instance will work to validate the token. The result of the validation can be monitored by invoking the FirebaseServerApp.appCheckTokenVerified(). Awaiting the Promise returned by appCheckTokenVerified is highly recommended if an AppCheck token is provided.<!-- -->If the token has been properly verified then the AppCheck token will be automatically used by Firebase SDKs that support App Check.<!-- -->If the token fails verification then a warning is logged and the token will not be used. | |
| 27 | +| [authIdToken](./app.firebaseserverappsettings.md#firebaseserverappsettingsauthidtoken) | string | An optional Auth ID token used to resume a signed in user session from a client runtime environment.<!-- -->If provided, the FirebaseServerApp instance will work to validate the token. The result of the validation can be queried via by the application by invoking the FirebaseServerApp.authIdTokenVerified(). Awaiting the Promise returned by authIdTokenVerified is highly recommended if an Auth ID token is provided.<!-- -->Once the token has been properly verified then invoking getAuth() will attempt to automatically sign in a user with the provided Auth ID Token.<!-- -->If the token fails verification then a warning is logged and Auth SDK will not attempt to sign in a user upon its initalization. | |
| 28 | +| [installationsAuthToken](./app.firebaseserverappsettings.md#firebaseserverappsettingsinstallationsauthtoken) | string | An optional Installation Auth token.<!-- -->If provided, the FirebaseServerApp instance will work to validate the token. The result of the validation can be monitored by invoking the FirebaseServerApp.installationTokenVerified(). Awaiting the Promise returned by appCheckTokenVerified is highly recommended before initalization any other Firebase SDKs.<!-- -->If the token has been properly verified then the Installation Auth token will be automatically used by Firebase SDKs that support Firebase Installations.<!-- -->If the token fails verification then a warning is logged and the token will not be used. | |
| 29 | +| [name](./app.firebaseserverappsettings.md#firebaseserverappsettingsname) | undefined | There is no get for FirebaseServerApps, so the name is not relevant. however it's always a blank string so that FirebaseServerApp conforms to the FirebaseApp interface declaration. | |
| 30 | +| [releaseOnDeref](./app.firebaseserverappsettings.md#firebaseserverappsettingsreleaseonderef) | object | An optional object. If provided, the Firebase SDK will use a FinalizationRegistry object to monitor the Garbage Collection status of the provided object, and the Firebase SDK will release its refrence on the FirebaseServerApp instance when the provided object is collected. or.<!-- -->The intent of this field is to help reduce memory overhead for long-running cloud functions executing SSR fulfillment without the customer's app needing to orchestrate FirebaseServerApp cleanup. Additionally, prexisting FirebaseServerApp instances may reused if they're identical to a previously generated one that has yet to be deleted.<!-- -->If the object is not provided then the application must clean up the FirebaseServerApp instance through the applicationss own standard mechanisms by invoking deleteApp.<!-- -->If the app provides an object in this parameter, but the application is executed in a JavaScript engine that predates the support of FinalizationRegistry (introduced in node v14.6.0, for instance), then the Firebase SDK will not be able to automatically clean up the FirebaseServerApp instance and an error will be thrown. | |
| 31 | +
|
| 32 | +## FirebaseServerAppSettings.appCheckToken |
| 33 | +
|
| 34 | +An optional AppCheck token. |
| 35 | +
|
| 36 | +If provided, the FirebaseServerApp instance will work to validate the token. The result of the validation can be monitored by invoking the FirebaseServerApp.appCheckTokenVerified(). Awaiting the Promise returned by appCheckTokenVerified is highly recommended if an AppCheck token is provided. |
| 37 | +
|
| 38 | +If the token has been properly verified then the AppCheck token will be automatically used by Firebase SDKs that support App Check. |
| 39 | +
|
| 40 | +If the token fails verification then a warning is logged and the token will not be used. |
| 41 | +
|
| 42 | +<b>Signature:</b> |
| 43 | +
|
| 44 | +```typescript |
| 45 | +appCheckToken?: string; |
| 46 | +``` |
| 47 | +
|
| 48 | +## FirebaseServerAppSettings.authIdToken |
| 49 | +
|
| 50 | +An optional Auth ID token used to resume a signed in user session from a client runtime environment. |
| 51 | +
|
| 52 | +If provided, the FirebaseServerApp instance will work to validate the token. The result of the validation can be queried via by the application by invoking the FirebaseServerApp.authIdTokenVerified(). Awaiting the Promise returned by authIdTokenVerified is highly recommended if an Auth ID token is provided. |
| 53 | +
|
| 54 | +Once the token has been properly verified then invoking getAuth() will attempt to automatically sign in a user with the provided Auth ID Token. |
| 55 | +
|
| 56 | +If the token fails verification then a warning is logged and Auth SDK will not attempt to sign in a user upon its initalization. |
| 57 | +
|
| 58 | +<b>Signature:</b> |
| 59 | +
|
| 60 | +```typescript |
| 61 | +authIdToken?: string; |
| 62 | +``` |
| 63 | +
|
| 64 | +## FirebaseServerAppSettings.installationsAuthToken |
| 65 | +
|
| 66 | +An optional Installation Auth token. |
| 67 | +
|
| 68 | +If provided, the FirebaseServerApp instance will work to validate the token. The result of the validation can be monitored by invoking the FirebaseServerApp.installationTokenVerified(). Awaiting the Promise returned by appCheckTokenVerified is highly recommended before initalization any other Firebase SDKs. |
| 69 | +
|
| 70 | +If the token has been properly verified then the Installation Auth token will be automatically used by Firebase SDKs that support Firebase Installations. |
| 71 | +
|
| 72 | +If the token fails verification then a warning is logged and the token will not be used. |
| 73 | +
|
| 74 | +<b>Signature:</b> |
| 75 | +
|
| 76 | +```typescript |
| 77 | +installationsAuthToken?: string; |
| 78 | +``` |
| 79 | +
|
| 80 | +## FirebaseServerAppSettings.name |
| 81 | +
|
| 82 | +There is no get for FirebaseServerApps, so the name is not relevant. however it's always a blank string so that FirebaseServerApp conforms to the FirebaseApp interface declaration. |
| 83 | +
|
| 84 | +<b>Signature:</b> |
| 85 | +
|
| 86 | +```typescript |
| 87 | +name?: undefined; |
| 88 | +``` |
| 89 | +
|
| 90 | +## FirebaseServerAppSettings.releaseOnDeref |
| 91 | +
|
| 92 | +An optional object. If provided, the Firebase SDK will use a FinalizationRegistry object to monitor the Garbage Collection status of the provided object, and the Firebase SDK will release its refrence on the FirebaseServerApp instance when the provided object is collected. or. |
| 93 | +
|
| 94 | +The intent of this field is to help reduce memory overhead for long-running cloud functions executing SSR fulfillment without the customer's app needing to orchestrate FirebaseServerApp cleanup. Additionally, prexisting FirebaseServerApp instances may reused if they're identical to a previously generated one that has yet to be deleted. |
| 95 | +
|
| 96 | +If the object is not provided then the application must clean up the FirebaseServerApp instance through the applicationss own standard mechanisms by invoking deleteApp. |
| 97 | +
|
| 98 | +If the app provides an object in this parameter, but the application is executed in a JavaScript engine that predates the support of FinalizationRegistry (introduced in node v14.6.0, for instance), then the Firebase SDK will not be able to automatically clean up the FirebaseServerApp instance and an error will be thrown. |
| 99 | +
|
| 100 | +<b>Signature:</b> |
| 101 | +
|
| 102 | +```typescript |
| 103 | +releaseOnDeref?: object; |
| 104 | +``` |
0 commit comments