-
Notifications
You must be signed in to change notification settings - Fork 21
/
config.properties
173 lines (151 loc) · 7.43 KB
/
config.properties
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
# Configuration properties for the Account provisioning for Google Apps API.
# ==============================================================================
# Google API properties
# ==============================================================================
#
# **Note:** Follow the steps in the Google Apps domain configuration guide (CONFIG.md)
# to set these properties.
#
# The Google Apps domain.
# Example: apis.GoogleAPIs.domain=yourdomain.com
apis.GoogleAPIs.domain=
# Admin user who created the project in the Google Developer Console.
# Example:
apis.GoogleAPIs.authUser=
# The P12 file that stores the Google private key. Can be generated following the
# steps in: https://cloud.google.com/storage/docs/authentication#service_accounts
# Example:
# apis.GoogleAPIs.keyPath=./service_account_key.p12
apis.GoogleAPIs.keyPath=
# This value represents an internal user for server side applications and can be
# generated following the steps in:
# https://cloud.google.com/storage/docs/authentication#service_accounts
# There's an extra step to enable API scopes in the Google Admin Console
# This scopes can be registered following the steps in:
# https://support.google.com/a/answer/162106?hl=en
# And adding the following scope to your service account:
# https://www.googleapis.com/auth/admin.directory.user
# Example:
# apis.GoogleAPIs.serviceAccountEmail=1234567890123-abcdefghijklmnopqrstuvwxz01234567@developer.gserviceaccount.com
apis.GoogleAPIs.serviceAccountEmail=
# This value is the full project name in the Google Developer Console project name
# can be obtained following the steps in:
# https://developers.google.com/console/help/new/#creatingdeletingprojects
# Example: apis.GoogleAPIs.appName=My project
apis.GoogleAPIs.appName=
# ==============================================================================
# Username generation properties
# ==============================================================================
#
# In order to save API calls we can validate with cached accounts, if
# cachedUsernames value is set to YES this tool will validate with cache,
# if not it will use API calls (The possible values are: YES, NO, default: NO).
accounts.UsernameGeneration.cachedUsernames=YES
# This variable defines the expiration time in hours of the cached usernames.
# After expiration the application refreshes the username cache.
# For reference, refreshing an account with 1 million users takes approximately
# 35 minutes.
# (Default value: 24)
# Valid values: Integers larger or equal to 1
accounts.UsernameGeneration.cacheExpirationHours=24
# The number of username suggestions to be returned for each call to suggest.
# Possible values: 1-10
# Default: 3
accounts.UsernameGeneration.numberOfSuggestions=5
# The amount of time (in seconds) that suggested usernames will remain locked
# (unavailable to another client).
# Default: 2 minutes.
accounts.UsernameGeneration.suggestedUsernamesTimeout=120
# A pattern is something that looks like [firstname][lastname]. This pattern
# indicates the API that we want to generate a username with "the firstname
# followed by the lastname". Now, if that username happens to be taken the
# API will need another pattern. Therefore, a list of multiple patterns is
# recommended. For example:
# accounts.UsernameGeneration.patterns=[firstname][lastname],[lastname][firstname]
# This will first try to generate a username with "the firstname followed by
# the lastname" if that is taken then it will try to generate a username with
# "the lastname followed by the firstname".
# Now, say we want to generate a username with "the nickname followed by the
# lastname" of a person. We'd simply do:
# accounts.UsernameGeneration.patterns=[nickname][lastname]
# What's [nickname] you might ask?
# Well, nickname is a field that should be passed to the suggest method.
# For example:
# var parameters = '{' +
# '"firstname": "Jonathan",' +
# '"lastname": "Bravo",' +
# '"nickname": "Jonny"' +
#'}';
# This will generate the username jonnybravo.
# You can name nickname anything else as long as the key in the parameters
# passed to suggest and the key used in the pattern are the same.
#
# **Taking the first char(acters) of a field**
# Now say that for someone named John Smith we'd like to generate a username jsmith.
# We'd do it with the following pattern:
# [C1_firstname][lastname]
# C1 indicates that the API should take the first character of firstname. If we'd
# like to take the first two characters then we'd do:
# [C2_firstname][lastname]
# This same method applies for custom fields. For example, if we wanted to split
# the first character of the nickname we'd do:
# [C1_nickname]
#
# **Adding a counter to a pattern**
# Now, say we have so many people named "John Smith" in a school district that we
# ran out of patterns. We could then define a pattern that adds a number at the
# end of the username:
# [firstname][lastname][#]
# [#] indicates that a number will be added to the username. For example:
# johnsmith3
# This numeric value will start at 1 and continue adding until a username is
# available.
#
# **Adding separators to usernames**
# A common practice is to separate usernames with a period (.), an underscore
# (_) or a dash (-). These separators can be added to patterns. Example:
# [firstname].[lastname]
# would generate the username john.smith
#
# **Adding a string to a pattern**
# Same as the separators, it is possible to add a static string to username
# suggestions. For example, the pattern:
# [lastname]_nyc
# would generate the username smith_nyc
#
# **What if the API runs out of patterns?**
# The following pattern is used as the last resort:
# [C9_firstname][C9_lastname][#]
accounts.UsernameGeneration.patterns=[firstname][C1_lastname][C1_customfield],[firstname][C1_lastname][customfield],[C1_firstname].[lastname][C1_customfield],[C1_firstname].[lastname]_[customfield],[C1_firstname][lastname][C1_customfield],[firstname]_[lastname][C1_customfield],[C1_firstname]_[lastname][C1_customfield],[firstname][lastname],[C1_firstname][lastname],[firstname][C1_lastname],[C1_firstname].[lastname],[firstname]_[lastname],[firstname].[lastname]
# ==============================================================================
# SSL properties
# ==============================================================================
#
# Enables HTTPS support over SSL.
# (The possible values are: YES, NO, default: NO).
security.ssl.useSSL=NO
# Defines where the jks file is located.
# This can be generated executing the following command:
# keytool -genkey -alias sitename -keyalg RSA -keystore keystore.jks -keysize 2048
# If the file is placed in the same folder of jar file, you can use: ./keystore,jks
security.ssl.keyStorePath=
# Password provided when the jks file was generated.
# This value is required when useSSL is set to YES.
security.ssl.keyStorePassword=
# Commonly is the same as the key store, but it can change if it is not a
# self-generated certificate.
# This value is required when useSSL is set to YES.
security.ssl.keyManagerPassword=
# ==============================================================================
# Cache location properties
# ==============================================================================
#
# The name of the database where the cache is stored.
# This only applies when cacheUsernames is set to YES.
# (default: usernames).
db.h2.name=
# Path where the database files are stored.
# This only applies when cacheUsernames is set to YES.
# (default: ./).
db.h2.path=