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
Copy file name to clipboardExpand all lines: README.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -467,7 +467,7 @@ plugins:
467
467
### Share link generation
468
468
469
469
It is possible to share valid credentials by adding them to the hash part of the URL.
470
-
The plugin can also generate share links for certain pages if the metag tag `sharelink: true`
470
+
The plugin can also generate share links for certain pages if the meta tag `sharelink: true`
471
471
is defined in markdown.
472
472
It will use the first credential for the pages level or the pages password.
473
473
The credentials for auto-generated links are base64url encoded.
@@ -487,6 +487,17 @@ However if `sharelinks: True` is enabled in the plugin configuration you can gen
487
487
> Then another condition applies: If non-aphanumeric characters are used in user/password,
488
488
> they need to be URLencoded (f.ex. %20 = space character). Some browsers may do that automatically (Do a copy/paste from the browsers address bar then).
489
489
490
+
#### Incomplete Share links
491
+
492
+
Since version 3.0.3 it is possible to leave out one part of the password when share links are generated via meta tag.
493
+
To do this use the ":" character in a password to divide the part that is incorporated to the share link and the part that remains secret,
494
+
like "PartThatIsEncodedToTheShareLink:PartThatRemainsSecret".
495
+
The feature is enabled by setting the option `sharelinks_incomplete: true`.
496
+
If the password that is read from the share link ends with the ":" character, then an additional password input field is displayed for entering the secret part.
497
+
498
+
> If the feature is used, then passwords must not end with the ":" character.
499
+
500
+
490
501
### Storage of additional variables in keystore
491
502
492
503
Since version 3.0.3 it is possible to set arbitrary session store variables after decryption.
Copy file name to clipboardExpand all lines: documentation/docs/features/index.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,7 @@ plugins:
124
124
### Share link generation
125
125
126
126
It is possible to share valid credentials by adding them to the hash part of the URL.
127
-
The plugin can also generate share links for certain pages if the metag tag `sharelink: true`
127
+
The plugin can also generate share links for certain pages if the meta tag `sharelink: true`
128
128
is defined in markdown.
129
129
It will use the first credential for the pages level or the pages password.
130
130
The credentials for auto-generated links are base64url encoded.
@@ -144,6 +144,17 @@ However if `sharelinks: True` is enabled in the plugin configuration you can gen
144
144
> Then another condition applies: If non-aphanumeric characters are used in user/password,
145
145
> they need to be URLencoded (f.ex. %20 = space character). Some browsers may do that automatically (Do a copy/paste from the browsers address bar then).
146
146
147
+
#### Incomplete Share links
148
+
149
+
Since version 3.0.3 it is possible to leave out one part of the password when share links are generated via meta tag.
150
+
To do this use the ":" character in a password to divide the part that is incorporated to the share link and the part that remains secret,
151
+
like "PartThatIsEncodedToTheShareLink:PartThatRemainsSecret".
152
+
The feature is enabled by setting the option `sharelinks_incomplete: true`.
153
+
If the password that is read from the share link ends with the ":" character, then an additional password input field is displayed for entering the secret part.
154
+
155
+
> If the feature is used, then passwords must not end with the ":" character.
156
+
157
+
147
158
### Storage of additional variables in keystore
148
159
149
160
Since version 3.0.3 it is possible to set arbitrary session store variables after decryption.
0 commit comments