-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
34 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Profile | ||
|
||
VAuthenticator can be configured to be strongly AWS integrated using DynamoDB for the persistence layer and KMS for Key management. | ||
|
||
If your organization or for you run VAuthenticator so tiny integrated with AWS does not is suitable you can decide to switch postgresql instead dynamodb for the persistence | ||
and plain java security key management instead of KMS | ||
|
||
All what you need is enable the relative spring profile as below: | ||
|
||
use ```spring.profiles.active``` with | ||
|
||
- ```database```: to use PostgresSQL | ||
- ```dynamo```: to use DyanamoDB | ||
- ```kms``` to use KMS | ||
- omitting ```kms``` to use plain java security api | ||
|
||
in case of plain java security implementation the follow configuration is required: | ||
|
||
|
||
```yaml | ||
key: | ||
master-key: | ||
storage: | ||
content: | ||
key : value | ||
key2 : value2 | ||
``` | ||