[Building Sakai] sakai-dev Digest, Vol 65, Issue 10
Steve Swinsburg
steve.swinsburg at gmail.com
Wed Jul 16 05:05:53 PDT 2014
Hi,
Not sure what you mean here, do you want a listing of the tools in a site?
Or the data for the tools in the site in the context of a user?
cheers,
Steve
On Fri, Jul 11, 2014 at 4:03 PM, Srinivas Puramshetty <
puramshetty.srinu at gmail.com> wrote:
> Hi Team,
>
> Is there any way to build sakai10 json object of each tool in mobile app?
>
>
>
>
> On Fri, Jul 11, 2014 at 12:30 AM, <
> sakai-dev-request at collab.sakaiproject.org> wrote:
>
>> Send sakai-dev mailing list submissions to
>> sakai-dev at collab.sakaiproject.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> or, via email, send a message with subject or body 'help' to
>> sakai-dev-request at collab.sakaiproject.org
>>
>> You can reach the person managing the list at
>> sakai-dev-owner at collab.sakaiproject.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of sakai-dev digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Jira maintenance, Friday, July 11, 9 pm Eastern (Neal Caidin)
>> 2. Re: Help on how to query Sakai database (Steve Swinsburg)
>> 3. Re: Default an External Tool as on or checked (Steve Swinsburg)
>> 4. enabling portal video chat on Sakai 10.x (Mustansar Mehmood)
>> 5. Re: SAKAI LDAP configuration (Ismail Naik)
>> 6. Re: Editing roles and permission (Ismail Naik)
>> 7. Site participants (Ismail Naik)
>> 8. Re: Site participants (Gao Jun)
>> 9. SCORM with Sakai 2.8 or later (Jean-Francois Leveque)
>> 10. Re: Editing roles and permission (Kurosch Petzold)
>> 11. Metaobj Permissions (Kurosch Petzold)
>> 12. Contrib tools and TOChelp.xml (Roger Brown)
>> 13. Re: enabling portal video chat on Sakai 10.x (Alex Ballest?)
>> 14. Re: Metaobj Permissions (Noah Botimer)
>> 15. Re: [Contrib: Evaluation System] QA server for evaluation
>> trunk? (Matthew Jones)
>> 16. Re: [Contrib: Evaluation System] QA server for evaluation
>> trunk? (Neal Caidin)
>> 17. Re: SAKAI LDAP configuration (Rashid, Amir)
>> 18. Save the Date! Sakai Virtual Conference 2014 "Bridging
>> Education with Technology" - Nov. 7th (Neal Caidin)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 09 Jul 2014 15:50:46 -0400
>> From: Neal Caidin <neal.caidin at apereo.org>
>> Subject: [Building Sakai] Jira maintenance, Friday, July 11, 9 pm
>> Eastern
>> To: sakai-dev <sakai-dev at collab.sakaiproject.org>, Sakai QA
>> <sakai-qa at collab.sakaiproject.org>,
>> "production at collab.sakaiproject.org"
>> <production at collab.sakaiproject.org>,
>> "portfolio at collab.sakaiproject.org"
>> <portfolio at collab.sakaiproject.org>,
>> "sakai-user at collab.sakaiproject.org"
>> <sakai-user at collab.sakaiproject.org>, "
>> i18n at collab.sakaiproject.org"
>> <i18n at collab.sakaiproject.org>,
>> "accessibility at collab.sakaiproject.org"
>> <accessibility at collab.sakaiproject.org>,
>> "pedagogy at collab.sakaiproject.org" <
>> pedagogy at collab.sakaiproject.org>
>> Message-ID: <53BD9D16.8060808 at apereo.org>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> Jira will be unavailable due to maintenance on Friday, July 11, 9 pm
>> Eastern / 6 pm Pacific / 1 pm GMT .
>>
>> Expected to be available within 2 hours or less after maintenance
>> commences.
>>
>> Thanks for your attention.
>>
>> Cheers,
>> Neal
>>
>> --
>> Neal Caidin
>> Sakai Community Coordinator
>> Apereo Foundation
>> neal.caidin at apereo.org
>> Skype me! (but let me know in advance for the first interaction) -
>> nealkdin
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 10 Jul 2014 07:26:01 +1000
>> From: Steve Swinsburg <steve.swinsburg at gmail.com>
>> Subject: Re: [Building Sakai] Help on how to query Sakai database
>> To: "Mark J. Norton" <markjnorton at earthlink.net>
>> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
>> Message-ID:
>> <CAPyxfbG9UK012PGYWbPrEMsD4V9-39R5SSkbe=
>> x9XVn_GrHv8w at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Reiterating what Mark said, you should not manipulate the db directly.
>> Reads are more acceptable though.
>>
>> SELECT site_id
>> FROM sakai_site_tool
>> WHERE registration = 'sakai.dropbox'
>>
>> Will give you the site_ids for all sites that have the dropbox tool.
>>
>> cheers,
>> Steve
>>
>>
>> On Thu, Jul 10, 2014 at 3:01 AM, <markjnorton at earthlink.net> wrote:
>>
>> > Generally, it is not recommended to make direct queries against a Sakai
>> > database. The data contained in these records are maintained and
>> managed
>> > by the Site Service. A Java API allows you to access Site information,
>> > including some rather powerful search capabilities. While the database
>> > schema has been stable for quite some time, there is no guarantee that
>> it
>> > won't change in a future release. The API protects you against those
>> sorts
>> > of changes, even updating table definitions as needed. I strongly
>> suggest
>> > you have a look at the Site Service in the Sakai kernel and see if the
>> > objects/methods meet your needs.
>> >
>> > - Mark Norton
>> >
>> >
>> > -----Original Message-----
>> > >From: Virg?lio Santos <virgilio.santos at gmail.com>
>> > >Sent: Jul 9, 2014 11:04 AM
>> > >To: sakai-dev at collab.sakaiproject.org
>> > >Subject: [Building Sakai] Help on how to query Sakai database
>> > >
>> > >Hello,
>> > >
>> > >I have a query do execute on Sakai database that I could not figured
>> > >out how to do with the available services. Basically, I want to query
>> > >all Sites that have some specific tool in at least one of its pages.
>> > >
>> > >For know, I'm trying something like this (It's not the query I will
>> > >really use, just an example):
>> > >
>> > >String sql = "SELECT * from SAKAI_SITE";
>> > >List<Site> siteList = null;
>> > >
>> > >SQLQuery query = this.getSession().createSQLQuery(sql);
>> > >query.addEntity(Site.class);
>> > >query.setResultTransformer(Criteria.ALIAS_TO_ENTITY_MAP);
>> > >List results = query.list();
>> > >
>> > >for(Object object : results) {
>> > > Site s = (Site) object;
>> > > // do stuff
>> > >}
>> > >
>> > >And getting this error:
>> > >org.sakaiproject.portal.api.PortalHandlerException:
>> > >org.sakaiproject.tool.api.ToolException:
>> > >org.springframework.web.util.NestedServletException: Request
>> > >processing failed; nested exception is org.hibernate.MappingException:
>> > >Unknown entity: org.sakaiproject.site.api.Site
>> > >
>> > >Any tips on making complex data queries on Sakai database will be very
>> > >useful as well
>> > >
>> > >Thanks in advance.
>> > >
>> > >--
>> > >Deserve's Got Nothing To Do With It
>> > >_______________________________________________
>> > >sakai-dev mailing list
>> > >sakai-dev at collab.sakaiproject.org
>> > >http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> > >
>> > >TO UNSUBSCRIBE: send email to
>> > sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> > "unsubscribe"
>> >
>> > _______________________________________________
>> > sakai-dev mailing list
>> > sakai-dev at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >
>> > TO UNSUBSCRIBE: send email to
>> > sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> > "unsubscribe"
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/c250e6b9/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Thu, 10 Jul 2014 07:31:58 +1000
>> From: Steve Swinsburg <steve.swinsburg at gmail.com>
>> Subject: Re: [Building Sakai] Default an External Tool as on or
>> checked
>> To: Brett Parker <brparke1 at wsc.edu>
>> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
>> Message-ID:
>> <
>> CAPyxfbEY9M8gQ_KU25Gz9hWL1nZFKZ7Sf199z5ixpxra_RPKSg at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi,
>>
>> You can create a toolOrder.xml file that defines the tools and their
>> defaults, and drop it into Tomcat/sakai/toolOrder.xml (or wherever your
>> sakai.properties file lives).
>>
>> For example:
>>
>> <?xml version="1.0"?>
>> <toolOrder>
>> <category name="course">
>> <tool id="sakai.iframe.site" selected="true"/>
>> <tool id="sakai.synoptic.chat" selected="true"/>
>> <tool id="sakai.synoptic.discussion" selected="true"/>
>> <tool id="sakai.synoptic.announcement" selected="true"/>
>> <tool id="home" selected="true"/>
>> <tool id="sakai.syllabus" selected="true"/>
>> <tool id="sakai.schedule" selected="true"/>
>> <tool id="sakai.announcements" selected="true"/>
>> <tool id="sakai.resources" selected="true"/>
>> <tool id="sakai.discussion" selected="true"/>
>> <tool id="sakai.assignment" selected="true"/>
>> <tool id="sakai.assignment.grades" selected="true"/>
>> <tool id="sakai.samigo" selected="true"/>
>> <tool id="sakai.gradebook.tool" selected="true"/>
>> <tool id="sakai.dropbox"/>
>> <tool id="sakai.rwiki" selected="true" />
>> <tool id="sakai.chat" selected="true"/>
>> <tool id="sakai.mailbox" selected="true"/>
>> <tool id="sakai.news" selected="true"/>
>> <tool id="sakai.iframe" selected="true"/>
>> <tool id="sakai.presentation"/>
>> <tool id="sakai.sections" selected="true"/>
>> <tool id="sakai.site.roster" selected="true"/>
>> <tool id="sakai.siteinfo" required="true"/>
>> </category>
>> <category name="project">
>> <tool id="sakai.iframe.site"/>
>> <tool id="sakai.synoptic.chat"/>
>> <tool id="sakai.synoptic.discussion"/>
>> <tool id="sakai.synoptic.announcement"/>
>> <tool id="home" selected="true"/>
>> <tool id="sakai.syllabus"/>
>> <tool id="sakai.schedule"/>
>> <tool id="sakai.announcements"/>
>> <tool id="sakai.resources"/>
>> <tool id="sakai.discussion"/>
>> <tool id="sakai.assignment"/>
>> <tool id="sakai.assignment.grades"/>
>> <tool id="sakai.samigo"/>
>> <tool id="sakai.gradebook.tool"/>
>> <tool id="sakai.dropbox"/>
>> <tool id="sakai.chat"/>
>> <tool id="sakai.rwiki"/>
>> <tool id="sakai.mailbox"/>
>> <tool id="sakai.news"/>
>> <tool id="sakai.iframe"/>
>> <tool id="sakai.presentation"/>
>> <tool id="sakai.sections"/>
>> <tool id="sakai.site.roster"/>
>> <tool id="sakai.siteinfo" required="true"/>
>> </category>
>> <category name="collaboration">
>> <tool id="sakai.iframe.site"/>
>> <tool id="sakai.synoptic.chat"/>
>> <tool id="sakai.synoptic.discussion"/>
>> <tool id="sakai.synoptic.announcement"/>
>> <tool id="home" selected="true"/>
>> <tool id="sakai.syllabus"/>
>> <tool id="sakai.schedule"/>
>> <tool id="sakai.announcements"/>
>> <tool id="sakai.resources"/>
>> <tool id="sakai.discussion"/>
>> <tool id="sakai.chat"/>
>> <tool id="sakai.rwiki"/>
>> <tool id="sakai.mailbox"/>
>> <tool id="sakai.news"/>
>> <tool id="sakai.iframe"/>
>> <tool id="sakai.presentation"/>
>> <tool id="sakai.sections"/>
>> <tool id="sakai.site.roster"/>
>> <tool id="sakai.siteinfo" required="true"/>
>> </category>
>> </toolOrder>
>>
>>
>>
>>
>> On Thu, Jul 10, 2014 at 3:47 AM, Brett Parker <brparke1 at wsc.edu> wrote:
>>
>> > Greetings,
>> >
>> > Hoping someone out there has done something like this before. We have
>> an
>> > external tool that we want all our sakai classes to have by default. I
>> > have created the tool on the sakai server so it is available for
>> everyone
>> > but I would like it to be automatically checked, and if possible
>> greyed-out
>> > (like Site Info) in the Edit Tools window of Site Info. This way it is
>> > included into every class that is created be automatically.
>> >
>> > Thanks.
>> >
>> > -Brett-
>> >
>> > _______________________________________________
>> > sakai-dev mailing list
>> > sakai-dev at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >
>> > TO UNSUBSCRIBE: send email to
>> > sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> > "unsubscribe"
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/52cea769/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Wed, 09 Jul 2014 17:44:48 -0500
>> From: Mustansar Mehmood <mustansar at rice.edu>
>> Subject: [Building Sakai] enabling portal video chat on Sakai 10.x
>> To: "sakai-dev at collab.sakaiproject.org Dev"
>> <sakai-dev at collab.sakaiproject.org>
>> Message-ID: <53BDC5E0.1080700 at rice.edu>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi,
>> I am not seeing portal chat(new video chat) on Sakai 10.x. Chances(a
>> mere guess) are my sakai.properties needs adjustment. I am hoping somone
>> can point me to the documentation on configuring that video chat feature
>> or share working settings that I can throw into my properties file.
>> Thanks,
>> Mustansar
>>
>> --
>> Mustansar Mehmood
>> Educational System Developer& Integrator
>>
>> Information Technology
>> 6100 Main St. MS 119
>> Houston Texas 77005
>>
>> Phone:(713)348-2523
>> Fax :(713)348 6099
>> email:mustansar at rice.edu
>>
>>
>>
>>
>>
>> I have yet to see any problem, however complicated, which, when,you
>> looked at it in the right way, did not become still more complicated.
>> -- Poul Anderson
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140709/7d8042fe/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Thu, 10 Jul 2014 10:12:56 +0530
>> From: "Ismail Naik" <ismail.n at in.uaeexchange.com>
>> Subject: Re: [Building Sakai] SAKAI LDAP configuration
>> To: "'Rashid, Amir'" <arashid at bu.edu>, "'Steve Swinsburg'"
>> <steve.swinsburg at gmail.com>
>> Cc: sakai-dev at collab.sakaiproject.org
>> Message-ID: <01fc01cf9bf9$6beb52e0$43c1f8a0$@in.uaeexchange.com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi Team,
>>
>>
>>
>> We faced same issue, just do the below changes and try the luck.
>>
>>
>>
>> . Comment out the eidValidator
>>
>>
>>
>> <!--
>>
>> <!-- Optional. If you don't provide an eidValidator the system
>>
>> defaults to allowing searches on any EID, including empty
>>
>> and null Strings. -->
>>
>> <property name="eidValidator">
>>
>> <bean
>> class="edu.amc.sakai.user.RegexpBlacklistEidValidator">
>>
>> <property name="regexpFlags">
>>
>> <bean
>> id="java.util.regex.Pattern.CASE_INSENSITIVE"
>>
>>
>>
>> class="org.springframework.beans.factory.config.FieldRetrievingFactoryBean"
>> />
>>
>> </property>
>>
>> <property name="eidBlacklist">
>>
>> <list>
>>
>> <value>null</value>
>>
>> <!--value>nobody</value-->
>>
>>
>> <!--value>adversary</value-->
>>
>> </list>
>>
>> </property>
>>
>> </bean>
>>
>> </property>
>>
>> <property
>> name="searchAliases"><value>false</value></property>
>>
>> -->
>>
>>
>>
>> . Make followReferrals as true
>>
>>
>>
>> <property name="followReferrals">
>>
>> <value>true</value>
>>
>> </property>
>>
>>
>>
>>
>>
>> . Use the folloing keys for attributeMappings and use your values
>>
>>
>>
>> <property name="attributeMappings">
>>
>> <map>
>>
>> <entry
>> key="login"><value>sAMAccountName</value></entry>
>>
>> <entry
>> key="firstName"><value></value></entry>
>>
>> <entry key="preferredFirstName">user
>> ur prefereedFirstName<value> </value></entry>
>>
>> <entry key="lastName"><value> this
>> is
>> okay</value></entry>
>>
>> <entry
>> key="email"><value>mail</value></entry>
>>
>> </map>
>>
>> </property>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>> Ismail N. - IT Department
>>
>> Xm Software Solutions Pvt Ltd | SKCL | CENTRAL SQUARE- 1
>>
>> CIPET Road | Thiru-Vi-Ka Industrial Estate| Guindy | Chennai- 600032.
>>
>> TEL: 044-30464899 | FAX: 044-30464861|
>>
>> Ext:613
>>
>> <mailto:ismail.n at in.uaeexchange.com> ismail.n at in.uaeexchange.com
>>
>>
>>
>> From: sakai-dev-bounces at collab.sakaiproject.org
>> [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Rashid,
>> Amir
>> Sent: 09 July 2014 18:44
>> To: Steve Swinsburg
>> Cc: sakai-dev at collab.sakaiproject.org
>> Subject: Re: [Building Sakai] SAKAI LDAP configuration
>>
>>
>>
>> Yes. Infact I have a 2.8.1 instance on the same machine with the same
>> LDAP
>> setting that will boot up without any issues.
>>
>>
>>
>> --Amir
>>
>>
>>
>>
>>
>> Amir Rashid - 617.358.2782
>>
>> Boston University - SMG ITS
>>
>>
>>
>>
>>
>> From: Steve Swinsburg <steve.swinsburg at gmail.com>
>> Date: Wednesday, July 9, 2014 at 9:05 AM
>> To: "Rashid, Amir" <arashid at bu.edu>
>> Cc: "sakai-dev at collab.sakaiproject.org" <
>> sakai-dev at collab.sakaiproject.org>
>> Subject: Re: [Building Sakai] SAKAI LDAP configuration
>>
>>
>>
>> Ok so using those same parameters are you able to perform an ldapsearch on
>> the commandline of your Sakai server for a given user?
>>
>>
>>
>> On Wed, Jul 9, 2014 at 10:58 PM, Rashid, Amir <arashid at bu.edu> wrote:
>>
>> Hi
>>
>> Following properties are being used in the jldap-beans.xml file.
>>
>> Thanks,
>>
>> --Amir
>>
>>
>>
>>
>>
>> Amir Rashid - 617.358.2782
>>
>> Boston University - SMG ITS
>>
>>
>>
>> <property name="memoryService">
>>
>> <ref
>> bean="org.sakaiproject.memory.api.MemoryService"/>
>>
>> </property>
>>
>>
>>
>> <!-- Required. Host name or address of your LDAP server
>> -->
>>
>> <property name="ldapHost">
>>
>> <value>XX.XX.XXX</value>
>>
>> </property>
>>
>>
>>
>> <!-- Optional. LDAP connection port. Typically defaults to
>>
>> JLDAPDirectoryProvider.DEFAULT_LDAP_PORT (389).
>> Secured
>>
>> connections are usually on 636 -->
>>
>> <property name="ldapPort">
>>
>> <value>389</value>
>>
>> </property>
>>
>>
>>
>> <!-- If secureConnection is true, a keystore location
>> must
>> be provided
>>
>> unless javax.net.ssl.trustStore system property
>> has
>> already been
>>
>> set -->
>>
>> <!--property name="keystoreLocation">
>>
>> <value>/usually/set/at/startup</value>
>>
>> </property-->
>>
>>
>>
>> <!-- If secureConnection is true, a keystore password
>> must
>> be provided
>>
>> unless javax.net.ssl.trustStorePassword system
>> property has already
>>
>> been set -->
>>
>> <!--property name="keystorePassword">
>>
>> <value>usually-set-at-startup</value>
>>
>> </property-->
>>
>>
>>
>> <!-- Optional. DN to which to bind for directory searches.
>>
>> Typically only necessary if autoBind is true -->
>>
>> <property name="ldapUser">
>>
>>
>> <value>cn=XXXXXXX,OU=people,dc=XX,dc=XX,dc=XXX</value>
>>
>> </property>
>>
>>
>>
>> <!-- Optional. Password for ldapUser defined above -->
>>
>> <property name="ldapPassword">
>>
>> <value>XXXXXXXXXX</value>
>>
>> </property>
>>
>>
>>
>> <!-- Optional. Enables/disables secure LDAP connections.
>>
>> defaults to
>> JLDAPDirectoryProvider.DEFAULT_IS_SECURE_CONNECTION (false) -->
>>
>> <property name="secureConnection">
>>
>> <value>false</value>
>>
>> </property>
>>
>> <!-- Optional. Indicate if connection allocation should
>>
>> implicitly bind as ${ldapUser}. Defaults to false
>> -->
>>
>> <property name="autoBind">
>>
>> <value>true</value>
>>
>> </property>
>>
>> <!-- Optional, but usually specified. Base DN for directory searches. -->
>>
>> <property name="basePath">
>>
>> <value>dc=XX,dc=XX,dc=XXX</value>
>>
>> </property>
>>
>>
>>
>> <!-- Optional. Indicate if connections should follow
>>
>> referrals. Defaults to
>>
>> JLDAPDirectoryProvider.DEFAULT_IS_FOLLOW_REFERRALS
>> (false)-->
>>
>> <property name="followReferrals">
>>
>> <value>false</value>
>>
>> </property>
>>
>> <property name="caseSensitiveCacheKeys">
>>
>> <value>false</value>
>>
>> </property>
>>
>> <property name="ldapAttributeMapper">
>>
>> <ref bean="edu.amc.sakai.user.LdapAttributeMapper"
>> />
>>
>> </property>
>>
>> <!-- Optional. If you don't provide an eidValidator the system
>>
>> defaults to allowing searches on any EID, including empty
>>
>> and null Strings. -->
>>
>> <property name="eidValidator">
>>
>> <bean
>> class="edu.amc.sakai.user.RegexpBlacklistEidValidator">
>>
>> <property name="regexpFlags">
>>
>> <bean
>> id="java.util.regex.Pattern.CASE_INSENSITIVE"
>>
>>
>>
>> class="org.springframework.beans.factory.config.FieldRetrievingFactoryBean"
>> />
>>
>> </property>
>>
>> <property name="eidBlacklist">
>>
>> <list>
>>
>> <value>null</value>
>>
>> <!--value>nobody</value-->
>>
>>
>> <!--value>adversary</value-->
>>
>> </list>
>>
>> </property>
>>
>> </bean>
>>
>> </property>
>>
>> <property
>> name="searchAliases"><value>false</value></property>
>>
>>
>>
>> </bean>
>>
>>
>>
>> <!-- An optional bean definition which can be used to customize LDAP
>>
>> attribute to Sakai User instance member mapping behaviors. This
>>
>> example describes availabel configuration options for
>> SimpleLdapAttributeMapper
>>
>> (the default LdapAttributeMapper implementation). -->
>>
>> <bean id="edu.amc.sakai.user.LdapAttributeMapper"
>>
>>
>> class="edu.amc.sakai.user.SimpleLdapAttributeMapper"
>>
>> init-method="init"
>>
>> singleton="true">
>>
>>
>>
>> <!-- A typical set of attribute mappings. Keys are logical
>>
>> names expected by the application. Values are physical
>> LDAP
>>
>> attribute names. If not specified or empty, defaults to
>>
>> AttributeMappingConstants.DEFAULT_ATTR_MAPPINGS. -->
>>
>> <property name="attributeMappings">
>>
>> <map>
>>
>> <entry
>> key="login"><value>sAMAccountName</value></entry>
>>
>> <entry
>> key="firstName"><value>givenName</value></entry>
>>
>> <!--entry
>> key="preferredFirstName"><value>preferredName</value></entry-->
>>
>> <entry
>> key="lastName"><value>sn</value></entry>
>>
>> <entry
>> key="email"><value>mail</value></entry>
>>
>> <entry
>> key="groupMembership"><value>groupMembership</value></entry>
>>
>> <!--entry
>> key="jpegPhoto"><value>jpegPhoto</value></entry -->
>>
>> </map>
>>
>> </property>
>>
>>
>>
>> <!-- Several options for calculating Sakai user types
>> based
>>
>> on LDAP attributes. Defaults to an instance of
>> EmptyStringUserTypeMapper -->
>>
>> <property name="userTypeMapper">
>>
>> <!-- Select one of the following beans -->
>>
>> <!--ref
>> bean="edu.amc.sakai.user.EmptyStringUserTypeMapper" /-->
>>
>> <!-- ref
>> bean="edu.amc.sakai.user.EntryAttributeToUserTypeMapper" /-->
>>
>> <!-- ref
>> bean="edu.amc.sakai.user.EntryContainerRdnToUserTypeMapper" /-->
>>
>> <ref
>> bean="edu.amc.sakai.user.StringUserTypeMapper"
>> />
>>
>> </property>
>>
>>
>>
>> </bean>
>>
>>
>>
>>
>>
>>
>>
>> From: Steve Swinsburg <steve.swinsburg at gmail.com>
>> Date: Tuesday, July 8, 2014 at 11:56 PM
>> To: "Rashid, Amir" <arashid at bu.edu>
>> Cc: "sakai-dev at collab.sakaiproject.org" <
>> sakai-dev at collab.sakaiproject.org>
>> Subject: Re: [Building Sakai] SAKAI LDAP configuration
>>
>>
>>
>> Looks like you need to provide a username and password in the LDAP config
>> to
>> get a bind. What are your LDAP settings from jldap-beans.xml ?
>>
>>
>>
>> On Wed, Jul 9, 2014 at 5:36 AM, Rashid, Amir <arashid at bu.edu> wrote:
>>
>>
>>
>> Hi Folks,
>>
>>
>>
>> I have 2.81 in production right now. I am using one of the test machine to
>> install SAKAI 10. I am trying to configure it to use LDAP the same as 2.8.
>> Included is the trace from the log file. I can intermittently log in if I
>> try it a few times. Please let me know if there are any undocumented
>> configuration changes to the LDAP configuration settings .
>>
>>
>>
>> I will appreciate your help in this matter.
>>
>>
>>
>> --Amir
>>
>>
>>
>>
>>
>> Amir Rashid - 617.358.2782
>>
>> Boston University - SMG ITS
>>
>>
>>
>>
>>
>> 2014-07-08 13:26:36,428 WARN ajp-bio-8009-exec-14
>> org.sakaiproject.portal.util.ErrorReporter - Bug Report bug-id:
>> 573880ae-c5b0-42f5-8b47-534991e591a0 user: null usage-session: null time:
>> Jul 8, 2014 13:26:36 user comment: null stack trace
>>
>> org.sakaiproject.portal.api.PortalHandlerException:
>> java.lang.RuntimeException: authenticateUser(): LDAPException during
>> authentication attempt [userLogin = arashid][result code = Operations
>> Error][error message = 00000000: LdapErr: DSID-0C090627, comment: In order
>> to perform this operation a successful bind must be completed on the
>> connection., data 0, vece]
>>
>> at
>>
>> org.sakaiproject.portal.charon.handlers.ReLoginHandler.doPost(ReLoginHandler
>> .java:50)
>>
>> caused by: java.lang.RuntimeException: authenticateUser(): LDAPException
>> during authentication attempt [userLogin = arashid][result code =
>> Operations
>> Error][error message = 00000000: LdapErr: DSID-0C090627, comment: In order
>> to perform this operation a successful bind must be completed on the
>> connection., data 0, vece]
>>
>> at
>>
>> org.sakaiproject.user.impl.BaseUserDirectoryService.getProviderAuthenticated
>> User(BaseUserDirectoryService.java:1668)
>>
>> caused by: LDAPException: Operations Error (1) Operations Error
>>
>> LDAPException: Server Message: 00000000: LdapErr: DSID-0C090627, comment:
>> In
>> order to perform this operation a successful bind must be completed on the
>> connection., data 0, vece
>>
>> LDAPException: Matched DN:
>>
>> at com.novell.ldap.LDAPResponse.getResultException(null:-1)
>>
>> at com.novell.ldap.LDAPResponse.chkResultCode(null:-1)
>>
>> at com.novell.ldap.LDAPSearchResults.next(null:-1)
>>
>> at
>>
>> edu.amc.sakai.user.JLDAPDirectoryProvider.searchDirectory(JLDAPDirectoryProv
>> ider.java:959)
>>
>> at
>>
>> edu.amc.sakai.user.JLDAPDirectoryProvider.searchDirectoryForSingleEntry(JLDA
>> PDirectoryProvider.java:856)
>>
>> at
>>
>> edu.amc.sakai.user.JLDAPDirectoryProvider.getUserByEid(JLDAPDirectoryProvide
>> r.java:778)
>>
>> at
>>
>> edu.amc.sakai.user.JLDAPDirectoryProvider.lookupUserBindDn(JLDAPDirectoryPro
>> vider.java:820)
>>
>> at
>>
>> edu.amc.sakai.user.JLDAPDirectoryProvider.authenticateUser(JLDAPDirectoryPro
>> vider.java:397)
>>
>> at
>>
>> org.sakaiproject.user.impl.BaseUserDirectoryService.getProviderAuthenticated
>> User(BaseUserDirectoryService.java:1668)
>>
>> at
>>
>> org.sakaiproject.user.impl.BaseUserDirectoryService.authenticate(BaseUserDir
>> ectoryService.java:1611)
>>
>> at
>>
>> org.sakaiproject.user.impl.UserAuthnComponent.authenticate(UserAuthnComponen
>> t.java:108)
>>
>> at
>>
>> org.sakaiproject.login.impl.LoginServiceComponent.authenticate(LoginServiceC
>> omponent.java:90)
>>
>> at
>> org.sakaiproject.login.tool.SkinnableLogin.doPost(SkinnableLogin.java:302)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
>> FilterChain.java:303)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
>> ain.java:208)
>>
>> at
>> org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:394)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
>> FilterChain.java:241)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
>> ain.java:208)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.
>> java:748)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDis
>> patcher.java:486)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch
>> er.java:378)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher
>> .java:338)
>>
>> at
>>
>> org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.help(ActiveToolC
>> omponent.java:583)
>>
>> at
>>
>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doLogin(SkinnableCharon
>> Portal.java:997)
>>
>> at
>>
>> org.sakaiproject.portal.charon.handlers.ReLoginHandler.doGet(ReLoginHandler.
>> java:65)
>>
>> at
>>
>> org.sakaiproject.portal.charon.handlers.ReLoginHandler.doPost(ReLoginHandler
>> .java:50)
>>
>> at
>>
>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doPost(SkinnableCharonP
>> ortal.java:1296)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
>> FilterChain.java:303)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
>> ain.java:208)
>>
>> at
>> org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:455)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
>> FilterChain.java:241)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
>> ain.java:208)
>>
>> at
>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
>> FilterChain.java:241)
>>
>> at
>>
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
>> ain.java:208)
>>
>> at
>>
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
>> va:220)
>>
>> at
>>
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
>> va:122)
>>
>> at
>>
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
>> .java:501)
>>
>> at
>>
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171
>> )
>>
>> at
>>
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102
>> )
>>
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
>>
>> at
>>
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
>> :116)
>>
>> at
>>
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
>>
>> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:193)
>>
>> at
>>
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(Abstrac
>> tProtocol.java:607)
>>
>> at
>>
>> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:
>> 314)
>>
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
>> 45)
>>
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
>> 15)
>>
>> at
>>
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.ja
>> va:61)
>>
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>>
>> Tool Placement:
>>
>> No Placement
>>
>>
>>
>> Request:
>>
>> : AuthType:null
>>
>> : CharEncoding:UTF-8
>>
>> : ContentLength:38
>>
>> : ContentType:application/x-www-form-urlencoded
>>
>> : ContextPath:/portal
>>
>> : LocalAddress:smgcms1.bu.edu <http://bu.edu/>
>>
>> : LocalName:smgcms1.bu.edu <http://smgcms1.bu.edu/>
>>
>> : LocalPort:443
>>
>> : Method:POST
>>
>> : PathInfo:/relogin
>>
>> : Protocol:HTTP/1.1
>>
>> : QueryString:null
>>
>> : RemoteAddress:168.122.33.194
>>
>> : RemoteHost:168.122.33.194
>>
>> : RemotePort:-1
>>
>> : Requested URL:https://smgcms1.bu.edu/portal/relogin
>>
>> : Scheme:https
>>
>> : ServerName:smgcms1.bu.edu <http://smgcms1.bu.edu/>
>>
>> : Headers:
>>
>> : Header:host:smgcms1.bu.edu <http://bu.edu/>
>>
>> : Header:connection:keep-alive
>>
>> : Header:content-length:38
>>
>> : Header:Cache-Control:max-age=0
>>
>> :
>>
>> Header:accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/we
>> bp,*/*;q=0.8
>>
>> : Header:Origin:https://smgcms1.bu.edu <http://smgcms1.bu.edu/>
>>
>> : Header:user-agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4)
>> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36
>>
>> : Header:content-type:application/x-www-form-urlencoded
>>
>> : Header:DNT:1
>>
>> : Header:referer:https://smgcms1.bu.edu/portal/login
>>
>> : Header:accept-encoding:gzip,deflate,sdch
>>
>> : Header:accept-language:en-US,en;q=0.8
>>
>> : Header:cookie:---censored---
>>
>> : Parameters:
>>
>> : Parameter:eid:0:----censored----
>>
>> : Parameter:pw:0:----censored----
>>
>> : Parameter:submit:0:Login
>>
>> : Attributes:
>>
>> :
>>
>> Attribute:javax.servlet.request.ssl_session:1C4C47A3FFAEEA4FAF017B65F33A9162
>> 71C8B1293EB3487C9F7EEC25B8206C46
>>
>> :
>>
>> Attribute:javax.servlet.request.ssl_session_id:1C4C47A3FFAEEA4FAF017B65F33A9
>> 16271C8B1293EB3487C9F7EEC25B8206C46
>>
>> :
>> Attribute:sakai.character.encoding.done:sakai.character.encoding.done
>>
>> : Attribute:javax.servlet.request.key_size:128
>>
>> : Attribute:sakai.filtered:sakai.filtered
>>
>> : Attribute:javax.servlet.request.cipher_suite:DHE-RSA-AES128-SHA
>>
>> :
>> Attribute:sakai.session:MyS_null{60cc469c-90b1-4a78-9bce-f06c3cc1c81a,
>> userId='null', at=8, ts=2, cs=2, Tue Jul 08 13:24:53 EDT 2014}
>>
>> Session:
>>
>> : Created:1404840293523
>>
>> : LastAccess:1404840396425
>>
>> : CreationDateAndTime:Tuesday, July 8, 2014
>>
>> : LastAccessDateAndTime:Tuesday, July 8, 2014
>>
>> : MaxInactive:3600
>>
>> : Attributes:
>>
>> : Attribute:portalskin:neoskin
>>
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
>>
>>
>>
>>
>>
>>
>> Disclaimer: This communication is intended solely for the use of the
>> individual or entity to whom it is addressed and others authorized to
>> receive it. It may contain confidential or legally privileged information.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution, or action taken in reliance upon the
>> information is strictly prohibited and is unlawful. If you have received
>> this communication by error, please notify us immediately by responding to
>> this email before deleting it from your system. UAE Exchange cannot be held
>> responsible for the improper or incomplete transmission of information
>> contained in this communication, or for any delay in its receipt.
>>
>> Warning: Internet communication cannot be guaranteed to be timely,
>> secure, error-free or virus-free. It is the responsibility of the recipient
>> to ensure that this email and its attachments, if any, are free from
>> viruses. UAE Exchange doesn't accept liability for any damage that may
>> result from viruses transmitted through this email.
>>
>> Please be informed that as per UAE Exchange Information Security policy,
>> we will never request you to disclose your Account Number, Credit Card
>> Information, User ID, Personal Identification Number (PIN), Telephone
>> Identification Number (TIN), Password or any such information through
>> e-mails or phone.
>>
>> Any e-mail or written communication received by you, which appears to
>> have been sent from UAE Exchange seeking your personal & confidential
>> information, should not be answered but advised to UAE Exchange at
>> info.sec at uaeexchange.com
>>
>> For further assistance email us at info.sec at uaeexchange.com.
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/a1c55444/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Thu, 10 Jul 2014 10:36:17 +0530
>> From: "Ismail Naik" <ismail.n at in.uaeexchange.com>
>> Subject: Re: [Building Sakai] Editing roles and permission
>> To: "'Kurosch Petzold'" <kurosch.petzold at fu-berlin.de>
>> Cc: sakai-dev at collab.sakaiproject.org
>> Message-ID: <020701cf9bfc$aeb07ee0$0c117ca0$@in.uaeexchange.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hi Kurosch,
>>
>> "AdminSitePerms" show the default/predefined sites and roles but, I like
>> to
>> add a new role(example: Team Lead, ...) or change existing roles to some
>> other name for any type of sites and that should reflect in AdminSitePerms
>> also, this is what I would like to know, any assistance is appreciable
>>
>>
>>
>>
>> Thanks & Regards
>> Ismail N. - IT Department
>> Xm Software Solutions Pvt Ltd | SKCL | CENTRAL SQUARE- 1
>> CIPET Road | Thiru-Vi-Ka? Industrial? Estate| Guindy | Chennai- 600032.
>> TEL: 044-30464899 | FAX: 044-30464861|
>> Ext:613
>> ismail.n at in.uaeexchange.com
>>
>> -----Original Message-----
>> From: sakai-dev-bounces at collab.sakaiproject.org
>> [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Kurosch
>> Petzold
>> Sent: 09 July 2014 17:41
>> To: sakai-dev at collab.sakaiproject.org
>> Subject: Re: [Building Sakai] Editing roles and permission
>>
>> Hey,
>>
>> if you mean the changes do not apply to existing sites, than yes that will
>> not work with the realms tool. Instead you should use the Admin site perms
>> tool to update the permissions from existing sites.
>>
>>
>> In Sakai the !site.template.<type> realms are basically classes out of
>> which
>> you create objects/instances when creating a course. If the class gets
>> updated the already existing courses will not be synchronized with the
>> template. This is where tools like UMUSYNC or the AdminSitePerms tool came
>> in handy as they synchronize the changes in one way or another (I know
>> that
>> UMUSYNC synchronizes the site objects with their classes and I am assuming
>> AdminSitePerms does the same?).
>> You could also use the sakai.helper realm to do this but I would not
>> recommend using it as it may be easily be forgotten etc.
>>
>> Best regards,
>> Kurosch
>>
>> > Greetings Team,
>> >
>> >
>> >
>> > Is there any way to edit the roles and permission in Sakai 10, I tried
>> > editing using the realms tool but I changes are not reflecting.
>> >
>> >
>> >
>> > Thanks & Regards
>> >
>> > Ismail N. - IT Department
>> >
>> > Xm Software Solutions Pvt Ltd | SKCL | CENTRAL SQUARE- 1
>> >
>> > CIPET Road | Thiru-Vi-Ka Industrial Estate| Guindy | Chennai- 600032.
>> >
>> > TEL: 044-30464899 | FAX: 044-30464861|
>> >
>> > Ext:613
>> >
>> > <mailto:ismail.n at in.uaeexchange.com> ismail.n at in.uaeexchange.com
>> >
>> >
>> >
>> >
>> > Disclaimer: This communication is intended solely for the use of the
>> > individual or entity to whom it is addressed and others authorized to
>> > receive it. It may contain confidential or legally privileged
>> information.
>> > If you are not the intended recipient, you are hereby notified that
>> > any disclosure, copying, distribution, or action taken in reliance
>> > upon the information is strictly prohibited and is unlawful. If you
>> > have received this communication by error, please notify us
>> > immediately by responding to this email before deleting it from your
>> > system. UAE Exchange cannot be held responsible for the improper or
>> > incomplete transmission of information contained in this
>> > communication, or for any delay in its receipt.
>> >
>> > Warning: Internet communication cannot be guaranteed to be timely,
>> > secure, error-free or virus-free. It is the responsibility of the
>> > recipient to ensure that this email and its attachments, if any, are
>> free
>> from viruses.
>> > UAE Exchange doesn't accept liability for any damage that may result
>> > from viruses transmitted through this email.
>> >
>> > Please be informed that as per UAE Exchange Information Security
>> > policy, we will never request you to disclose your Account Number,
>> > Credit Card Information, User ID, Personal Identification Number
>> > (PIN), Telephone Identification Number (TIN), Password or any such
>> > information through e-mails or phone.
>> >
>> > Any e-mail or written communication received by you, which appears to
>> > have been sent from UAE Exchange seeking your personal & confidential
>> > information, should not be answered but advised to UAE Exchange at
>> > info.sec at uaeexchange.com
>> >
>> > For further assistance email us at
>> > info.sec at uaeexchange.com._____________________________________________
>> > __
>> > sakai-dev mailing list
>> > sakai-dev at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >
>> > TO UNSUBSCRIBE: send email to
>> > sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> > "unsubscribe"
>>
>>
>> --
>> Best regards,
>> Kurosch Petzold
>>
>>
>> --
>> Best regards,
>> Kurosch Petzold
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
>>
>>
>> Disclaimer: This communication is intended solely for the use of the
>> individual or entity to whom it is addressed and others authorized to
>> receive it. It may contain confidential or legally privileged information.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution, or action taken in reliance upon the
>> information is strictly prohibited and is unlawful. If you have received
>> this communication by error, please notify us immediately by responding to
>> this email before deleting it from your system. UAE Exchange cannot be held
>> responsible for the improper or incomplete transmission of information
>> contained in this communication, or for any delay in its receipt. Warning:
>> Internet communication cannot be guaranteed to be timely, secure,
>> error-free or virus-free. It is the responsibility of the recipient to
>> ensure that this email and its attachments, if any, are free from viruses.
>> UAE Exchange doesn't accept liability for any dama
>> ge that may result from viruses transmitted through this email.
>>
>>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Thu, 10 Jul 2014 11:17:54 +0530
>> From: "Ismail Naik" <ismail.n at in.uaeexchange.com>
>> Subject: [Building Sakai] Site participants
>> To: <sakai-dev at collab.sakaiproject.org>
>> Message-ID: <021301cf9c02$7f047560$7d0d6020$@in.uaeexchange.com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Greetings Team,
>>
>> I couldn't able to get exact difference/meaning of "Non-official
>> Participants"(we are giving Email Address of Non-official Participant) and
>> "Other Official Participants"(we are giving Official Email Address or
>> Username), please do any one explain me what it is and what is the test
>> scenario.
>>
>>
>>
>> Thanks & Regards
>>
>> Ismail N. - IT Department
>>
>> Xm Software Solutions Pvt Ltd | SKCL | CENTRAL SQUARE- 1
>>
>> CIPET Road | Thiru-Vi-Ka Industrial Estate| Guindy | Chennai- 600032.
>>
>> TEL: 044-30464899 | FAX: 044-30464861|
>>
>> Ext:613
>>
>> <mailto:ismail.n at in.uaeexchange.com> ismail.n at in.uaeexchange.com
>>
>>
>>
>>
>> Disclaimer: This communication is intended solely for the use of the
>> individual or entity to whom it is addressed and others authorized to
>> receive it. It may contain confidential or legally privileged information.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution, or action taken in reliance upon the
>> information is strictly prohibited and is unlawful. If you have received
>> this communication by error, please notify us immediately by responding to
>> this email before deleting it from your system. UAE Exchange cannot be held
>> responsible for the improper or incomplete transmission of information
>> contained in this communication, or for any delay in its receipt.
>>
>> Warning: Internet communication cannot be guaranteed to be timely,
>> secure, error-free or virus-free. It is the responsibility of the recipient
>> to ensure that this email and its attachments, if any, are free from
>> viruses. UAE Exchange doesn't accept liability for any damage that may
>> result from viruses transmitted through this email.
>>
>> Please be informed that as per UAE Exchange Information Security policy,
>> we will never request you to disclose your Account Number, Credit Card
>> Information, User ID, Personal Identification Number (PIN), Telephone
>> Identification Number (TIN), Password or any such information through
>> e-mails or phone.
>>
>> Any e-mail or written communication received by you, which appears to
>> have been sent from UAE Exchange seeking your personal & confidential
>> information, should not be answered but advised to UAE Exchange at
>> info.sec at uaeexchange.com
>>
>> For further assistance email us at info.sec at uaeexchange.com.
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/be301457/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 8
>> Date: Thu, 10 Jul 2014 13:59:28 +0800
>> From: Gao Jun <gaojun at fudan.edu.cn>
>> Subject: Re: [Building Sakai] Site participants
>> To: Ismail Naik <ismail.n at in.uaeexchange.com>,
>> sakai-dev at collab.sakaiproject.org
>> Message-ID: <53BE2BC0.6000900 at fudan.edu.cn>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hi Ismail,
>>
>> 'Official Participants' means these users are already in Sakai, you can
>> add them by user name or email.
>>
>> 'Non-official Participants' means user hasn't got an account in Sakai
>> yet. If you add them with email, an email will be sent to their email
>> address with a link.
>>
>> Cheers,
>> Gao Jun
>>
>>
>>
>> ? 2014?07?10? 13:47, Ismail Naik ??:
>> >
>> > Greetings Team,
>> >
>> > I couldn't able to get exact difference/meaning of "*Non-official
>> > Participants*"(we are giving Email Address of Non-official
>> > Participant)*and "Other Official Participants*"(we are giving Official
>> > Email Address or Username), please do any one explain me what it is
>> > and what is the test scenario.
>> >
>> > *Thanks & Regards*
>> >
>> > *Ismail N**.*- IT Department**
>> >
>> > *X**m****Software**Solutions Pvt Ltd*| SKCL | CENTRAL SQUARE- 1
>> >
>> > CIPET Road | Thiru-Vi-Ka Industrial Estate| Guindy | Chennai- 600032.
>> >
>> > TEL: 044-30464899 | FAX: 044-30464861|
>> >
>> > Ext:613
>> >
>> > ismail.n at in.uaeexchange.com <mailto:ismail.n at in.uaeexchange.com>
>> >
>> > */Disclaimer/*: This communication is intended solely for the use of
>> > the individual or entity to whom it is addressed and others authorized
>> > to receive it. It may contain confidential or legally privileged
>> > information. If you are not the intended recipient, you are hereby
>> > notified that any disclosure, copying, distribution, or action taken
>> > in reliance upon the information is strictly prohibited and is
>> > unlawful. If you have received this communication by error, please
>> > notify us immediately by responding to this email before deleting it
>> > from your system. UAE Exchange cannot be held responsible for the
>> > improper or incomplete transmission of information contained in this
>> > communication, or for any delay in its receipt.
>> > */Warning/*: Internet communication cannot be guaranteed to be timely,
>> > secure, error-free or virus-free. It is the responsibility of the
>> > recipient to ensure that this email and its attachments, if any, are
>> > free from viruses. UAE Exchange doesn't accept liability for any
>> > damage that may result from viruses transmitted through this email.
>> > Please be informed that as per UAE Exchange Information Security
>> > policy, we will never request you to disclose your Account Number,
>> > Credit Card Information, User ID, Personal Identification Number
>> > (PIN), Telephone Identification Number (TIN), Password or any such
>> > information through e-mails or phone.
>> > Any e-mail or written communication received by you, which appears to
>> > have been sent from UAE Exchange seeking your personal & confidential
>> > information, should not be answered but advised to UAE Exchange at
>> > info.sec at uaeexchange.com.
>> > For further assistance email us at info.sec at uaeexchange.com.
>> >
>> >
>> >
>> > _______________________________________________
>> > sakai-dev mailing list
>> > sakai-dev at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >
>> > TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/ce11431f/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 9
>> Date: Thu, 10 Jul 2014 11:15:14 +0200
>> From: Jean-Francois Leveque <jean-francois.leveque at upmc.fr>
>> Subject: [Building Sakai] SCORM with Sakai 2.8 or later
>> To: "sakai-dev at collab.sakaiproject.org"
>> <sakai-dev at collab.sakaiproject.org>,
>> production at collab.sakaiproject.org,
>> sakai-user at collab.sakaiproject.org,
>> pedagogy at collab.sakaiproject.org
>> Cc: Dooremont <Frederic.Dooremont at univ-littoral.fr>, Fr?d?ric CELLA
>> <frederic.cella at upmc.fr>
>> Message-ID: <53BE59A2.6030103 at upmc.fr>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> Hi,
>>
>> I'm looking for the best SCORM 2004 Sakai module, including import and
>> export, that works with Sakai 2.8 or later and is as free (as in
>> freedom) as Sakai is.
>>
>> I've found a list in
>> https://confluence.sakaiproject.org/display/SCORMPLAYER/SCORM. Are there
>> modules not listed there that might fit my requirements?
>>
>> Which software that produces SCORM is compatible with the module(s) you
>> have experience with?
>>
>> Which are the know limits of SCORM compatibility with the module(s) you
>> have experience with?
>>
>> Regards,
>>
>> Jean-Francois Leveque
>>
>>
>> ------------------------------
>>
>> Message: 10
>> Date: Thu, 10 Jul 2014 11:38:53 +0200
>> From: "Kurosch Petzold" <kurosch.petzold at fu-berlin.de>
>> Subject: Re: [Building Sakai] Editing roles and permission
>> To: "Ismail Naik" <ismail.n at in.uaeexchange.com>
>> Cc: sakai-dev at collab.sakaiproject.org
>> Message-ID:
>> <53607.87.77.184.83.1404985133.webmail at webmail.zedat.fu-berlin.de
>> >
>> Content-Type: text/plain;charset=utf-8
>>
>> Hey Ismail,
>>
>> I checked on our test server and all the extra roles (secretary, research
>> assistant) and the extra site type (internal) we have on it show up in the
>> "AdminSitePerms" tool. You might need to restart tomcat/Sakai to get them
>> to show up in the tool, but I am not entirely sure. If this does not work
>> try to deploy UMUSYNC tool in Sakai 10 it definatly has that
>> functionality.[0]
>>
>> If you want to change the names you either go into the DB and change them
>> or copy existing ones with new names and delete the old one.
>>
>> Best regards,
>> Kurosch
>>
>> [0]
>>
>> https://confluence.sakaiproject.org/display/UMUSYNC/Sites+sync+tool+-+Umusync
>> > Hi Kurosch,
>> >
>> > "AdminSitePerms" show the default/predefined sites and roles but, I like
>> > to
>> > add a new role(example: Team Lead, ...) or change existing roles to some
>> > other name for any type of sites and that should reflect in
>> AdminSitePerms
>> > also, this is what I would like to know, any assistance is appreciable
>> >
>> >
>> >
>> >
>> > Thanks & Regards
>> > Ismail N. - IT Department
>> > Xm Software Solutions Pvt Ltd | SKCL | CENTRAL SQUARE- 1
>> > CIPET Road | Thiru-Vi-Ka? Industrial? Estate| Guindy | Chennai- 600032.
>> > TEL: 044-30464899 | FAX: 044-30464861|
>> > Ext:613
>> > ismail.n at in.uaeexchange.com
>> >
>> > -----Original Message-----
>> > From: sakai-dev-bounces at collab.sakaiproject.org
>> > [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Kurosch
>> > Petzold
>> > Sent: 09 July 2014 17:41
>> > To: sakai-dev at collab.sakaiproject.org
>> > Subject: Re: [Building Sakai] Editing roles and permission
>> >
>> > Hey,
>> >
>> > if you mean the changes do not apply to existing sites, than yes that
>> will
>> > not work with the realms tool. Instead you should use the Admin site
>> perms
>> > tool to update the permissions from existing sites.
>> >
>> >
>> > In Sakai the !site.template.<type> realms are basically classes out of
>> > which
>> > you create objects/instances when creating a course. If the class gets
>> > updated the already existing courses will not be synchronized with the
>> > template. This is where tools like UMUSYNC or the AdminSitePerms tool
>> came
>> > in handy as they synchronize the changes in one way or another (I know
>> > that
>> > UMUSYNC synchronizes the site objects with their classes and I am
>> assuming
>> > AdminSitePerms does the same?).
>> > You could also use the sakai.helper realm to do this but I would not
>> > recommend using it as it may be easily be forgotten etc.
>> >
>> > Best regards,
>> > Kurosch
>> >
>> >> Greetings Team,
>> >>
>> >>
>> >>
>> >> Is there any way to edit the roles and permission in Sakai 10, I tried
>> >> editing using the realms tool but I changes are not reflecting.
>> >>
>> >>
>> >>
>> >> Thanks & Regards
>> >>
>> >> Ismail N. - IT Department
>> >>
>> >> Xm Software Solutions Pvt Ltd | SKCL | CENTRAL SQUARE- 1
>> >>
>> >> CIPET Road | Thiru-Vi-Ka Industrial Estate| Guindy | Chennai- 600032.
>> >>
>> >> TEL: 044-30464899 | FAX: 044-30464861|
>> >>
>> >> Ext:613
>> >>
>> >> <mailto:ismail.n at in.uaeexchange.com> ismail.n at in.uaeexchange.com
>> >>
>> >>
>> >>
>> >>
>> >> Disclaimer: This communication is intended solely for the use of the
>> >> individual or entity to whom it is addressed and others authorized to
>> >> receive it. It may contain confidential or legally privileged
>> >> information.
>> >> If you are not the intended recipient, you are hereby notified that
>> >> any disclosure, copying, distribution, or action taken in reliance
>> >> upon the information is strictly prohibited and is unlawful. If you
>> >> have received this communication by error, please notify us
>> >> immediately by responding to this email before deleting it from your
>> >> system. UAE Exchange cannot be held responsible for the improper or
>> >> incomplete transmission of information contained in this
>> >> communication, or for any delay in its receipt.
>> >>
>> >> Warning: Internet communication cannot be guaranteed to be timely,
>> >> secure, error-free or virus-free. It is the responsibility of the
>> >> recipient to ensure that this email and its attachments, if any, are
>> >> free
>> > from viruses.
>> >> UAE Exchange doesn't accept liability for any damage that may result
>> >> from viruses transmitted through this email.
>> >>
>> >> Please be informed that as per UAE Exchange Information Security
>> >> policy, we will never request you to disclose your Account Number,
>> >> Credit Card Information, User ID, Personal Identification Number
>> >> (PIN), Telephone Identification Number (TIN), Password or any such
>> >> information through e-mails or phone.
>> >>
>> >> Any e-mail or written communication received by you, which appears to
>> >> have been sent from UAE Exchange seeking your personal & confidential
>> >> information, should not be answered but advised to UAE Exchange at
>> >> info.sec at uaeexchange.com
>> >>
>> >> For further assistance email us at
>> >> info.sec at uaeexchange.com._____________________________________________
>> >> __
>> >> sakai-dev mailing list
>> >> sakai-dev at collab.sakaiproject.org
>> >> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >>
>> >> TO UNSUBSCRIBE: send email to
>> >> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> >> "unsubscribe"
>> >
>> >
>> > --
>> > Best regards,
>> > Kurosch Petzold
>> >
>> >
>>
>>
>> --
>> Best regards,
>> Kurosch Petzold
>>
>>
>>
>> ------------------------------
>>
>> Message: 11
>> Date: Thu, 10 Jul 2014 11:39:59 +0200
>> From: "Kurosch Petzold" <kurosch.petzold at fu-berlin.de>
>> Subject: [Building Sakai] Metaobj Permissions
>> To: sakai-dev at collab.sakaiproject.org
>> Message-ID:
>> <53609.87.77.184.83.1404985199.webmail at webmail.zedat.fu-berlin.de
>> >
>> Content-Type: text/plain;charset=utf-8
>>
>> Hey guys,
>>
>> what are the Metaobj permissions used for? I cannot find any description
>> explaining their purpose.
>>
>>
>> Best regards,
>> Kurosch Petzold
>>
>>
>>
>> ------------------------------
>>
>> Message: 12
>> Date: Thu, 10 Jul 2014 10:47:45 +0000
>> From: Roger Brown <roger.brown at uct.ac.za>
>> Subject: [Building Sakai] Contrib tools and TOChelp.xml
>> To: "sakai-dev at collab.sakaiproject.org"
>> <sakai-dev at collab.sakaiproject.org>
>> Message-ID:
>> <
>> CDE30AFCA7C54049B4513EBEB4231A0786A4A36F at SRVWINEXC004.wf.uct.ac.za>
>> Content-Type: text/plain; charset="windows-1252"
>>
>>
>> Hi all
>>
>> Just need some clarity as to how to manage help for contrib tools via the
>> help TOC.
>>
>> For example I'd like the help information for Q&A to be available via TOC
>> > Instructor Guide > Q&A
>>
>> Can I just create <ref bean="AboutQnAInstructorGuide"> and drop the
>> beans from
>> https://source.sakaiproject.org/contrib/qna/tags/qna-1.1/help/src/sakai_qna/help.xml
>> (ie
>>
>> <bean id="qnaOverview"
>> class="org.sakaiproject.component.app.help.model.ResourceBean">
>> <property name="docId"><value>qnaOverview</value></property>
>> <property name="name"><value>Q&A
>> Overview</value></property>
>> <property
>> name="location"><value>/sakai_qna/QNA_Overview.html</value></property>
>> <property
>> name="defaultForTool"><value>sakai.qna</value></property>
>> </bean>
>>
>> )
>>
>> into the correct section of
>> ./src_mods/trunk/help/help/src/sakai_toc/help.xml
>>
>> If not can someone suggest how this can be done.
>>
>> At the moment our Sakai 10 help TOC is a mixture of hierarchies, viz
>>
>>
>> * Blogs *
>> * Group Manager *
>> * Instructor Guide
>> * Profile *
>> * SMS messages *
>> * Student guide
>>
>> The * items need moved into appropriate level.
>>
>> Cheers
>>
>> Roger
>>
>> Roger Brown
>> Learning Technologies Operations Manager
>> Centre for Innovation in Learning and Teaching (formerly CET and HAEDSU)
>> 7.58 PD Hahn Building Upper Campus
>> University of Cape Town
>> Email/IM/XMPP roger.brown at uct.ac.za
>> Skype rjg.brown
>> Tel:+27(21) 650 4425
>> ________________________________
>> UNIVERSITY OF CAPE TOWN
>>
>> This e-mail is subject to the UCT ICT policies and e-mail disclaimer
>> published on our website at
>> http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27
>> 21 650 9111. This e-mail is intended only for the person(s) to whom it
>> is addressed. If the e-mail has reached you in error, please notify the
>> author. If you are not the intended recipient of the e-mail you may not
>> use, disclose, copy, redirect or print the content. If this e-mail is not
>> related to the business of UCT it is sent by the sender in the sender's
>> individual capacity.
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/8bf964db/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 13
>> Date: Thu, 10 Jul 2014 13:07:04 +0200
>> From: Alex Ballest? <alexandre.balleste at udl.cat>
>> Subject: Re: [Building Sakai] enabling portal video chat on Sakai 10.x
>> To: sakai-dev at collab.sakaiproject.org, mustansar at rice.edu
>> Message-ID: <53BE73D8.5010908 at udl.cat>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hi Mustansar,
>> I think portal chat is enabled by default is sakai 10. The property to
>> enable/disable is
>> portal.neochat = true/false
>>
>>
>> If you want to have the video option you should enable a set of
>> properties:
>>
>> # 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 <http://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
>>
>>
>> You can find information about how to enable it to this document about
>> how video plugin works at
>>
>> https://docs.google.com/document/d/1UT3McN89QayB39nlPqe5g5G2Sc42KGMBGb0qnP4Y6H4/edit?usp=sharing
>>
>> In addition, if you want to run portal chat in a clustered environment
>> you must specify an ID for JGROUPS with the property
>> portalchat.cluster.channel=yourportachalid
>>
>> I hope it will help.
>>
>> Alex
>>
>>
>> On 07/10/2014 12:44 AM, Mustansar Mehmood wrote:
>> > Hi,
>> > I am not seeing portal chat(new video chat) on Sakai 10.x. Chances(a
>> > mere guess) are my sakai.properties needs adjustment. I am hoping
>> > somone can point me to the documentation on configuring that video
>> > chat feature or share working settings that I can throw into my
>> > properties file.
>> > Thanks,
>> > Mustansar
>> > --
>> > Mustansar Mehmood
>> > Educational System Developer& Integrator
>> >
>> > Information Technology
>> > 6100 Main St. MS 119
>> > Houston Texas 77005
>> >
>> > Phone:(713)348-2523
>> > Fax :(713)348 6099
>> > email:mustansar at rice.edu
>> >
>> >
>> >
>> >
>> >
>> > I have yet to see any problem, however complicated, which, when,you
>> looked at it in the right way, did not become still more complicated.
>> > -- Poul Anderson
>> >
>> >
>> >
>> > _______________________________________________
>> > sakai-dev mailing list
>> > sakai-dev at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >
>> > TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>>
>> --
>> Alexandre Ballest? Crevill?n alexandre.balleste at udl.cat
>> =====================
>> Universitat de Lleida
>> ?rea de sistemes d'Informaci? i Comunicacions
>> Analista/Programador
>>
>> University of Lleida
>> Information and Communication Systems Service
>> Analyst / Programmer
>>
>> Tlf: +34 973 702148
>> Fax: +34 973 702130
>> =====================
>>
>> Av?s legal/Aviso legal/Avertiment legal/Legal notice
>> http://www.imatge.udl.cat/avis_legal_lopd.html
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/94d06752/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 14
>> Date: Thu, 10 Jul 2014 08:12:10 -0400
>> From: Noah Botimer <botimer at umich.edu>
>> Subject: Re: [Building Sakai] Metaobj Permissions
>> To: "Kurosch Petzold" <kurosch.petzold at fu-berlin.de>
>> Cc: sakai-dev at collab.sakaiproject.org
>> Message-ID: <3F4BD1E8-E109-4EA4-AAFE-41E5778D0505 at umich.edu>
>> Content-Type: text/plain; charset=us-ascii
>>
>> These are for the Forms tool, which is almost exclusively used with OSP
>> Matrices and Presentations. When you see "metaobj", you can almost always
>> mentally substitute "form".
>>
>> Thanks,
>> -Noah
>>
>> On Jul 10, 2014, at 5:39 AM, Kurosch Petzold wrote:
>>
>> > Hey guys,
>> >
>> > what are the Metaobj permissions used for? I cannot find any description
>> > explaining their purpose.
>> >
>> >
>> > Best regards,
>> > Kurosch Petzold
>> >
>> > _______________________________________________
>> > sakai-dev mailing list
>> > sakai-dev at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >
>> > TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>>
>>
>> ------------------------------
>>
>> Message: 15
>> Date: Thu, 10 Jul 2014 09:25:29 -0400
>> From: Matthew Jones <matthew at longsight.com>
>> Subject: Re: [Building Sakai] [Contrib: Evaluation System] QA server
>> for evaluation trunk?
>> To: Neal Caidin <neal.caidin at apereo.org>
>> Cc: "evaluation at collab.sakaiproject.org"
>> <evaluation at collab.sakaiproject.org>, sakai-dev
>> <sakai-dev at collab.sakaiproject.org>
>> Message-ID:
>> <
>> CACz7-HQSwMh-f7SLgfZybNnbLovmG3cM7fcyKDMBE90sLZAnCw at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> FYI: Trunk experimental is back up this morning without Assignment 2.
>>
>> On Wed, Jul 9, 2014 at 2:36 PM, Matthew Jones <matthew at longsight.com>
>> wrote:
>>
>> > Yeah, I'm not going to be able to commit or change anything on A2, so
>> I'm
>> > removing that from experimental in hopes that the rest of the tools will
>> > come up.
>> >
>> > Likely someone will have to incorporate these changes into trunk and
>> have
>> > a branch for Sakai 10.0 and earlier.
>> >
>> >
>> > On Wed, Jul 9, 2014 at 8:36 AM, Neal Caidin <neal.caidin at apereo.org>
>> > wrote:
>> >
>> >> Right. I looked in the catalina.out instead of the build logs.
>> >>
>> >> Thanks for finding this!
>> >>
>> >> I hope someone has time to fix in the meantime!
>> >>
>> >> -- Neal
>> >>
>> >>
>> >> Matthew Jones <matthew at longsight.com>
>> >> July 8, 2014 at 3:34 PM
>> >> Looking at the build logs, it looks like this has been broken since
>> >> 02-Jul-2014
>> >>
>> >> From a variety of errors in Assignment 2 likely related to
>> >> https://jira.sakaiproject.org/browse/SAK-26601
>> >> [INFO] sakai-assignment2-impl ............................ FAILURE
>> >> [4.240s]
>> >> The quick fix is to remove assignment 2 from this build. I won't
>> >> personally be able to do anything else until probably next week though
>> >> others might.
>> >>
>> >>
>> >>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/64edae5c/attachment-0001.html
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: compose-unknown-contact.jpg
>> Type: image/jpeg
>> Size: 770 bytes
>> Desc: not available
>> Url :
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/64edae5c/attachment-0001.jpg
>>
>> ------------------------------
>>
>> Message: 16
>> Date: Thu, 10 Jul 2014 09:28:57 -0400
>> From: Neal Caidin <neal.caidin at apereo.org>
>> Subject: Re: [Building Sakai] [Contrib: Evaluation System] QA server
>> for evaluation trunk?
>> To: Matthew Jones <matthew at longsight.com>
>> Cc: "evaluation at collab.sakaiproject.org"
>> <evaluation at collab.sakaiproject.org>, sakai-dev
>> <sakai-dev at collab.sakaiproject.org>
>> Message-ID: <53BE9519.4030501 at apereo.org>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Thanks!
>>
>>
>> > Matthew Jones <mailto:matthew at longsight.com>
>> > July 10, 2014 at 9:25 AM
>> > FYI: Trunk experimental is back up this morning without Assignment 2.
>> >
>> > Matthew Jones <mailto:matthew at longsight.com>
>> > July 9, 2014 at 2:36 PM
>> > Yeah, I'm not going to be able to commit or change anything on A2, so
>> > I'm removing that from experimental in hopes that the rest of the
>> > tools will come up.
>> >
>> > Likely someone will have to incorporate these changes into trunk and
>> > have a branch for Sakai 10.0 and earlier.
>> >
>> >
>> >
>> > Neal Caidin <mailto:neal.caidin at apereo.org>
>> > July 9, 2014 at 8:36 AM
>> > Right. I looked in the catalina.out instead of the build logs.
>> >
>> > Thanks for finding this!
>> >
>> > I hope someone has time to fix in the meantime!
>> >
>> > -- Neal
>> >
>> >
>> >
>> > Matthew Jones <mailto:matthew at longsight.com>
>> > July 8, 2014 at 3:34 PM
>> > Looking at the build logs, it looks like this has been broken since
>> > 02-Jul-2014
>> >
>> > From a variety of errors in Assignment 2 likely related to
>> > https://jira.sakaiproject.org/browse/SAK-26601
>> > [INFO] sakai-assignment2-impl ............................ FAILURE
>> > [4.240s]
>> > The quick fix is to remove assignment 2 from this build. I won't
>> > personally be able to do anything else until probably next week though
>> > others might.
>> >
>> >
>> >
>> > Neal Caidin <mailto:neal.caidin at apereo.org>
>> > July 8, 2014 at 3:20 PM
>> > According to http://nightly2.sakaiproject.org , it is running on the
>> > Experimental build, http://nightly2.sakaiproject.org:8085/portal
>> > (though, ahem, it seems to be broken at the moment.)
>> >
>> >
>> https://source.sakaiproject.org/svn/sakai/branches/sakai-trunk-experimental/TOOLS.txt
>> >
>> > Can someone from sakai-dev please take a look at the Experimental
>> > build and see why it is failing?
>> >
>> > Looks like it might be a problem with the Archive tool?
>> >
>> > Jul 08, 2014 2:43:33 AM org.apache.catalina.startup.HostConfig deployWAR
>> > SEVERE: Error deploying web application archive
>> > /home/tomcat-contrib/sakai-demo/webapps/sakai-archive-tool.war
>> > java.lang.IllegalStateException: ContainerBase.addChild: start:
>> > org.apache.catalina.LifecycleException: Failed to start component
>> >
>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/sakai-archive-tool]]
>> > at
>> >
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
>> > at
>> > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> > at
>> > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>> > at
>> > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
>> > at
>> >
>> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1654)
>> > at
>> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> > at
>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>> > at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>> > at
>> >
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> > at
>> >
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> > at java.lang.Thread.run(Thread.java:722)
>> >
>> > Thanks,
>> > Neal
>> >
>> >
>> >
>>
>> --
>> Neal Caidin
>> Sakai Community Coordinator
>> Apereo Foundation
>> neal.caidin at apereo.org
>> Skype me! (but let me know in advance for the first interaction) -
>> nealkdin
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/3c04bbf5/attachment-0001.html
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: compose-unknown-contact.jpg
>> Type: image/jpeg
>> Size: 770 bytes
>> Desc: not available
>> Url :
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/3c04bbf5/attachment-0001.jpg
>>
>> ------------------------------
>>
>> Message: 17
>> Date: Thu, 10 Jul 2014 14:50:43 +0000
>> From: "Rashid, Amir" <arashid at bu.edu>
>> Subject: Re: [Building Sakai] SAKAI LDAP configuration
>> To: Ismail Naik <ismail.n at in.uaeexchange.com>, "'Steve Swinsburg'"
>> <steve.swinsburg at gmail.com>
>> Cc: "sakai-dev at collab.sakaiproject.org"
>> <sakai-dev at collab.sakaiproject.org>
>> Message-ID: <CFE41FE3.A49FF%arashid at bu.edu>
>> Content-Type: text/plain; charset="windows-1252"
>>
>> Thanks for your suggestions. Unfortunately the suggested changes to the
>> bean configuration did not resolve the issue for us.
>>
>> Please let us know if you see anything else that will help.
>>
>> --Amir
>>
>>
>> Amir Rashid - 617.358.2782
>> Boston University - SMG ITS
>>
>>
>> From: Ismail Naik <ismail.n at in.uaeexchange.com<mailto:
>> ismail.n at in.uaeexchange.com>>
>> Date: Thursday, July 10, 2014 at 12:42 AM
>> To: "Rashid, Amir" <arashid at bu.edu<mailto:arashid at bu.edu>>, 'Steve
>> Swinsburg' <steve.swinsburg at gmail.com<mailto:steve.swinsburg at gmail.com>>
>> Cc: "sakai-dev at collab.sakaiproject.org<mailto:
>> sakai-dev at collab.sakaiproject.org>" <sakai-dev at collab.sakaiproject.org
>> <mailto:sakai-dev at collab.sakaiproject.org>>
>> Subject: RE: [Building Sakai] SAKAI LDAP configuration
>>
>> Hi Team,
>>
>> We faced same issue, just do the below changes and try the luck.
>>
>>
>> ? Comment out the eidValidator
>>
>> <!--
>>
>> <!-- Optional. If you don't provide an eidValidator the system
>>
>> defaults to allowing searches on any EID, including empty
>>
>> and null Strings. -->
>>
>> <property name="eidValidator">
>>
>> <bean
>> class="edu.amc.sakai.user.RegexpBlacklistEidValidator">
>>
>> <property name="regexpFlags">
>>
>> <bean
>> id="java.util.regex.Pattern.CASE_INSENSITIVE"
>>
>>
>> class="org.springframework.beans.factory.config.FieldRetrievingFactoryBean"
>> />
>>
>> </property>
>>
>> <property name="eidBlacklist">
>>
>> <list>
>>
>> <value>null</value>
>>
>> <!--value>nobody</value-->
>>
>>
>> <!--value>adversary</value-->
>>
>> </list>
>>
>> </property>
>>
>> </bean>
>>
>> </property>
>>
>> <property
>> name="searchAliases"><value>false</value></property>
>> -->
>>
>>
>> ? Make followReferrals as true
>>
>> <property name="followReferrals">
>> <value>true</value>
>> </property>
>>
>>
>>
>> ? Use the folloing keys for attributeMappings and use your values
>>
>> <property name="attributeMappings">
>> <map>
>> <entry
>> key="login"><value>sAMAccountName</value></entry>
>> <entry
>> key="firstName"><value></value></entry>
>> <entry
>> key="preferredFirstName">user ur prefereedFirstName<value> </value></entry>
>> <entry key="lastName"><value> this
>> is okay</value></entry>
>> <entry
>> key="email"><value>mail</value></entry>
>> </map>
>> </property>
>>
>>
>> Thanks & Regards
>> Ismail N. - IT Department
>> XmSoftware Solutions Pvt Ltd | SKCL | CENTRAL SQUARE- 1
>> CIPET Road | Thiru-Vi-Ka Industrial Estate| Guindy | Chennai- 600032.
>> TEL: 044-30464899 | FAX: 044-30464861|
>> Ext:613
>> ismail.n at in.uaeexchange.com<mailto:ismail.n at in.uaeexchange.com>
>>
>> From: sakai-dev-bounces at collab.sakaiproject.org<mailto:
>> sakai-dev-bounces at collab.sakaiproject.org> [mailto:
>> sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Rashid, Amir
>> Sent: 09 July 2014 18:44
>> To: Steve Swinsburg
>> Cc: sakai-dev at collab.sakaiproject.org<mailto:
>> sakai-dev at collab.sakaiproject.org>
>> Subject: Re: [Building Sakai] SAKAI LDAP configuration
>>
>> Yes. Infact I have a 2.8.1 instance on the same machine with the same
>> LDAP setting that will boot up without any issues.
>>
>> --Amir
>>
>>
>> Amir Rashid - 617.358.2782
>> Boston University - SMG ITS
>>
>>
>> From: Steve Swinsburg <steve.swinsburg at gmail.com<mailto:
>> steve.swinsburg at gmail.com>>
>> Date: Wednesday, July 9, 2014 at 9:05 AM
>> To: "Rashid, Amir" <arashid at bu.edu<mailto:arashid at bu.edu>>
>> Cc: "sakai-dev at collab.sakaiproject.org<mailto:
>> sakai-dev at collab.sakaiproject.org>" <sakai-dev at collab.sakaiproject.org
>> <mailto:sakai-dev at collab.sakaiproject.org>>
>> Subject: Re: [Building Sakai] SAKAI LDAP configuration
>>
>> Ok so using those same parameters are you able to perform an ldapsearch
>> on the commandline of your Sakai server for a given user?
>>
>> On Wed, Jul 9, 2014 at 10:58 PM, Rashid, Amir <arashid at bu.edu<mailto:
>> arashid at bu.edu>> wrote:
>> Hi
>> Following properties are being used in the jldap-beans.xml file.
>> Thanks,
>> --Amir
>>
>>
>> Amir Rashid - 617.358.2782
>> Boston University - SMG ITS
>>
>>
>> <property name="memoryService">
>>
>> <ref
>> bean="org.sakaiproject.memory.api.MemoryService"/>
>>
>> </property>
>>
>>
>>
>> <!-- Required. Host name or address of your LDAP server
>> -->
>>
>> <property name="ldapHost">
>>
>> <value>XX.XX.XXX</value>
>>
>> </property>
>>
>>
>>
>> <!-- Optional. LDAP connection port. Typically defaults to
>>
>> JLDAPDirectoryProvider.DEFAULT_LDAP_PORT (389).
>> Secured
>>
>> connections are usually on 636 -->
>>
>> <property name="ldapPort">
>>
>> <value>389</value>
>>
>> </property>
>>
>>
>>
>> <!-- If secureConnection is true, a keystore location
>> must be provided
>>
>> unless javax.net.ssl.trustStore system property
>> has already been
>>
>> set -->
>>
>> <!--property name="keystoreLocation">
>>
>> <value>/usually/set/at/startup</value>
>>
>> </property-->
>>
>>
>>
>> <!-- If secureConnection is true, a keystore password
>> must be provided
>>
>> unless javax.net.ssl.trustStorePassword system
>> property has already
>>
>> been set -->
>>
>> <!--property name="keystorePassword">
>>
>> <value>usually-set-at-startup</value>
>>
>> </property-->
>>
>>
>>
>> <!-- Optional. DN to which to bind for directory searches.
>>
>> Typically only necessary if autoBind is true -->
>>
>> <property name=?ldapUser?>
>>
>>
>> <value>cn=XXXXXXX,OU=people,dc=XX,dc=XX,dc=XXX</value>
>>
>> </property>
>>
>>
>>
>> <!-- Optional. Password for ldapUser defined above -->
>>
>> <property name=?ldapPassword?>
>>
>> <value>XXXXXXXXXX</value>
>>
>> </property>
>>
>>
>>
>> <!-- Optional. Enables/disables secure LDAP connections.
>>
>> defaults to
>> JLDAPDirectoryProvider.DEFAULT_IS_SECURE_CONNECTION (false) -->
>>
>> <property name="secureConnection">
>>
>> <value>false</value>
>>
>> </property>
>>
>> <!-- Optional. Indicate if connection allocation should
>>
>> implicitly bind as ${ldapUser}. Defaults to false
>> -->
>>
>> <property name="autoBind">
>>
>> <value>true</value>
>>
>> </property>
>>
>> <!-- Optional, but usually specified. Base DN for directory searches. -->
>>
>> <property name="basePath">
>>
>> <value>dc=XX,dc=XX,dc=XXX</value>
>>
>> </property>
>>
>>
>>
>> <!-- Optional. Indicate if connections should follow
>>
>> referrals. Defaults to
>>
>>
>> JLDAPDirectoryProvider.DEFAULT_IS_FOLLOW_REFERRALS (false)-->
>>
>> <property name="followReferrals">
>>
>> <value>false</value>
>>
>> </property>
>>
>> <property name="caseSensitiveCacheKeys">
>>
>> <value>false</value>
>>
>> </property>
>>
>> <property name="ldapAttributeMapper">
>>
>> <ref
>> bean="edu.amc.sakai.user.LdapAttributeMapper" />
>>
>> </property>
>>
>> <!-- Optional. If you don't provide an eidValidator the system
>>
>> defaults to allowing searches on any EID, including empty
>>
>> and null Strings. -->
>>
>> <property name="eidValidator">
>>
>> <bean
>> class="edu.amc.sakai.user.RegexpBlacklistEidValidator">
>>
>> <property name="regexpFlags">
>>
>> <bean
>> id="java.util.regex.Pattern.CASE_INSENSITIVE"
>>
>>
>> class="org.springframework.beans.factory.config.FieldRetrievingFactoryBean"
>> />
>>
>> </property>
>>
>> <property name="eidBlacklist">
>>
>> <list>
>>
>> <value>null</value>
>>
>> <!--value>nobody</value-->
>>
>>
>> <!--value>adversary</value-->
>>
>> </list>
>>
>> </property>
>>
>> </bean>
>>
>> </property>
>>
>> <property
>> name="searchAliases"><value>false</value></property>
>>
>>
>>
>> </bean>
>>
>>
>>
>> <!-- An optional bean definition which can be used to customize LDAP
>>
>> attribute to Sakai User instance member mapping behaviors. This
>>
>> example describes availabel configuration options for
>> SimpleLdapAttributeMapper
>>
>> (the default LdapAttributeMapper implementation). -->
>>
>> <bean id="edu.amc.sakai.user.LdapAttributeMapper"
>>
>>
>> class="edu.amc.sakai.user.SimpleLdapAttributeMapper"
>>
>> init-method="init"
>>
>> singleton="true">
>>
>>
>>
>> <!-- A typical set of attribute mappings. Keys are logical
>>
>> names expected by the application. Values are physical
>> LDAP
>>
>> attribute names. If not specified or empty, defaults to
>>
>> AttributeMappingConstants.DEFAULT_ATTR_MAPPINGS. -->
>>
>> <property name="attributeMappings">
>>
>> <map>
>>
>> <entry
>> key="login"><value>sAMAccountName</value></entry>
>>
>> <entry
>> key="firstName"><value>givenName</value></entry>
>>
>> <!--entry
>> key="preferredFirstName"><value>preferredName</value></entry-->
>>
>> <entry
>> key="lastName"><value>sn</value></entry>
>>
>> <entry
>> key="email"><value>mail</value></entry>
>>
>> <entry
>> key="groupMembership"><value>groupMembership</value></entry>
>>
>> <!--entry
>> key="jpegPhoto"><value>jpegPhoto</value></entry -->
>>
>> </map>
>>
>> </property>
>>
>>
>>
>> <!-- Several options for calculating Sakai user types
>> based
>>
>> on LDAP attributes. Defaults to an instance of
>> EmptyStringUserTypeMapper -->
>>
>> <property name="userTypeMapper">
>>
>> <!-- Select one of the following beans -->
>>
>> <!--ref
>> bean="edu.amc.sakai.user.EmptyStringUserTypeMapper" /-->
>>
>> <!-- ref
>> bean="edu.amc.sakai.user.EntryAttributeToUserTypeMapper" /-->
>>
>> <!-- ref
>> bean="edu.amc.sakai.user.EntryContainerRdnToUserTypeMapper" /-->
>>
>> <ref
>> bean="edu.amc.sakai.user.StringUserTypeMapper" />
>>
>> </property>
>>
>>
>>
>> </bean>
>>
>>
>>
>>
>>
>>
>> From: Steve Swinsburg <steve.swinsburg at gmail.com<mailto:
>> steve.swinsburg at gmail.com>>
>> Date: Tuesday, July 8, 2014 at 11:56 PM
>> To: "Rashid, Amir" <arashid at bu.edu<mailto:arashid at bu.edu>>
>> Cc: "sakai-dev at collab.sakaiproject.org<mailto:
>> sakai-dev at collab.sakaiproject.org>" <sakai-dev at collab.sakaiproject.org
>> <mailto:sakai-dev at collab.sakaiproject.org>>
>> Subject: Re: [Building Sakai] SAKAI LDAP configuration
>>
>> Looks like you need to provide a username and password in the LDAP config
>> to get a bind. What are your LDAP settings from jldap-beans.xml ?
>>
>> On Wed, Jul 9, 2014 at 5:36 AM, Rashid, Amir <arashid at bu.edu<mailto:
>> arashid at bu.edu>> wrote:
>>
>> Hi Folks,
>>
>> I have 2.81 in production right now. I am using one of the test machine
>> to install SAKAI 10. I am trying to configure it to use LDAP the same as
>> 2.8. Included is the trace from the log file. I can intermittently log in
>> if I try it a few times. Please let me know if there are any undocumented
>> configuration changes to the LDAP configuration settings .
>>
>> I will appreciate your help in this matter.
>>
>> --Amir
>>
>>
>> Amir Rashid - 617.358.2782
>> Boston University - SMG ITS
>>
>>
>> 2014-07-08 13:26:36,428 WARN ajp-bio-8009-exec-14
>> org.sakaiproject.portal.util.ErrorReporter - Bug Report bug-id:
>> 573880ae-c5b0-42f5-8b47-534991e591a0 user: null usage-session: null time:
>> Jul 8, 2014 13:26:36 user comment: null stack trace
>> org.sakaiproject.portal.api.PortalHandlerException:
>> java.lang.RuntimeException: authenticateUser(): LDAPException during
>> authentication attempt [userLogin = arashid][result code = Operations
>> Error][error message = 00000000: LdapErr: DSID-0C090627, comment: In order
>> to perform this operation a successful bind must be completed on the
>> connection., data 0, vece]
>> at
>> org.sakaiproject.portal.charon.handlers.ReLoginHandler.doPost(ReLoginHandler.java:50)
>> caused by: java.lang.RuntimeException: authenticateUser(): LDAPException
>> during authentication attempt [userLogin = arashid][result code =
>> Operations Error][error message = 00000000: LdapErr: DSID-0C090627,
>> comment: In order to perform this operation a successful bind must be
>> completed on the connection., data 0, vece]
>> at
>> org.sakaiproject.user.impl.BaseUserDirectoryService.getProviderAuthenticatedUser(BaseUserDirectoryService.java:1668)
>> caused by: LDAPException: Operations Error (1) Operations Error
>> LDAPException: Server Message: 00000000: LdapErr: DSID-0C090627, comment:
>> In order to perform this operation a successful bind must be completed on
>> the connection., data 0, vece
>> LDAPException: Matched DN:
>> at com.novell.ldap.LDAPResponse.getResultException(null:-1)
>> at com.novell.ldap.LDAPResponse.chkResultCode(null:-1)
>> at com.novell.ldap.LDAPSearchResults.next(null:-1)
>> at
>> edu.amc.sakai.user.JLDAPDirectoryProvider.searchDirectory(JLDAPDirectoryProvider.java:959)
>> at
>> edu.amc.sakai.user.JLDAPDirectoryProvider.searchDirectoryForSingleEntry(JLDAPDirectoryProvider.java:856)
>> at
>> edu.amc.sakai.user.JLDAPDirectoryProvider.getUserByEid(JLDAPDirectoryProvider.java:778)
>> at
>> edu.amc.sakai.user.JLDAPDirectoryProvider.lookupUserBindDn(JLDAPDirectoryProvider.java:820)
>> at
>> edu.amc.sakai.user.JLDAPDirectoryProvider.authenticateUser(JLDAPDirectoryProvider.java:397)
>> at
>> org.sakaiproject.user.impl.BaseUserDirectoryService.getProviderAuthenticatedUser(BaseUserDirectoryService.java:1668)
>> at
>> org.sakaiproject.user.impl.BaseUserDirectoryService.authenticate(BaseUserDirectoryService.java:1611)
>> at
>> org.sakaiproject.user.impl.UserAuthnComponent.authenticate(UserAuthnComponent.java:108)
>> at
>> org.sakaiproject.login.impl.LoginServiceComponent.authenticate(LoginServiceComponent.java:90)
>> at
>> org.sakaiproject.login.tool.SkinnableLogin.doPost(SkinnableLogin.java:302)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:394)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:378)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
>> at
>> org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.help(ActiveToolComponent.java:583)
>> at
>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doLogin(SkinnableCharonPortal.java:997)
>> at
>> org.sakaiproject.portal.charon.handlers.ReLoginHandler.doGet(ReLoginHandler.java:65)
>> at
>> org.sakaiproject.portal.charon.handlers.ReLoginHandler.doPost(ReLoginHandler.java:50)
>> at
>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doPost(SkinnableCharonPortal.java:1296)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:455)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
>> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:193)
>> at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
>> at
>> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> Tool Placement:
>> No Placement
>>
>> Request:
>> : AuthType:null
>> : CharEncoding:UTF-8
>> : ContentLength:38
>> : ContentType:application/x-www-form-urlencoded
>> : ContextPath:/portal
>> : LocalAddress:smgcms1.bu.edu<http://bu.edu/>
>> : LocalName:smgcms1.bu.edu<http://smgcms1.bu.edu/>
>> : LocalPort:443
>> : Method:POST
>> : PathInfo:/relogin
>> : Protocol:HTTP/1.1
>> : QueryString:null
>> : RemoteAddress:168.122.33.194
>> : RemoteHost:168.122.33.194
>> : RemotePort:-1
>> : Requested URL:https://smgcms1.bu.edu/portal/relogin<
>> http://smgcms1.bu.edu/portal/relogin>
>> : Scheme:https
>> : ServerName:smgcms1.bu.edu<http://smgcms1.bu.edu/>
>> : Headers:
>> : Header:host:smgcms1.bu.edu<http://bu.edu/>
>> : Header:connection:keep-alive
>> : Header:content-length:38
>> : Header:Cache-Control:max-age=0
>> :
>> Header:accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
>> : Header:Origin:https://smgcms1.bu.edu<http://smgcms1.bu.edu/>
>> : Header:user-agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4)
>> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36
>> : Header:content-type:application/x-www-form-urlencoded
>> : Header:DNT:1
>> : Header:referer:https://smgcms1.bu.edu/portal/login<
>> http://smgcms1.bu.edu/portal/login>
>> : Header:accept-encoding:gzip,deflate,sdch
>> : Header:accept-language:en-US,en;q=0.8
>> : Header:cookie:---censored---
>> : Parameters:
>> : Parameter:eid:0:----censored----
>> : Parameter:pw:0:----censored----
>> : Parameter:submit:0:Login
>> : Attributes:
>> :
>> Attribute:javax.servlet.request.ssl_session:1C4C47A3FFAEEA4FAF017B65F33A916271C8B1293EB3487C9F7EEC25B8206C46
>> :
>> Attribute:javax.servlet.request.ssl_session_id:1C4C47A3FFAEEA4FAF017B65F33A916271C8B1293EB3487C9F7EEC25B8206C46
>> :
>> Attribute:sakai.character.encoding.done:sakai.character.encoding.done
>> : Attribute:javax.servlet.request.key_size:128
>> : Attribute:sakai.filtered:sakai.filtered
>> : Attribute:javax.servlet.request.cipher_suite:DHE-RSA-AES128-SHA
>> :
>> Attribute:sakai.session:MyS_null{60cc469c-90b1-4a78-9bce-f06c3cc1c81a,
>> userId='null', at=8, ts=2, cs=2, Tue Jul 08 13:24:53 EDT 2014}
>> Session:
>> : Created:1404840293523
>> : LastAccess:1404840396425
>> : CreationDateAndTime:Tuesday, July 8, 2014
>> : LastAccessDateAndTime:Tuesday, July 8, 2014
>> : MaxInactive:3600
>> : Attributes:
>> : Attribute:portalskin:neoskin
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org<mailto:
>> sakai-dev at collab.sakaiproject.org>
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:
>> sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of
>> "unsubscribe"
>>
>>
>>
>> Disclaimer: This communication is intended solely for the use of the
>> individual or entity to whom it is addressed and others authorized to
>> receive it. It may contain confidential or legally privileged information.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution, or action taken in reliance upon the
>> information is strictly prohibited and is unlawful. If you have received
>> this communication by error, please notify us immediately by responding to
>> this email before deleting it from your system. UAE Exchange cannot be held
>> responsible for the improper or incomplete transmission of information
>> contained in this communication, or for any delay in its receipt.
>> Warning: Internet communication cannot be guaranteed to be timely,
>> secure, error-free or virus-free. It is the responsibility of the recipient
>> to ensure that this email and its attachments, if any, are free from
>> viruses. UAE Exchange doesn't accept liability for any damage that may
>> result from viruses transmitted through this email.
>> Please be informed that as per UAE Exchange Information Security policy,
>> we will never request you to disclose your Account Number, Credit Card
>> Information, User ID, Personal Identification Number (PIN), Telephone
>> Identification Number (TIN), Password or any such information through
>> e-mails or phone.
>> Any e-mail or written communication received by you, which appears to
>> have been sent from UAE Exchange seeking your personal & confidential
>> information, should not be answered but advised to UAE Exchange at
>> info.sec at uaeexchange.com<mailto:info.sec at uaeexchange.com>.
>> For further assistance email us at info.sec at uaeexchange.com<mailto:
>> info.sec at uaeexchange.com>.
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/b6cda82a/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 18
>> Date: Thu, 10 Jul 2014 14:29:01 -0400
>> From: Neal Caidin <neal.caidin at apereo.org>
>> Subject: [Building Sakai] Save the Date! Sakai Virtual Conference 2014
>> "Bridging Education with Technology" - Nov. 7th
>> To: sakai-dev <sakai-dev at collab.sakaiproject.org>, Sakai QA
>> <sakai-qa at collab.sakaiproject.org>,
>> "production at collab.sakaiproject.org"
>> <production at collab.sakaiproject.org>,
>> "sakai-user at collab.sakaiproject.org"
>> <sakai-user at collab.sakaiproject.org>,
>> "pedagogy at collab.sakaiproject.org" <
>> pedagogy at collab.sakaiproject.org>,
>> "portfolio at collab.sakaiproject.org"
>> <portfolio at collab.sakaiproject.org>, "
>> i18n at collab.sakaiproject.org"
>> <i18n at collab.sakaiproject.org>,
>> "accessibility at collab.sakaiproject.org"
>> <accessibility at collab.sakaiproject.org>,
>> "sakai-docs at collab.sakaiproject.org"
>> <sakai-docs at collab.sakaiproject.org>
>> Cc: "sakai-pmc at collab.sakaiproject.org"
>> <sakai-pmc at collab.sakaiproject.org>
>> Message-ID: <53BEDB6D.9010607 at apereo.org>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> [all Sakai related collab lists]
>>
>>
>> Make plans now to attend the Sakai Virtual Conference on Friday,
>> November 7th!
>>
>>
>> The conference will be held entirely online, and will have an emphasis
>> on pedagogy and best practices. Join us for a faculty-friendly day of
>> learning, sharing and community building with your fellow Sakai users,
>> all without the need to travel!
>>
>>
>> More details coming soon.
>>
>>
>> Sincerely,
>>
>>
>> Ian Dolphin, Executive Director, Apereo Foundation
>>
>> Neal Caidin, Sakai Community Coordinator, Apereo Foundation
>>
>> Wilma Hodges, Sakai Virtual Conference 2014 Planning Committee Chair
>>
>>
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/4af7168b/attachment-0001.html
>>
>> ------------------------------
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>>
>> End of sakai-dev Digest, Vol 65, Issue 10
>> *****************************************
>>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140716/225112ee/attachment.html
More information about the sakai-dev
mailing list