-
Notifications
You must be signed in to change notification settings - Fork 153
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
xAlias - overview, integration examples #797
Conversation
|
||
[comment]: # (mx-context-auto) | ||
|
||
## The Web Wallet Provider | ||
## The web wallet & xAlias provider |
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.
this will break the link to this section. might add a redirect on docusaurus.config.js
or leave the section title as it is
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.
Good catch, thanks 🙌
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.
Left the section title as it was.
|
||
Generally speaking, a signing provider is a component that supports the following use-cases: | ||
|
||
- **Login (trivial flow, not recommended)**: the user of a dApp is asked her MultiversX identity. The user reaches the wallet, unlocks it, and confirms the login. The flow continues back to the dApp, which is now informed about the user's blockchain address. Note, though, that this piece of information is not authenticated: the dApp receives a _hint_ about the user's address, not a _guarantee_ (proof). Sometimes (though rarely), this is enough. If in doubt, always have your users login using the **native authentication** flow (see below). |
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.
login->log in and logout->log out where needed
login/logout are nouns (for example: the login page)
log in/log out are actions (for example: please log in)
Description of the pull request (what is new / what has changed)
Document xAlias. Add integration notes.
Related to: multiversx/mx-sdk-js-examples#29.
Did you test the changes locally ?
Which category (categories) does this pull request belong to?