Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add retrieve fingerprints page and consolidate - Unity SDK #1267

Closed
wants to merge 1 commit into from
Closed

Add retrieve fingerprints page and consolidate - Unity SDK #1267

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
114 changes: 3 additions & 111 deletions src/content/docs/en/sdk/unity/v4/integrations/signature-library.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,122 +77,14 @@ The Signature library can’t verify the authenticity of your certificate finger

You must add the fingerprints of your signing certificates to the allowlist. If no fingerprints are added to the allowlist, traffic from your app can be spoofed.

</Callout>

#### From a keystore {#from-a-keystore}

If you use your own keystore, or if Android Studio generated a keystore for you, you can retrieve the certificate fingerprint by following these steps:

1. Find the keystore file (`.jks`) you used to sign **the release version of your app**. The keystore must be the one you used to sign the release version sent to the Google Play Store. If the keystore is different, your SDK requests will be rejected.
2. Run the following command to list your keys. Replace the parts in angle brackets with your information.

```console
$ keytool -list -v -keystore <path/to/keystore.jks> -alias <your_key_alias>
```

This command prompts you for your keystore password. This is the password you defined when you generated the keystore.

The final output looks like this:

```text
Alias name: Key0
Creation date: May 15, 2018
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=[Adjust, GmbH.]
Issuer: CN=[Adjust, GmbH.]
Serial number: 642f1b62
Valid from: Tue May 15 09:46:06 CEST 2018 until: Sat May 09
09:46:06 CEST 2043
Certificate fingerprints:
MD5: E7:88:9F:8C:9D:F4:14:C1:CF:E8:4C:97:F3:F2:3A:E3
SHA1:
C4:BD:07:91:BC:09:F8:B6:15:CD:BC:A3:3F:BC:68:8B:C2:EF:4F:F5
SHA256:
55:FB:97:0F:46:0F:94:EC:07:EA:01:69:50:5A:20:3F:A0:91:60:A4:F
1:33:58:EA:76:DC:54:9E:A7:6A:B9:1A
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
```

3. Save the SHA-1 fingerprint to [add to your allowlist in the Adjust Suite](#add-your-digital-certificate-fingerprints-to-adjusts-allowlist).

#### From Google Play Internal App Sharing {#from-google-play-internal-app-sharing}

If you use [Google Play Internal App Sharing](https://support.google.com/googleplay/android-developer/answer/9303479?hl=en), you need to send both your organization’s SHA-1 certificate fingerprint and your Internal test certificate fingerprint to Adjust for allowlisting.

To extract the fingerprints:

1. Navigate to the Google Play Console and log in.
2. Select your app.
3. Select **Release Management --> App Releases --> Manage internal app sharing > App certificates**.
4. Save the **SHA-1 certificate fingerprint** for both the **Internal test certificate** and your organization’s keystore to [add to your allowlist in the Adjust Suite](#add-your-digital-certificate-fingerprints-to-adjusts-allowlist).

![A screenshot of the certficate page in Google Play Console](@images/sig-v3/google-play-internal-sharing.png)

#### From Google Play App Signing {#from-google-play-app-signing}

If you use [Google Play App Signing](https://support.google.com/googleplay/android-developer/answer/7384423?hl=en), you need to send both your organization’s SHA-1 certificate fingerprint and your Internal test certificate fingerprint to Adjust for allowlisting.

To extract the fingerprints:

1. Navigate to the Google Play Console and log in.
2. Select your app.
3. Select **Release Management > App Signing**.
4. Save the **SHA-1 certificate fingerprint** for both the **App signing certificate** and **Upload certificate** to send to Adjust.

![A screenshot of the App signing page in the Google Play Console](@images/sig-v3/google-play-signing.png)

#### From Huawei AppGallery App Signing {#from-huawei-appgallery-app-signing}

If you use Huawei AppGallery App Signing, you need to send both your organization’s SHA-1 certificate fingerprint and your Internal test certificate fingerprint to Adjust for allowlisting.

<Callout type="note">

If you use your own signing certificate with Huawei AppGallery, follow the [instructions for retrieving your certificate fingerprint from a keystore](#from-a-keystore).

</Callout>

To extract the fingerprints:

1. Navigate to the App Signing page in AppGallery Connect and download the App signing certificate (`certificate.pem`).

![A screenshot of the App Signing page in AppGallery Connect](@images/sig-v3/huawei-appgallery-signing.png)

2. Once you’ve downloaded the certificate, run the following command to output the SHA-1 fingerprint of the certificate.

```console
$ openssl x509 -fingerprint -in certificate.pem -noout -SHA1
```

The output looks like this:

```text
SHA1 Fingerprint=C4:BD:07:91:BC:09:F8:B6:15:CD:BC:A3:3F:BC:68:8B:C2:EF:4F:F5
```

3. Save the fingerprint to [add to your allowlist in the Adjust Suite](#add-your-digital-certificate-fingerprints-to-adjusts-allowlist)..

### Add your digital certificate fingerprints to Adjust’s allowlist {#add-your-digital-certificate-fingerprints-to-adjust-s-allowlist}

<Callout type="note">

Remember to add all certificate fingerprints you want to use to the Adjust suite. This might include debug versions and versions for different stores.

</Callout>

Once you’ve obtained your certificate fingerprints, do the following to add them to your allowlist:

1. Select your app in AppView to open the app details screen.
2. Select the **Protection** tab.
3. Select the **Edit** button on the **Suspicious installs** section.
4. Under the **Android fingerprinting** section, select **New fingerprint**.
5. Paste the SHA-1 fingerprint into the text box that appears.
6. Select **Add**.
Follow these steps to retrieve and configure your certificate fingerprints:

That’s it! Your fingerprint is now allowlisted for your app.
1. [Retrieve Android certificate fingerprints](/en/sdk/android/integrations/retrieve-certificate-fingerprints)
2. [Configure them in the Adjust dashboard](https://help.adjust.com/en/article/sdk-signature#add-signatures-in-the-adjust-suite)

## Test your app {#test-your-app}

Expand Down
114 changes: 3 additions & 111 deletions src/content/docs/en/sdk/unity/v5/integrations/signature-library.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,122 +83,14 @@ The Signature library can’t verify the authenticity of your certificate finger

You must add the fingerprints of your signing certificates to the allowlist. If no fingerprints are added to the allowlist, traffic from your app can be spoofed.

</Callout>

#### From a keystore {#from-a-keystore}

If you use your own keystore, or if Android Studio generated a keystore for you, you can retrieve the certificate fingerprint by following these steps:

1. Find the keystore file (`.jks`) you used to sign **the release version of your app**. The keystore must be the one you used to sign the release version sent to the Google Play Store. If the keystore is different, your SDK requests will be rejected.
2. Run the following command to list your keys. Replace the parts in angle brackets with your information.

```console
$ keytool -list -v -keystore <path/to/keystore.jks> -alias <your_key_alias>
```

This command prompts you for your keystore password. This is the password you defined when you generated the keystore.

The final output looks like this:

```text
Alias name: Key0
Creation date: May 15, 2018
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=[Adjust, GmbH.]
Issuer: CN=[Adjust, GmbH.]
Serial number: 642f1b62
Valid from: Tue May 15 09:46:06 CEST 2018 until: Sat May 09
09:46:06 CEST 2043
Certificate fingerprints:
MD5: E7:88:9F:8C:9D:F4:14:C1:CF:E8:4C:97:F3:F2:3A:E3
SHA1:
C4:BD:07:91:BC:09:F8:B6:15:CD:BC:A3:3F:BC:68:8B:C2:EF:4F:F5
SHA256:
55:FB:97:0F:46:0F:94:EC:07:EA:01:69:50:5A:20:3F:A0:91:60:A4:F
1:33:58:EA:76:DC:54:9E:A7:6A:B9:1A
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
```

3. Save the SHA-1 fingerprint to [add to your allowlist in the Adjust Suite](#add-your-digital-certificate-fingerprints-to-adjusts-allowlist).

#### From Google Play Internal App Sharing {#from-google-play-internal-app-sharing}

If you use [Google Play Internal App Sharing](https://support.google.com/googleplay/android-developer/answer/9303479?hl=en), you need to send both your organization’s SHA-1 certificate fingerprint and your Internal test certificate fingerprint to Adjust for allowlisting.

To extract the fingerprints:

1. Navigate to the Google Play Console and log in.
2. Select your app.
3. Select **Release Management --> App Releases --> Manage internal app sharing > App certificates**.
4. Save the **SHA-1 certificate fingerprint** for both the **Internal test certificate** and your organization’s keystore to [add to your allowlist in the Adjust Suite](#add-your-digital-certificate-fingerprints-to-adjusts-allowlist).

![A screenshot of the certficate page in Google Play Console](@images/sig-v3/google-play-internal-sharing.png)

#### From Google Play App Signing {#from-google-play-app-signing}

If you use [Google Play App Signing](https://support.google.com/googleplay/android-developer/answer/7384423?hl=en), you need to send both your organization’s SHA-1 certificate fingerprint and your Internal test certificate fingerprint to Adjust for allowlisting.

To extract the fingerprints:

1. Navigate to the Google Play Console and log in.
2. Select your app.
3. Select **Release Management > App Signing**.
4. Save the **SHA-1 certificate fingerprint** for both the **App signing certificate** and **Upload certificate** to send to Adjust.

![A screenshot of the App signing page in the Google Play Console](@images/sig-v3/google-play-signing.png)

#### From Huawei AppGallery App Signing {#from-huawei-appgallery-app-signing}

If you use Huawei AppGallery App Signing, you need to send both your organization’s SHA-1 certificate fingerprint and your Internal test certificate fingerprint to Adjust for allowlisting.

<Callout type="note">

If you use your own signing certificate with Huawei AppGallery, follow the [instructions for retrieving your certificate fingerprint from a keystore](#from-a-keystore).

</Callout>

To extract the fingerprints:

1. Navigate to the App Signing page in AppGallery Connect and download the App signing certificate (`certificate.pem`).

![A screenshot of the App Signing page in AppGallery Connect](@images/sig-v3/huawei-appgallery-signing.png)

2. Once you’ve downloaded the certificate, run the following command to output the SHA-1 fingerprint of the certificate.

```console
$ openssl x509 -fingerprint -in certificate.pem -noout -SHA1
```

The output looks like this:

```text
SHA1 Fingerprint=C4:BD:07:91:BC:09:F8:B6:15:CD:BC:A3:3F:BC:68:8B:C2:EF:4F:F5
```

3. Save the fingerprint to [add to your allowlist in the Adjust Suite](#add-your-digital-certificate-fingerprints-to-adjusts-allowlist)..

### Add your digital certificate fingerprints to Adjust’s allowlist {#add-your-digital-certificate-fingerprints-to-adjust-s-allowlist}

<Callout type="note">

Remember to add all certificate fingerprints you want to use to the Adjust suite. This might include debug versions and versions for different stores.

</Callout>

Once you’ve obtained your certificate fingerprints, do the following to add them to your allowlist:

1. Select your app in AppView to open the app details screen.
2. Select the **Protection** tab.
3. Select the **Edit** button on the **Suspicious installs** section.
4. Under the **Android fingerprinting** section, select **New fingerprint**.
5. Paste the SHA-1 fingerprint into the text box that appears.
6. Select **Add**.
Follow these steps to retrieve and configure your certificate fingerprints:

That’s it! Your fingerprint is now allowlisted for your app.
1. [Retrieve Android certificate fingerprints](/en/sdk/android/integrations/retrieve-certificate-fingerprints)
2. [Configure them in the Adjust dashboard](https://help.adjust.com/en/article/sdk-signature#add-signatures-in-the-adjust-suite)

## Test your app {#test-your-app}

Expand Down
Loading