Password-protect notes

[diogomiloco]

Is your feature request related to a problem? Please describe.
Some notes may be sensitive, IE. Internal company documentation, business notes, personal health data and such. It would be really useful to be able to protect some pages or group of pages so they don't appear to everyone, while still allowing them to be published.

Describe the solution you'd like
To password-protect some routes so I can use a deployment on a public URL without exposing selected sensitive items

Describe alternatives you've considered

• User Logins - Would be too complex and would require back-end logic, DBs and session management
• Using a VPC - Will be the fallback, however this service has a cost and setup, wouldn't work if someone is not in the VPC (visitors)
• Hiding items - Wouldn't allow anyone to see the notes but is a compromise
• Not using env variable - using the file's metadata to create page-specific passwords - this would be more complex than the simplest use case

Additional context
Being able to pass an environment variable on build time that would generate an encrypted hash in the header of each 'protected' page. If someone tries to access a note that has the 'protected' property, this password would be prompted. On successful input, the 'authorized' flag would be saved on the user's browser for the future. Would also put a configurable time-to-expire env configuration.

[jackyzha0]

Closed as duplicate of #630

[dynamotn]

@jackyzha0 I want to have this ability to protect some pages, but I have another approach: password for each Markdown file in frontmatter. I assumed that you're welcome PR for this feature.
Besides that, I'm researching about using JWT with OpenID Connect to encrypt/decrypt page by key pair.
Let me know if you hope to resolve this ticket.