nhyatt/bitwarden
1
0
Fork 0
mirror of https://github.com/bitwarden/server.git synced 2025-04-05 13:08:17 -05:00
Code

Add quickfix for problem with src/Identity (#1201)

Browse Source
This commit is contained in:
João Miguel Campos 2021-03-11 16:00:17 +00:00 committed by GitHub
parent df7a035d9b
commit 52d29aef94
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 23 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
CONTRIBUTING.md
View File

@ -174,10 +174,10 @@ This is an example user secrets file for both the Api and Identity projects.
"globalSettings": { "globalSettings": {
"selfHosted": true, "selfHosted": true,
"identityServer": { "identityServer": {
"certificateThumbprint": "<your Identity certificate thumbprint>" "certificateThumbprint": "<your Identity certificate thumbprint with no spaces>"
}, },
"dataProtection": { "dataProtection": {
"certificateThumbprint": "<your Data Protection certificate thumbprint>" "certificateThumbprint": "<your Data Protection certificate thumbprint with no spaces>"
}, },
"installation": { "installation": {
"id": "<your Installation Id>", "id": "<your Installation Id>",
@ -190,6 +190,26 @@ This is an example user secrets file for both the Api and Identity projects.
} }
} }
``` ```
### Possible setup error in `src/Identity`
You may encounter an `Invalid licensing certificate` when running the command `dotnet run` in the project `src/Identity`, like this one:
```console
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
User profile is available. Using '/Users/<username>/.aspnet/DataProtection-Keys' as key repository; keys will not be encrypted at rest.
info: IdentityServer4.Startup[0]
Starting IdentityServer4 version 4.0.4+1b36d1b414f4e0f965af97ab2a7e9dd1b5167bca
crit: Microsoft.AspNetCore.Hosting.Diagnostics[6]
Application startup exception
System.Exception: Invalid licensing certificate.
```
As a quick fix, navigate to [`src/Core/Services/Implementations/LicensingService.cs`](https://github.com/bitwarden/server/blob/df7a035d9bdbee40e019a596a1a7a66826db02f4/src/Core/Services/Implementations/LicensingService.cs#L49), line 49, and change that line to
```cs
var certThumbprint = !environment.IsDevelopment() ? "207E64A231E8AA32AAF68A61037C075EBEBD553F" :
"‎B34876439FCDA2846505B2EFBBA6C4A951313EBE";
```
⚠️ Do not commit this change, as it might ruin the experience for others.
## Running and Debugging ## Running and Debugging
After you have completed the above steps, you should be ready to launch your development environment for the Api and Identity projects. After you have completed the above steps, you should be ready to launch your development environment for the Api and Identity projects.
@ -219,4 +239,4 @@ From within Rider, launch both the Api project and the Identity project by click
* If you are using the CLI client, you will also need to set the Node environment variables for your self-signed certificates by following the instructions here: [The Bitwarden command-line tool (CLI) > Self-signed certificates](https://bitwarden.com/help/article/cli/#self-signed-certificates). * If you are using the CLI client, you will also need to set the Node environment variables for your self-signed certificates by following the instructions here: [The Bitwarden command-line tool (CLI) > Self-signed certificates](https://bitwarden.com/help/article/cli/#self-signed-certificates).
### Troubleshooting ### Troubleshooting
* If you get a 404 error, the projects may be listening on a non-default port. Check the output of your running projects to check the port they are listening on. * If you get a 404 error, the projects may be listening on a non-default port. Check the output of your running projects to check the port they are listening on.