Sakai 10 new properties and permissions

Not recommended, but available for using the pre-Sakai 10 search tool. ElasticSearch is the default. These properties would revert to legacy search.

search.service.impl=org.sakaiproject.search.component.service.impl.ConcurrentSearchServiceImpl
search.indexbuilder.impl=org.sakaiproject.search.component.service.impl.SearchIndexBuilderImpl

All question types are enabled by default.

It is correct that multiplechoice has two properties to be set (historical reasons for this)

samigo.question.show.extendedmatchingitems 
samigo.question.show.fileupload 
samigo.question.show.essay 
samigo.question.show.audio 
samigo.question.show.matching 
samigo.question.show.truefalse 
samigo.question.show.multiplechoicesinglecorrect 
samigo.question.show.multiplechoicemultiplecorrect 
samigo.question.show.fillintheblank 
samigo.question.show.fillinnumeric 
samigo.question.show.survey 
samigo.question.show.matrixsurvey 
samigo.question.show.calculatedquestion

example properties

portal.google.analytics_id=UA-12345-5 
portal.google.analytics_domain=http://www.dr-chuck.com/ 
portal.google.analytics_detail=true 

When a analytics_id is specified, the GA (ga.js) code is include in the portal pages. If analytics_detail is true, the user's eid and siteId are sent as Custom Variables 1 and 2. 

https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingCustomVariables

Default is OOTB "postmaster@"+host.

This can be problematic for institutions that need to configure this value for dev/qat environments. 

smtp.postmaster.address.local-part 
smtp.postmaster.address.domain

The new feature to display profile images will be disabled by default.

msgcntr.pvtmsg.showProfileInfo = true 

Additionally, if profile images are enabled and you do not want to allow linking to the profile information, you can utilize the following profile2 property. If absent, this defaults to true: 

profile2.profile.link.enabled

example:

msgcntr.forums.defaultAvailabilityTime=8:00am

Default is false.

mc.messages.forwardEmailDisabled=true/false

 ## SAK-23737 - User types allowed to bypass password validation when editing account details
# An empty list (no property set) indicates that all types require password validation (default behavior)
# Which user types are provided and will therefore be allowed to bypass the password validation step
#user.type.provided=asdf,qwerty

default

portal.title.shortdescription.show=false

# Allow instructors to create and manage sections by themselves while also
# having some types of sections locked (read only). With this configuration
# (and MANUAL type set) an Instructor can create and manage sections except
# with the configured readonly categories.
# Defines the category codes of sections that are readonly (e.g. 01.lct,02.lab)
# Default: "" (empty) - all sections can be edited
#section.info.readonly.section.categories=

# Specifies the amount of time, in milliseconds, between latestData requests sent by the javascript client.
#portal.chat.pollInterval=5000

# Set this to true and video calling will be enabled on portal chat.
# DEFAULT: false
# portal.chat.video=true

# A list of nat traversal servers to try during portal chat video calling.
# DEFAULT: stun:stun.l.google.com:19302
# portal.chat.video.servers={list of ice servers}

# The timeout, in seconds, for operations like waiting for a call to be answered.
# DEFAULT: 25
# portal.chat.video.timeout=50

# Control the default hidden status of imported resources content
# when using Import from Site > Re-use Content feature in Site Info (SAK-23305)
# Default: false (visible)
# Since: 2.10
#content.import.hidden=true

# Set this to true and portal chat will be disabled for a user UNLESS portal.chat.permitted is set
# in their MyWorkspace site. Defaults to false.
#portal.chat.securedByUser=false

#### SAK-23257: Restrict site maintainer from adding or elevating users to certain roles.
#### For example, prevent the Instructor of a course site from adding new Instructor users
# DEFAULT: empty (no restricted roles)
# You can narrow the restriction to a specific type of site by appending .sitetype
# sitemanage.addParticipants.restrictedRoles=CustomRole
# sitemanage.addParticipants.restrictedRoles.course=Instructor
# sitemanage.addParticipants.restrictedRoles.project=maintain

# SAK-22537: How many sections can be added at one time?
# DEFAULT: 10
#sections.maxgroups.category=20

# Log failed login attempts? Defaults to true.
#login.log-failed=true

defaults to true

content.upload.dragndrop=(true|false)

HTML code for branding the Sakai online help

help.header 
help.footer

If you use container login and hit the gateway page, then you get the ability to login with either a CAS account or an internal account.

There should be an intermediate page where users can choose which auth to use.

default is true

wsetup.mailarchive.prepopulate.email=(true|false)

### 
 # Url to redirect the user to when they have been disabled. If you do not specify a disabledSiteUrl then the system will use /portal/disabled by default

 ### 
 disabledSiteUrl=https://this.user.is.disabled/disabled

It has been requested that a user account should be able to be locked to prevent login, rather than deleting the user. A flag could be added to the User object to track this. The login tools and UserDirectoryService methods could then read this and deny access if a user account is locked.

Currently a new column has been added to the sakai_user table for disabled. This is either 1 or 0, 1 = disabled.

If a user is disabled, then you can select where to have the user redirected to via this sakai.property

###
# Url to redirect the user to when they have been disabled
###
disabledSiteUrl=https://this.user.is.disabled/disabled

If you do not specify a disabledSiteUrl then the system will use /portal/disabled by default. You can go and create a public /portal/disabled site/page for this purpose.

Changing property flag, added property to enable/disable 

 Default is true
portal.show.time=false 

Messaging enabled is the default.

profile2.messaging.enabled=(true|false) 

Now supports ONE_DEEP which is of the form BASEDIR/s/steve.jpg, which is additive to previous property (from PRFL-682)

# If you are using filesystem as your photo source you need to set this to the base directory where you store 
# them. Profile looks them up by appending the first letter of a user's eid then a slash, then the second 
# letter of the eid followed by a slash and finally the eid suffixed by '.jpg'. 
# Like this: 
# /official-photos/a/d/adrian.jpg 
#profile2.official.image.directory=/official-photos

PRFL-834 - Getting issue details... STATUS

(see PRFL-831)

#default is profile.official.image.enabled=false . See completed documentation in Sakai default properties.

profile2.official.image.enabled=true 
profile2.picture.type=official 
profile2.official.image.source=filesystem 
profile2.official.image.directory=/Users/steve/dev/sakai/official-images 
profile2.official.image.directory.pattern = ALL_IN_ONE

################################
## Available as of version 1.6:
################################
 
# Enable/disable the staff profile feature? (true/false, default true)
profile2.profile.staff.enabled=true

# Enable/disable the student profile feature? (true/false, default true)
profile2.profile.student.enabled=true

# Enable/disable the social profile feature? (true/false, default true)
profile2.profile.social.enabled=true

# Enable/disable the interests profile feature? (true/false, default true)
profile2.profile.interests.enabled=true

# Convert images from URL to local storage (added in PRFL-740)
profile2.import.images=true

# Default: false 
#lrs.enabled=true 

# Default: No filters (all statements processed) 
#lrs.origins.filter=tool1,tool2,tool3

# Example: tool.categories.append.sakai.announcements=course 
# Default: use the categories defined in the tool xml file 
# tool.categories.append.{toolid}=category1,category2,category3 

## (2) Override the current tool categories with a new set of categories (removes all categories if it is blank) 
# Example: tool.categories.sakai.announcements=course,project 
# Default: use the categories defined in the tool xml file 
# tool.categories.{toolid}=category1,category2,category3

# Otherwise, the URLs will reflect the attributes of the request URL. (443 | 8443 | or any other port)
# Default: no secure port or protocol (https) will be used, setting this to 0 will have the same effect as not setting it
#force.url.secure=443

# Turn on mime type detection
# DEFAULT: true (on)
# content.useMimeMagic=false

Permission in the synoptic calendar tool in order to configure if a user has/ has not the rights to edit the options.