This provides a reference for all of the Approov related methods defined in the plugin. These are available if you import:
import { HTTP } from '@awesome-cordova-plugins/approov-advanced-http';or for Angular:
import { HTTP } from '@awesome-cordova-plugins/approov-advanced-http/ngx';It is assumed a local instance of HTTP is defined in the component with:
private http = HTTP;Many of the methods execute asynchronously and return a Promise. This is resolved to indicate success, or rejected with an error otherwise. The error is a map that provides:
message: A descriptive error message.type: Type of the error which may begeneral,networkorrejection. If the type isnetworkthen this indicates that the error was caused by a temporary networking issue, so an option should be provided to the user to retry.rejectionARC: Only provided for arejectionerror type. Provides the Attestation Response Code, which could be provided to the user for communication with your app support to determine the reason for failure, without this being revealed to the end user.rejectionReasons: Only provided for arejectionerror type. If the Rejection Reasons feature is enabled, this provides a comma separated list of reasons why the app attestation was rejected.
Initializes the Approov SDK and thus enables the Approov features. The config will have been provided in the initial onboarding or email or can be obtained using the Approov CLI. This will generate an error if a second attempt is made at initialization with a different config.
http.approovInitialize(config: string): Promise<void>;Note that the initialization should be performed as soon as the app starts, and before any network requests that require Approov protection. The returned Promise is resolved when the initialization is complete, and rejected if there was a problem with initialization.
Indicates that the network interceptor should proceed anyway if it is not possible to obtain an Approov token due to a networking failure. If this is called then the backend API can receive calls without the expected Approov token header being added, or without header/query parameter substitutions being made. This should only ever be used if there is some particular reason, perhaps due to local network conditions, that you believe that traffic to the Approov cloud service will be particularly problematic.
http.approovSetProceedOnNetworkFail(): void;Note that this should be used with CAUTION because it may allow a connection to be established before any dynamic pins have been received via Approov, thus potentially opening the channel to a MitM.
Sets a development key in order to force an app to be passed. This can be used if the app has to be resigned in a test environment and would thus fail attestation otherwise.
http.approovSetDevKey(devKey: string): void;Sets the header that the Approov token is added on, as well as an optional prefix String (such as "Bearer "). Pass in an empty string if you do not wish to have a prefix. By default the token is provided on Approov-Token with no prefix.
http.approovSetTokenHeader(header: string, prefix: string): void;Sets a binding header that may be present on requests being made. This is for the token binding feature. A header should be chosen whose value is unchanging for most requests (such as an Authorization header). If the header is present, then a hash of the header value is included in the issued Approov tokens to bind them to the value. This may then be verified by the backend API integration.
http.approovSetBindingHeader(header: string): void;Adds the name of a header which should be subject to secure strings substitution. This means that if the header is present then the value will be used as a key to look up a secure string value which will be substituted into the header value instead. This allows easy migration to the use of secure strings. A requiredPrefix may be specified to deal with cases such as the use of "Bearer " prefixed before values in an authorization header. If this is not required then simply use an empty string.
http.approovAddSubstitutionHeader(header: string, requiredPrefix: string): void;Removes a header previously added using approovAddSubstitutionHeader.
http.approovRemoveSubstitutionHeader(header: string): void;Adds a key name for a query parameter that should be subject to secure strings substitution. This means that if the query parameter is present in a URL then the value will be used as a key to look up a secure string value which will be substituted as the query parameter value instead. This allows easy migration to the use of secure strings.
http.approovAddSubstitutionQueryParam(key: string): void;Removes a query parameter key name previously added using approovAddSubstitutionQueryParam.
http.approovRemoveSubstitutionQueryParam(key: string): void;Adds an exclusion URL regular expression via the urlRegex parameter. If a URL for a request matches this regular expression then it will not be subject to any Approov protection.
http.approovAddExclusionURLRegex(urlRegex: string): void;Note that this facility must be used with EXTREME CAUTION due to the impact of dynamic pinning. Pinning may be applied to all domains added using Approov, and updates to the pins are received when an Approov fetch is performed. If you exclude some URLs on domains that are protected with Approov, then these will be protected with Approov pins but without a path to update the pins until a URL is used that is not excluded. Thus you are responsible for ensuring that there is always a possibility of calling a non-excluded URL, or you should make an explicit call to fetchToken if there are persistent pinning failures. Conversely, use of those option may allow a connection to be established before any dynamic pins have been received via Approov, thus potentially opening the channel to a MitM.
Removes an exclusion URL regular expression urlRegex previously added using approovAddExclusionURLRegex.
http.approovRemoveExclusionURLRegex(urlRegex: string): void;Performs a background fetch to lower the effective latency of a subsequent token fetch or secure string fetch by starting the operation earlier so the subsequent fetch may be able to use cached data.
http.prefetch(): Promise<void>;The returned Promise is rejected if the prefetch failed.
Performs a precheck to determine if the app will pass attestation. This requires secure strings to be enabled for the account, although no strings need to be set up. This will likely require network access so may take some time to complete.
http.approovPrecheck(): Promise<void>;The returned Promise is rejected if the precheck failed.
Gets the device ID used by Approov to identify the particular device that the SDK is running on. Note that different Approov apps on the same device will return a different ID. Moreover, the ID may be changed by an uninstall and reinstall of the app.
http.approovGetDeviceID(): Promise<String>;Directly sets the token binding hash from the given data to be included in subsequently fetched Approov tokens. If the hash is different from any previously set value then this will cause the next token fetch operation to fetch a new token with the correct payload data hash. The hash appears in the pay claim of the Approov token as a base64 encoded string of the SHA256 hash of the data. Note that the data is hashed locally and never sent to the Approov cloud service. This is an alternative to using SetBindingHeader and you should not use both methods at the same time.
http.approovSetDataHashInToken(data: string): Promise<void>;Performs an Approov token fetch for the given url. This should be used in situations where it is not possible to use the networking interception to add the token. This will likely require network access so may take some time to complete.
http.approovFetchToken(url: string): Promise<String>;The returned Promise is rejected if there was a problem fetching the token.
Gets the message signature for the given message. This uses an account specific message signing key that is transmitted to the SDK after a successful fetch if the facility is enabled for the account. Note that if the attestation failed then the signing key provided is actually random so that the signature will be incorrect. An Approov token should always be included in the message being signed and sent alongside this signature to prevent replay attacks.
http.approovGetMessageSignature(message: string): Promise<String>;The returned Promise may be rejected if no previous Approov token has been fetched.
Fetches a secure string with the given key. If newDef is not null then a secure string for the particular app instance may be defined. In this case the new value is returned as the secure string. Use of an empty string for newDef removes the string entry. Note that the returned string should NEVER be cached by your app, you should call this function when it is needed.
http.approovFetchSecureString(key: string, newDef: string): Promise<String>;The returned Promise may provide a resolved null if the key is not defined. The returned Promise is rejected if the device fails attestation.
Fetches a custom JWT with the given marshaled JSON payload.
http.approovFetchCustomJWT(payloa: string): Promise<String>;The returned Promise is rejected if the device fails attestation.