Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
New feature for Sakai 10. Institutions may configure which question types they use in Samigo and which they do not.
10.0
OSP (Portfolios)
osp.freeform.disabled=true
OSP layouts are off by default. Do not turn OSP layouts on without consulting with the Sakai developer community (in other words it is strongly recommended you keep OSP layouts turned off by default.)
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.
To save system administrators' time, the copyright end date should automatically update to the current year, if the institution chooses.
10.0
Messages
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:
This can turn on/off the "CC" option when sending a message in the "Message" tool for all sites (institution level). If the property is true, then all sites will not have this option, otherwise, it defers to site level settings.
An institution can not disable the CC option, until now. They can set the default to false (mc.messages.ccEmailDefault=false) but an instructor could change it at the site level. This property completely removes this from the UI and force the value to false:
Required checkbox on the signup page which is only shown if account-validator.terms is set to a URL which contains the terms and conditions.
10.0
Password validation
Updating the default props
# Role that can use the password reset tool by default. # guest users are ones that are created by Site Info when adding external participants. # registered users are ones the are created by the New Account tool on the Gateway site. # Default: guest #resetRoles=guest,registered
# resetAllRoles allows this to work for any roles in the system (overrides resetRoles above) # Default: false #resetPass.resetAllRoles=true
# If you are running Sakai in a cluster behind a load balancer and the load balancer is changing the # scheme during forwarding, oauth validation will fail because the scheme is taken into account during the # signature comparison. Set this to the scheme that your load balancer is running under and the # launch request will be validated, or at least the scheme won't break it. # basiclti.provider.forcedurischeme=
 ## 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
In the default SectionFieldProviderImpl the sizes are limited to subject=8, course=3, section=3. This should be configurable, since most places use this default implementation.
# list of macros that will be expanded when used in a web link in resources. content.allowed.macros=${USER_ID},${USER_EID},${USER_FIRST_NAME},${USER_LAST_NAME}
Note that site related properties will not work because the resolver code is actually called from access which has no context. It may be possible to pass in the context since the original resource has context, then site properties would work, however this may have security implications where the link is embedded in another site and that aspect needs to be fully explored. As such it has not been included. It is a trivial exercise to add this though, see BaseContentService in the kernel.
The property site.title.maxlength allow long site titles fix the UI by cutting the end of the title in tabs.
We've got many long site titles and very similar, for example, "This is the subject part I", "This is the subject part II". In these cases both cutted titles appears to be the same "This is the subj...".
We want a more flexible way to do it. With 2 new properties:
The value has the format X:Y, wich means X percent of maxlength at the beginning and Y percent of maxlength at the end. Now if you choose 50:50 and [...], the above example, will get something like "This is[...]part I" and "This is[...]part II".
# Max length for site title display # Default 25 characters #site.title.maxlength=25
# Cut method for site title display # Default 100:0 display the first site.title.maxlength characters and the separator string at the end # Other values: # 0:100 display the last site.title.maxlength characters and the separator string at the beginning # 50:50 display first site.title.maxlength*50% characters the separator string and the last site.title.maxlength*50% #site.title.cut.method=100:0
# Separator string used to separate characters in cut method # Default ... #site.title.cut.separator= ...
Configuration will work like so: # SSP Early Alert integration # Allow Early Alerts integration? (default: false) ssp.allowed.alerts=true # URL to the SSP server ssp.server.url=http://ssp.unicon.net/ssp-platform/sso # the shared password between SSP and Sakai ssp.alerts.shared.password=********* # roles allowed to have SSP Early Alerts (default: access,Student) ssp.allowed.alert.roles=access,Student
# 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=
# Sites with non-editable title (by site type) # Example: course - course sites will have read only title. # Set as empty "site.type.titleNotEditable=", every site title would be modified. # Default: course #site.type.titleNotEditable=course,project
# 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