You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think Dotlicense could be used in a web context for SaaS apps. If you used a Metamask/signing-based login then you could use that proof of ownership to verify an active subscription.
For example, see meta-auth for a Metamask-based login with Node middleware. (Note: I haven't tried meta-auth and I can't vouch for it's security, but I think it's an interesting idea.)
This could work with Dotlicense like this:
The user has paid for a subscription-token on-chain
For a user to log in they sign a challenge, proving they own the given address (and the webserver sets a cookie so that this only has to be done as often as you would log in normally)
The webserver now knows the identity of the user, as well as the user's ETH address. This means the webserver can check on-chain if the user's subscription is valid and unlock features accordingly.
As of writing, I haven't built any of the supporting Web UI libraries nor the Node middleware, but once we have Dotlicense working, it should be straightforward to do this.
The text was updated successfully, but these errors were encountered:
I think Dotlicense could be used in a web context for SaaS apps. If you used a Metamask/signing-based login then you could use that proof of ownership to verify an active subscription.
For example, see meta-auth for a Metamask-based login with Node middleware. (Note: I haven't tried
meta-auth
and I can't vouch for it's security, but I think it's an interesting idea.)This could work with Dotlicense like this:
As of writing, I haven't built any of the supporting Web UI libraries nor the Node middleware, but once we have Dotlicense working, it should be straightforward to do this.
The text was updated successfully, but these errors were encountered: