1.0.0-RC

[JesusMcCloud]

Discussion points:

• Default Nonce validity duration
• Is there more potential to simplify APIs and remove old stuff/reduce API surface?
• Do we want multiple Makoto Constructors to ensure that at least iOS or Android is enabled, or do we just throw if both configs passed are null and expose the constructor with two nullable parameters?

TODOs:

• Testing (see below)
• Wait for info on SW roots and amend docs (and potentially code) accordingly
• Full migration guide wrt. config changes and API changes
• Docs and API docs proof reading (General task)
• Social Previews for all pagesSocial Preview for docs #38
• Exceptions
  • Check for exception annotations where required (constructors)
  • In particular, re-evaluate configuration exception
  • Re-evaluate exceptions throws during initialisations
  • Make sure internal errors are really always bugs and always add a link to creating an issue to the message

Testing:

• Test contracts (semantically, not Kotlin Contracts) and explicitly document implicit contracts/behaviour
  • Supreme Verifier constructor params propagate correctly to Makoto and nonce checker
  • Exception Mapping (Makoto Exceptions to AttestationResponse.Error)
• ~~KeyConstraints are observed correctly Tests if KeyConstraints are observed correctly #39
• CSR attributes and CSR extensions are correctly encodedTest if CSR attributes and extensions are correctly encoded #40
• Auth prompts are correctly displayed check if Auth prompts are correctly displayed #41

[nodh]

Nice!