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
+16-11Lines changed: 16 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,22 @@
1
1
# Secure User Property Store for RTC
2
-
3
-
> TODO: introduction, make a cross reference to git commit picker
2
+
This plugin is used to store additional properties that are associated to an RTC user account in a secure manner. It is used by the [RTC Git Connector](https://github.com/jazz-community/rtc-git-connector) project to store the _Personal Access Token_ that is needed to access GitLab data. The service uses strong, tamper-proof cryptography to make sure that stored information is safe. It uses a built-in mechanism of the Jazz Platform the information directly into the database.
4
3
5
4
## Setup Instructions
6
-
The most convenient way to install this service is to download the current stable release from the [Releases](https://github.com/jazz-community/rtc-secure-user-property-store/releases) page.
5
+
The most convenient way to install this service is to download the current stable release from the [Releases](https://github.com/jazz-community/rtc-secure-user-property-store/releases) page. If you not already know, head over to the [RTC Git Connector](https://github.com/jazz-community/rtc-git-connector) page to learn how to install RTC plug-ins (it's always the same procedure).
6
+
7
+
Once the plug-in is installed and the server rebooted, open the **Advanced Properties** page of your server and scroll down to the following section that allows to configure this service. Specify a _16 digit_ private key that is used for encrpytion.
8
+

7
9
8
-
> TODO: installation and Advanced Properties Configuration instructions
10
+
Important notes:
11
+
- Without providing a private key, the service will not wwork
12
+
- Do not share this key with anyone except a secure password manager, you may want to keep it for restore scenarios
13
+
- Make sure that the private key is absolutely random so that no one could guess it
9
14
10
15
## API Reference
11
16
This section contains the API definition for this project. While we try to do our best to keep this accurate, it is always best to have a look at the code in order to make sure that everything is covered.
12
17
13
18
### base path
14
-
You'll see the term `<root>` within the following API doc a few times. It represents the root (or base) path for this service. Assuming that your CCM server is being referred to as `localhost:7443/ccm`, the `<root>` path for this service is the following:
19
+
You'll see the term `BASE` within the following API doc a few times. It represents the root (or base) path for this service. Assuming that your CCM server is being referred to as `localhost:7443/ccm`, the `BASE` path for this service is the following:
0 commit comments