Skip to content

Commit 6486387

Browse files
authored
complete project documentation
closes #1
1 parent 3060ad4 commit 6486387

File tree

1 file changed

+16
-11
lines changed

1 file changed

+16
-11
lines changed

README.md

Lines changed: 16 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,22 @@
11
# 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.
43

54
## 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+
![Work Item Bulk Mover Version 1.0.0 demonstration](https://github.com/jazz-community/rtc-secure-user-property-store/blob/master/private_key_setup_in_AdvancedProperties.PNG)
79

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
914

1015
## API Reference
1116
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.
1217

1318
### 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:
1520

1621
> https://localhost:7443/ccm/service/com.siemens.bt.jazz.services.PersonalTokenService.IPersonalTokenService
1722
@@ -20,13 +25,13 @@ This will add a new entry for the currently logged-in user to the token store. <
2025
The implementing application must somehow remember the `key` of a user as it is required to get the `token` of the user.
2126

2227
**Request URL**
23-
> POST <root>/tokenStore
28+
> POST `BASE`/tokenStore
2429
2530
**Example Request Body**
26-
```
31+
```javascript
2732
{
2833
"key": "gitlab.com",
29-
"token": "<this is my secure github accees token>"
34+
"token": "<this placeholder would hold my secret personal access token for GitLab (or any other service)>"
3035
}
3136
```
3237

@@ -43,7 +48,7 @@ The implementing application must somehow remember the `key` of a user as it is
4348
Read the token associated to the passed in `key` for the currently logged-in user.
4449

4550
**Request URL**
46-
> GET <root>/tokenStore?key=`key`
51+
> GET `BASE`/tokenStore?key=`gitlab.com`
4752
4853
**Response Status Code**
4954

@@ -55,9 +60,9 @@ Read the token associated to the passed in `key` for the currently logged-in use
5560
| 500 | An internal server error has occured. Review the CCM log file to find more information |
5661

5762
**Response Body**
58-
```
63+
```javascript
5964
{
60-
"token": "<this is my secure github accees token>"
65+
"token": "<this is my secure GitLab accees token>"
6166
}
6267
```
6368

0 commit comments

Comments
 (0)