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: docs/deployment-window-iis.md
+54-6Lines changed: 54 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,8 @@ This deployment include:
18
18
19
19
- Two websites one for FoxIDs and one for the FoxIDs Control (Admin Client and API).
20
20
- The two websites are exposed on two different domains / sub-domains.
21
-
- NoSQL database containing all data including tenants, environments and users. Either deploy [MongoDB Community Edition](https://www.mongodb.com/docs/manual/tutorial/install-mongodb-on-windows/) or [PostgreSQL](https://www.postgresql.org/download/windows/).
21
+
- NoSQL database containing all data including tenants, environments and users. Either deploy **MongoDB Community Edition** or **PostgreSQL**.
22
+
- FoxIDs logs are default saved in files. Depending on the load, consider to use [OpenSearch](#opensearch) in production.
22
23
23
24
## Deployment
24
25
@@ -94,11 +95,11 @@ Download the `win-acme.v2.x.x.x64.pluggable.zip` file from the latest [win-acme
94
95
95
96
The two websites now have `https` bindings with the certificate created by Let's encrypt and the certificate will automatically be updated for every 3 months or so.
96
97
97
-
### Add FoxIDs to the websites
98
+
### Xcopy deploy FoxIDs to websites
98
99
Download the `FoxIDs-x.x.x-win-x64.zip` file from the [FoxIDs release](https://github.com/ITfoxtec/FoxIDs/releases) and unpack the ZIP file. The zip file contains two folders one for the FoxIDs site and one for the FoxIDs Control site.
99
100
100
-
- Copy the zip file folder FoxIDs into the websites physical path e.g. `C:\inetpub\FoxIDs`
101
-
- And copy the zip file folder FoxIDs.Control into the websites physical path e.g. `C:\inetpub\FoxIDs.Control`
101
+
- Xcopy the zip file folder FoxIDs into the websites physical path e.g. `C:\inetpub\FoxIDs`
102
+
- And Xcopy the zip file folder FoxIDs.Control into the websites physical path e.g. `C:\inetpub\FoxIDs.Control`
102
103
103
104
Configure both the FoxIDs site and the FoxIDs Control site in the `appsettings.json` files, located in e.g. `C:\inetpub\FoxIDs\appsettings.json` and `C:\inetpub\FoxIDs.Control\appsettings.json`
104
105
@@ -128,15 +129,62 @@ Configure both the FoxIDs site and the FoxIDs Control site in the `appsettings.j
FoxIDs log files are default saved in `C:\inetpub\logs\LogFiles`. You can change the path in the `web.config` file in the two websites.
138
139
139
-
The logs contain errors, warnings, events and trace. Depending on the load, consider using [OpenSearch](https://docs.opensearch.org/docs/latest/install-and-configure/install-opensearch/windows/) in production.
140
+
The logs contain errors, warnings, events and trace.
141
+
142
+
### OpenSearch
143
+
Depending on the load, consider to use OpenSearch in production instead of log files.
144
+
145
+
Download [OpenSearch](https://docs.opensearch.org/docs/latest/install-and-configure/install-opensearch/windows/) or download from the [download page](https://opensearch.org/downloads/).
146
+
147
+
1. Create a folder on a permanent place e.g. `C:\opensearch` on the C drive. The OpenSearch `.bat` file is subsequently registered to run in Windows Task Scheduler.
148
+
2. Move the downloaded file `opensearch-x.x.x-windows-x64.zip` to the folder and unpack the file - *the file names are to log to unpack in the default download folder*
149
+
3. Start a Command Prompt
150
+
4. Navigate to the `opensearch-x.x.x` folder
151
+
5. Set an administrator password, run `set OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password>`
152
+
6. Start service, run `.\opensearch-windows-install.bat`
153
+
7. Start another Command Prompt
154
+
8. Test the OpenSearch, run test request `curl.exe -X GET https://localhost:9200 -u "admin:<custom-admin-password>" --insecure`
155
+
9. Test the OpenSearch plugins, run test request `curl.exe -X GET https://localhost:9200/_cat/plugins?v -u "admin:<custom-admin-password>" --insecure`
156
+
10. Go back to the OpenSearch Command Prompt and stop OpenSearch by clicking `ctrl+c` and then `y`
157
+
158
+
Create a task to rune OpenSearch
159
+
1. Open **Task Scheduler**
160
+
2. Click **Create Task...**
161
+
3. Add the **Name** `OpenSearch`
162
+
4. Change the account that run the task, click **Change User or Group...**
163
+
5. Write `NETWORK SERVICE` and click **OK**
164
+
6. Select the **Actions** tab
165
+
7. Click **New...**
166
+
8. In **Program/script** start the `.bat` file e.g., write `C:\opensearch\opensearch-x.x.x\opensearch-windows-install.bat` and click **OK**
167
+
9. Select the **Settings** tab
168
+
10. Select the setting **If the task fails, restart every:**
169
+
11. Deselect the setting (remove the checkmark) **Stop the task if it runs longer then:**
170
+
12. Click **OK**
171
+
13. Start the task
172
+
173
+
OpenSearch is default started with a self-signed certificate. You can configure a domain and a certificate but, in this guide, the self-signed certificate is retained and FoxIDs is configured to accept the certificate.
174
+
175
+
Configure OpenSearch in both the FoxIDs site and the FoxIDs Control site in the `appsettings.json` files, located in e.g. `C:\inetpub\FoxIDs\appsettings.json` and `C:\inetpub\FoxIDs.Control\appsettings.json`
Open your FoxIDs Control site (<a href="http://control.my-domain.com" target="_blank">http://control.my-domain.com</a> or <a href="https://control.my-domain.com" target="_blank">https://control.my-domain.com</a>) in a browser.
Copy file name to clipboardExpand all lines: docs/risk-passwords.md
+18-14Lines changed: 18 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,20 +4,20 @@ You can achieve higher password quality and a higher level of security by using
4
4
5
5
Hundreds of millions of real world passwords previously exposed in data breaches is collected as risk passwords. By validating that the leaked passwords are not reused, you significantly increase the level of password security.
6
6
7
-
**1) Download risk passwords (pwned passwords)**
7
+
> The risk passwords are uploaded ones per FoxIDs deployment in the master tenant and can be used in all tenants and environments.
8
+
9
+
10
+
## 1) Download risk passwords (pwned passwords)
8
11
Download the `SHA-1` pwned passwords in a single file from [haveibeenpwned.com/passwords](https://haveibeenpwned.com/Passwords) using the [PwnedPasswordsDownloader tool](https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader).
9
12
10
13
> Be aware that it takes some time to download all risk passwords.
11
14
12
-
**2) Upload risk passwords to FoxIDs**
13
-
You can upload risk passwords with the FoxIDs seed tool console application. The seed tool code is [downloaded](https://github.com/ITfoxtec/FoxIDs/tree/master/tools/FoxIDs.SeedTool) and need to be compiled and [configured](#configure-the-seed-tool) to run.
14
-
15
-
> The risk passwords is uploaded ones per FoxIDs deployment in the master tenant.
15
+
## 2) Upload risk passwords to FoxIDs
16
+
You then upload the risk passwords with the FoxIDs seed tool console application.
16
17
17
-
**3) Test**
18
-
You can read the number of risk passwords uploaded to FoxIDs in [FoxIDs Control Client](control.md#foxids-control-client) master tenant on the Settings / Risk Passwords tap. And you can test if a password is okay or has appeared in breaches.
18
+
Download the `FoxIDs.SeedTool-x.x.x-win-x64.zip` or `FoxIDs.SeedTool-x.x.x-linux-x64.zip` file from the [FoxIDs release](https://github.com/ITfoxtec/FoxIDs/releases) and unpack the seed tool.
19
19
20
-
## Configure the Seed Tool
20
+
###Configure the Seed Tool
21
21
22
22
The seed tool is configured in the `appsettings.json` file.
23
23
@@ -51,18 +51,22 @@ Add your FoxIDs and FoxIDs Control API endpoints and client secret and local ris
Run the seed tool executable SeedTool.exe or run the seed tool directly from Visual Studio.
68
+
> The risk password upload will take a while.
65
69
66
-
* Click 'p' to start uploading risk passwords
70
+
## 3) Test
71
+
You can read the number of risk passwords uploaded to FoxIDs in [FoxIDs Control Client](control.md#foxids-control-client) master tenant on the Settings / Risk Passwords tap. And you can test if a password is okay or has appeared in breaches.
0 commit comments