3 ms·
Did you consider posting an issue on GH? my 2 cents: if you intend to secure the content then it cannot be delivered to the client, as in: you need to have a p
by piterrro 3y ago
Did you consider posting an issue on GH?
my 2 cents: if you intend to secure the content then it cannot be delivered to the client, as in: you need to have a password/token protected endpoint.
If it's just for the visuals then I guess you can prepare a Vue module that will prompt for a password before showing the content, then wrap a content within it.
<PasswordProtected :password="'foobar'">
This content will be displayed only after providing a password
</PasswordProtected>
- e12e 3y ago> if you intend to secure the content then it cannot be delivered to the client ... In plaintext. You could maybe wrap a kdf and a webcrypto thing in a Vue component - decrypting on the client by deriving a key from a user supplied password. It would almost certainly be a worse solution than basic auth on a normal web server...