-
Notifications
You must be signed in to change notification settings - Fork 85
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.
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
Sign-in with stacks #70
base: main
Are you sure you want to change the base?
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,91 @@ | ||
# Preamble | ||
|
||
SIP Number: X | ||
|
||
Title: Sign In With Stacks | ||
|
||
Author: Friedger Müffke ([email protected]), Leo Pradel | ||
|
||
Consideration: Technical | ||
|
||
Type: Standard | ||
|
||
Status: Draft | ||
|
||
Created: 18 May 2022 | ||
|
||
License: CC0-1.0 | ||
|
||
Sign-off: | ||
|
||
Layer: Applications | ||
|
||
Discussions-To: https://github.com/stacksgov/sips | ||
|
||
# Abstract | ||
|
||
Web application often provide their services only to authenticated users. In | ||
Web2, this was done through username and password or federated logins. In Web3, | ||
users can proof their digital identity by cryptographically signing that the | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. typo: "prove" |
||
user ownes the private key associated with that digital identity. | ||
|
||
SIP-018 defines the structure of signatures in general. This SIP defines the | ||
message format that web applications and similar off-chain services should use for their users to sign. | ||
|
||
# License and Copyright | ||
|
||
This SIP is made available under the terms of the Creative Commons CC0 1.0 Universal license, available at https://creativecommons.org/publicdomain/zero/1.0/ | ||
This SIP’s copyright is held by the Stacks Open Internet Foundation. | ||
|
||
# Introduction | ||
|
||
# Specification | ||
|
||
Sign-In with Stacks works as follows: | ||
|
||
1. The wallet presents the user with a structured message as defined in SIP-018. The message is a clarity value of type `tuple` with the properties described below. | ||
2. The signature is then presented to the server, which checks the signature’s validity and message content. | ||
3. Additional fields, including expiration-time, not-before, request-id, chain-id, and resources may be incorporated as part of authentication for the session. | ||
4. The server may further fetch data associated with the public key, the stacks address, or other data sources that may or may not be permissioned. | ||
|
||
## Properties | ||
|
||
| name | type | description | | ||
| --------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| title | (string-ascii 126) | Must be the application's domain name (max 80) followed by ` wants you to sign in with your Stacks account` | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. if going with domain name, shouldn't title then follow domain name limitations, ie 253 characters in size. Also, why |
||
| address | principal | The address of the signer | | ||
| statement | (string-ascii 80) | (optional) Describes the terms and conditions the user agrees to by using the application. | | ||
| URI | (string-ascii 80) | An RFC 3986 URI referring to the resource that is the subject of the signing (as in the subject of a claim). | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is 80 characters enough for a URL? Shouldn't it be more like 4,096? |
||
| version | uint | is the current version of the message, which MUST be X for this specification. | | ||
| chain-id | uint | (optional) the chain ID to which the session is bound. This must correspond to the version of the address. | | ||
| nonce | (string-ascii 64) | randomized token used to prevent replay attacks, at least 8 alphanumeric characters. | | ||
| issued-at | (string-ascii 27) | The ISO 8601 datetime string of the current time. | | ||
| expiration-time | (string-ascii 27) | (optional) The ISO 8601 datetime string that, if present, indicates when the signed authentication message is no longer valid. | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. One of the tricky things with authentication tokens like this is making sure they can't be replayed by someone who captures them. Is there a way we can mandate |
||
| not-before | (string-ascii 27) | (optional) The ISO 8601 datetime string that, if present, indicates when the signed authentication message will become valid. | | ||
| request-id | (string-ascii 64) | an system-specific identifier that may be used to uniquely refer to the sign-in request. | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. request-id should be optional too @friedger |
||
| resources | (list 10 (string-ascii 80)) | (optional) A list of information or references to information the user wishes to have resolved as part of authentication by the relying party. They are expressed as RFC 3986 URIs | | ||
|
||
## Presentation and Localization | ||
|
||
TODO | ||
|
||
# Related work | ||
friedger marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
## Ethereum EIP4361 | ||
|
||
[Ethereum EIP4361 standard](https://eips.ethereum.org/EIPS/eip-4361) | ||
|
||
## DID Auth | ||
|
||
[DID Auth Working | ||
group](https://identity.foundation/working-groups/authentication.html) | ||
|
||
[OpenID Connect for Verifiable Presentations](https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0.html) | ||
|
||
# Backwards Compatibility | ||
|
||
Not applicable | ||
|
||
# Activation | ||
|
||
TODO |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: "applications"