-
Notifications
You must be signed in to change notification settings - Fork 0
/
db-1.0.json
253 lines (253 loc) · 11.7 KB
/
db-1.0.json
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
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
{
"issues": [
{
"assignee": null,
"component": null,
"content": "Create a new branch named for your portal, mascot, school, etc. Base this branch off of Jasig/master or one of the -patches branches (e.g. 'huskeynet').",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 1,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Create a private fork of uPortal",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": "database",
"content": "Add your JDBC driver to uportal-db/pom.xml. Provide complete or sample JDBC connection settings in filters/prod.properties. (Local dev environments should use the embedded HSQL database.)",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 2,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Configure database platform for server environments",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": "database",
"content": "Copy the uportal-war/src/main/data/quickstart_entities dataset into a sibling folder with the same name as your branch in Git (e.g. 'huskeynet'). Uncomment the 'quickstart_entities.location' property in build.properties.sample ad adjust it to the location of the new folder you created. FOR UPORTAL MIGRATIONS you will (probably) want to export some data from your current portal and add it to this folder. Which data to migrate is a matter of judgement and circumstance, but portlets, groups, and fragments are often migrated (though often 'tweaked' in-transit). Avoid migrating layouts of non-fragment users if you can.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 3,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Create implementation dataset",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": "database",
"content": "The uPortal quickstart dataset includes demo user accounts with demo passwords (e.g. 'admin/admin'). You don't want any of these to leak into production. Find all <password> elements in *.user.xml files within uportal-war/src/main/data and remove them. OPTIONALLY you can provide passwords like these in your local dev environment by adding .user.xml file(s) to your implementation dataset (e.g. uportal-war/src/main/data/huskeynet) but BE CERTAIN NOT TO PUSH THEM TO GIT. Use a .gitignore file to prevent them from being committed accidentally.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 4,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Disable all default passwords",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": "database",
"content": "Edit the 'Portal_Administrators.group_membership.xml' file in your implementation dataset. Add <literal> elements containing the usernames of authorized portal administrators for your institution.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 5,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Add members of the portal dev team to Portal Administrators",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": null,
"content": "CAS, Shibboleth, and LDAP are common. Other SSO platforms are possible as well. Consider leaving local AuthN enabled for dev and occasional edge cases, but BE SURE TO DISABLE THE DEFAULT PASSWORDS. (See separate task.)",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 6,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Configure authentication sources",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": null,
"content": "LDAP is most common, but other sources are supported as well (e.g. RDBMS and SAML). LDAP connection info is configured in filters/*.propertiea and ldapContext.xml.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 7,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Configure user attributes in personDirectoryContext.xml",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": null,
"content": "Place users into groups like 'Students' 'Faculty' etc. based on their attributes. The groups defined here can be as fine- or course-grained as desired as as the available user attributes pertmit.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 8,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Configure groups in PagsGroupStoreConfig.xml",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": null,
"content": "Most portal content comes in the form of DLM fragments. Fragments are collections of content targetting a specific audience that may contain one or more _tabs_ as well as portlets in regions. Each fragment needs a fragment-definition.xml, a fragment-layout.xml, and a user.xml file in the implementation data set. Resolve this task once you have a first-pass collection of fragments; open new, specific tasks for updates to fragments beyond the initial setup.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 9,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Define DLM fragments for your portal",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": null,
"content": "Copy the uportal-war/src/main/webapp/media/skins/respondr/defaultSkin folder into a sibling folder with the same name as your branch (e.g. 'huskeynet'). Similarly copy the defaultSkinn.less file (e.g. 'huskeynet.less'). Edit the skinList.xml file to include your new custom skin.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 10,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Create a skin for your portal",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": null,
"content": "Ordinarly a good way to install your logo is to replace the portal-logo portlet (Simple CMS) with a new portlet (e.g. 'huskeynet-logo') based on Simple JSP.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 11,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Add your logo",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
},
{
"assignee": null,
"component": null,
"content": "uPortal comes with several 'bundled' portlet projects like Announcements and Calendar, but you may also want to use some of the other projects available in the Apereo comunity, or even custom portlet projects. In either case, additional portlet projects should be integrated into the aggregate uPortal build by either (1) _bundling_ them in uportal-portlets-overlay or (2) wrapping uPortal's build in a an aggregate ('puppet master') build script written in a tool like Groovy.",
"content_updated_on": "2014-07-01T00:00:00.000000+00:00",
"created_on": "2014-07-01T00:00:00.000000+00:00",
"edited_on": null,
"id": 12,
"kind": "task",
"milestone": null,
"priority": "major",
"reporter": null,
"status": "new",
"title": "Add additional portlet projects as necessary",
"updated_on": "2014-07-01T00:00:00.000000+00:00",
"version": null,
"watchers": null,
"voters": null
}
],
"comments": [],
"attachments": [],
"logs": [],
"meta": {
"default_assignee": null,
"default_component": null,
"default_kind": "bug",
"default_milestone": null,
"default_version": null
},
"components": [
{
"name": "database"
}
],
"milestones": [
{
"name": "M1"
}
],
"versions": []
}