Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Define keystore signature calculation algorithm

Open
#57 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, java

Research direction

The issue does not name a documentation file or test. Review the existing Android keystore and signature instructions first, then verify the proposed command and its binary SHA-1 to Base64 step; it is done when the documentation states the confirmed command and answers that question.

Written by the indexing model from the issue text.

Description

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Expected/desired behavior

Please provide exact Android keystore signature generation command in docs.

keytool -exportcert -alias [aliasname] -keystore [your app keystore path] | openssl sha1 -binary | openssl base64

Please confirm, if above command is correct.
Specifically, should base64 be generated from binary form of sha1?


Thanks! We'll be in touch soon.

Dominant language
Java
Stars
34
Forks
30
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure-Samples/ms-identity-android-java

All issues in Azure-Samples/ms-identity-android-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.