Skip to content

Commit eb111c8

Browse files
committed
some minor changes
1 parent 0c213a9 commit eb111c8

1 file changed

Lines changed: 24 additions & 13 deletions

File tree

‎_posts/2023-05-14-tak-server-install-centos.md‎

Lines changed: 24 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -103,9 +103,11 @@ This will generate the rpm image for you.
103103

104104
scp of ftp or sftp the downloaded .rpm file from tak.gov to your server.
105105

106+
`sftp <user>@<tak-server-ip>`
107+
106108
-------------------------------------------------
107109

108-
If you built from source run do the following:
110+
**If you built from source run do the following:**
109111

110112
```bash
111113
cd Server/src/takserver-package/build/distributions
@@ -117,14 +119,16 @@ In here you should see the server rpm:
117119

118120
At the time of writing this my rpm is `takserver-4.5-RELEASE72.noarch.rpm`
119121

120-
Run
122+
-----------------------------------------------
123+
124+
Both approaches follow the same steps:
125+
126+
Then install the .rpm by running the following command.
121127

122128
```bash
123129
sudo yum install takserver-4.5-RELEASE72.noarch.rpm
124130
```
125131

126-
-----------------------------------------------
127-
128132
# Setup DB
129133

130134
There is a db install script pre-made that you will have to run.
@@ -159,10 +163,10 @@ sudo su tak
159163

160164
Then create env variables:
161165
```bash
162-
export STATE=NY
163-
export CITY=NYC
164-
export ORGANIZATION=my-organizaton
165-
export ORGANIZATIONAL_UNIT=my-unit
166+
export STATE=<state>
167+
export CITY=<city>
168+
export ORGANIZATION=<my-organizaton>
169+
export ORGANIZATIONAL_UNIT=<my-unit>
166170
```
167171

168172
Navigate to
@@ -174,8 +178,7 @@ Then run
174178
```bash
175179
./makeRootCa.sh
176180
```
177-
178-
Give a name for your CA: example-name
181+
It will ask you to give a name for your CA: `example-name`
179182

180183
Create a server certificate:
181184

@@ -199,20 +202,29 @@ Generate an admin cert to gain access to the admin UI.
199202
```bash
200203
./makeCert.sh client admin
201204
```
205+
## Verify Certs
206+
In the `/opt/tak` directory open up the `coreConfig.xml`.
202207

208+
You should see a `<security>` section like this. Verify that the `keystoreFile` and `trustoreFile` match the output from the `generate CA` step.
209+
```xml
210+
<security>
211+
<tls keystore="JKS" keystoreFile="certs/files/takserver.jks" keystorePass="atakatak" truststore="JKS" truststoreFile="certs/files/truststore-root.jks" truststorePass="atakatak" context="TLSv1.2" keymanager="SunX509"/>
212+
</security>
213+
```
203214

204215
## Reload
216+
Stay logged in as the tak user when completing these commands
205217

206218
After you have created the certs restart the TAK Server.
207219

208220
```bash
209-
sudo systemctl restart takserver
221+
systemctl restart takserver
210222
```
211223

212224
Then authorize the admin cert.
213225

214226
```bash
215-
sudo java -jar /opt/tak/utils/UserManager.jar certmod -A /opt/tak/certs/files/admin.pem
227+
java -jar /opt/tak/utils/UserManager.jar certmod -A /opt/tak/certs/files/admin.pem
216228
```
217229

218230

@@ -223,7 +235,6 @@ Also, the generated CA trustores and certs will be here:
223235
```
224236

225237

226-
227238
# Firewall
228239
Setup the following firewall rules:
229240
```bash

0 commit comments

Comments
 (0)