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
EIT-3686 - Add access control information in platforms > products section and ce… (#4)
* add access control information in platforms > products section and certifier access control information
* fix lint errors
* update CI lint workflow
* update CI
---------
Co-authored-by: marcbaque <marc@bloock.com>
Copy file name to clipboardExpand all lines: docs/guides/platform/certifier.mdx
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,14 @@ The final step of the process involves users controlling access through Encrypti
45
45
46
46
Once you've completed the necessary setup steps, you can finalize the process by following these straightforward instructions. The system will then proceed to process the selected documents.
If the user signs and/or encrypts managed keys or certificates assigned access control, you should add the corresponding code after completing the process.
51
+
52
+
Depending on the products activated during the process and where a key with access control has been used, one or two fields will appear to complete: one for signing and the other for encryption.
53
+
54
+
If it's a key with access control via TOTP, the user should enter the temporary code displayed in the authentication app. The user should add the relevant password if access control is done through a Secret.
Files with a decentralized timestamp undergo a status transition from "pending" to "success" after being registered on the blockchain—an operation typically taking approximately one minute. Details screen and Verify link become available upon reaching the "success" status.
## Managed Keys[](https://docs.bloock.com/guides/platform/products/#managed-keys'Direct link to Managed Keys')
107
107
108
108
The Key Management Product ensures the security of private keys and certificates, safeguarding authentication credential safety. It enables precise access control and maintains a comprehensive audit trail for enhanced security. For a deeper understanding of this product, you can explore the Key Management section.
109
109
@@ -135,6 +135,92 @@ On the certificate details screen, users can view generic information about the
BLOOCK allows adding access controls to manage keys and certificates. To learn more about how access controls work, [please refer to this section](https://docs.bloock.com/guides/products/key/concepts/access-control/#secret-based-authentication).
141
+
142
+
**_Add Access Control_**
143
+
144
+
You can add an access control both at the time of key and certificate creation and through the "Key Details" section.
145
+
146
+
**Key and certificate creation form:**
147
+
148
+
At the bottom of the creation form, there are different access control options. Currently, options include Time-Based One-Time Password (TOTP) or Secret-based Authentication:
To utilize this functionality, you can use apps and browser extensions like 1Password, Google Authenticator, and Microsoft Authenticator, which generate one-time passwords used as a second factor to verify your access to this key.
159
+
160
+
Scan the generated QR code using any of the mentioned applications or manually enter the code provided at the bottom. Additionally, there are recovery codes in case the user loses access to the key.
> Note: It's important to save these recovery codes as BLOOCK does not store this information.
165
+
166
+
-**Secret-based Authentication:**
167
+
168
+
When selecting the Secret-based option, a form will appear with a secret field, which should be the code used for any operation with the access key and a field for a recovery email to retrieve the key if the user loses access to it.
In the top right corner of the key and certificate details page, you can find a dropdown menu to perform different actions, to add access control to this key, select the "+ Add access control" button.
Once this functionality is selected, a dropdown will appear on the right side of the screen where you can choose the type of access control, either Secret or TOTP.
179
+
180
+
-**Secret-based Authentication:**
181
+
182
+
When selecting the Secret-based option, a form will appear with a secret field. This secret will work as the code used for any operation with the access key and a field for a recovery email to recover the key if you lose access to it.
When selecting the TOTP option and confirming by clicking the "Next" button, information for operating with the key via access control will appear:
189
+
190
+
To utilize this functionality, you can use apps and browser extensions like 1Password, Google Authenticator, and Microsoft Authenticator, which generate one-time passwords that are used as a second factor to verify your access to this key.
191
+
192
+
Scan the generated QR code using any of the mentioned applications or manually enter the code provided at the bottom. Additionally, there are recovery codes in case the user loses access to the key.
If you wish to edit the access control of the key, select the "Edit Access Control" option from the dropdown menu on the key or certificate details screen. To proceed with the process, you will need to enter the "Secret" of the key if it is of the secret-based type.
If you want to change the secret of your key, you can select the "Reset Secret Password" option from the dropdown menu. Once you select this option, a window will appear for the change process, where you'll need to confirm that you want to proceed with this operation.
In the last tab of the Managed Keys section, we find the different signature operations carried out by the user in a general manner, along with information regarding them: The type of action (Signature, Verification, Encryption, and Decryption), the transaction ID, the name of the key or certificate used, the date of the operation, and the IP address where this operation took place.
0 commit comments