[Mahara-contributors] [Bug 548165] Re: Increase length of username column to 255 to support shibboleth/SSO userIDs
Is there any way we can get this fix committed to 1.3.7? We've arrived at our upgrade window (THIS WEEK!) and I see it's committed to 1.4, which isn't an official release. Thanks! -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/548165 Title: Increase length of username column to 255 to support shibboleth/SSO userIDs Status in Mahara ePortfolio: Fix Committed Bug description: get_new_username in lib/user.php truncates username to 30 characters by default. In some cases this is too short. As an example I have modified the SimpleSAMLPhP authenticator to use the Internet2 Shibboleth SAML service provider (SP). In cases where the eduPersonPrincipleName attribute (which look like usern...@domain.com) is not provider to the SP, the SP can either use the SAML1 eduPersonTargetedID attribute (which looks like e54710df7638d...@domain.com) or the serialized SAML2 NameID (which looks like !IdP-entityID!SP-entityID!lq7q48crsqzyqehetxahzcgi/bc= and the entityIDs have the form of a URL) as usernames. 30 characters is far to small to handle this and more over the varchar(100) username field in the various tables like 'usr' will impact on this issue aswell. My guess is that you should be looking atleast 256 or 512 characters for this. PS. This is an issue for both SSP and Shibboleth. This bug was imported from eduforge.org, see: https://eduforge.org/tracker/index.php?func=detailaid=3424group_id=176atid=739 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/548165/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 548165] Re: Increase length of username column to 255 to support shibboleth/SSO userIDs
I'm still hungry for this. Upgrade coming...thanks -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/548165 Title: Increase length of username column to 255 to support shibboleth/SSO userIDs Status in Mahara ePortfolio: In Progress Bug description: get_new_username in lib/user.php truncates username to 30 characters by default. In some cases this is too short. As an example I have modified the SimpleSAMLPhP authenticator to use the Internet2 Shibboleth SAML service provider (SP). In cases where the eduPersonPrincipleName attribute (which look like usern...@domain.com) is not provider to the SP, the SP can either use the SAML1 eduPersonTargetedID attribute (which looks like e54710df7638d...@domain.com) or the serialized SAML2 NameID (which looks like !IdP-entityID!SP-entityID!lq7q48crsqzyqehetxahzcgi/bc= and the entityIDs have the form of a URL) as usernames. 30 characters is far to small to handle this and more over the varchar(100) username field in the various tables like 'usr' will impact on this issue aswell. My guess is that you should be looking atleast 256 or 512 characters for this. PS. This is an issue for both SSP and Shibboleth. This bug was imported from eduforge.org, see: https://eduforge.org/tracker/index.php?func=detailaid=3424group_id=176atid=739 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 548165] Re: Increase length of username column to 255 to support shibboleth/SSO userIDs
François: I'm trying to understand your comment, to be sure it does not affect how we do things. We do not allow users to change their username, since we're SSO-ing from Moodle, and want to maintain parity. Your What needs to be done here... would only affect those installs which allow username changes, right? -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/548165 Title: Increase length of username column to 255 to support shibboleth/SSO userIDs Status in Mahara ePortfolio: In Progress Bug description: get_new_username in lib/user.php truncates username to 30 characters by default. In some cases this is too short. As an example I have modified the SimpleSAMLPhP authenticator to use the Internet2 Shibboleth SAML service provider (SP). In cases where the eduPersonPrincipleName attribute (which look like usern...@domain.com) is not provider to the SP, the SP can either use the SAML1 eduPersonTargetedID attribute (which looks like e54710df7638d...@domain.com) or the serialized SAML2 NameID (which looks like !IdP-entityID!SP-entityID!lq7q48crsqzyqehetxahzcgi/bc= and the entityIDs have the form of a URL) as usernames. 30 characters is far to small to handle this and more over the varchar(100) username field in the various tables like 'usr' will impact on this issue aswell. My guess is that you should be looking atleast 256 or 512 characters for this. PS. This is an issue for both SSP and Shibboleth. This bug was imported from eduforge.org, see: https://eduforge.org/tracker/index.php?func=detailaid=3424group_id=176atid=739 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 548165] Re: Increase length of username column to 255 to support shibboleth/SSO userIDs
Any progress on this? My beta install is ready to test changes. Thanks. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/548165 Title: Increase length of username column to 255 to support shibboleth/SSO userIDs Status in Mahara ePortfolio: Confirmed Bug description: get_new_username in lib/user.php truncates username to 30 characters by default. In some cases this is too short. As an example I have modified the SimpleSAMLPhP authenticator to use the Internet2 Shibboleth SAML service provider (SP). In cases where the eduPersonPrincipleName attribute (which look like usern...@domain.com) is not provider to the SP, the SP can either use the SAML1 eduPersonTargetedID attribute (which looks like e54710df7638d...@domain.com) or the serialized SAML2 NameID (which looks like !IdP-entityID!SP-entityID!lq7q48crsqzyqehetxahzcgi/bc= and the entityIDs have the form of a URL) as usernames. 30 characters is far to small to handle this and more over the varchar(100) username field in the various tables like 'usr' will impact on this issue aswell. My guess is that you should be looking atleast 256 or 512 characters for this. PS. This is an issue for both SSP and Shibboleth. This bug was imported from eduforge.org, see: https://eduforge.org/tracker/index.php?func=detailaid=3424group_id=176atid=739 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 548165] Re: Increase length of username column to 255 to support shibboleth/SSO userIDs
OK, where are we with this? I'm doing a beta upgrade this month, with an intended full upgrade of our production system the first week in June. My current version, Mahara version 1.3.2 (2010083108), still shows this bug, and a SSO AD username migration slated for the same time will greatly expand our username length. I need this but fixed! Thanks. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/548165 Title: Increase length of username column to 255 to support shibboleth/SSO userIDs Status in Mahara ePortfolio: Incomplete Bug description: get_new_username in lib/user.php truncates username to 30 characters by default. In some cases this is too short. As an example I have modified the SimpleSAMLPhP authenticator to use the Internet2 Shibboleth SAML service provider (SP). In cases where the eduPersonPrincipleName attribute (which look like usern...@domain.com) is not provider to the SP, the SP can either use the SAML1 eduPersonTargetedID attribute (which looks like e54710df7638d...@domain.com) or the serialized SAML2 NameID (which looks like !IdP-entityID!SP-entityID!lq7q48crsqzyqehetxahzcgi/bc= and the entityIDs have the form of a URL) as usernames. 30 characters is far to small to handle this and more over the varchar(100) username field in the various tables like 'usr' will impact on this issue aswell. My guess is that you should be looking atleast 256 or 512 characters for this. PS. This is an issue for both SSP and Shibboleth. This bug was imported from eduforge.org, see: https://eduforge.org/tracker/index.php?func=detailaid=3424group_id=176atid=739 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 548165] Re: Increase length of username column to 255 to support shibboleth/SSO userIDs
...bug fixed...*sigh*... -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/548165 Title: Increase length of username column to 255 to support shibboleth/SSO userIDs Status in Mahara ePortfolio: Incomplete Bug description: get_new_username in lib/user.php truncates username to 30 characters by default. In some cases this is too short. As an example I have modified the SimpleSAMLPhP authenticator to use the Internet2 Shibboleth SAML service provider (SP). In cases where the eduPersonPrincipleName attribute (which look like usern...@domain.com) is not provider to the SP, the SP can either use the SAML1 eduPersonTargetedID attribute (which looks like e54710df7638d...@domain.com) or the serialized SAML2 NameID (which looks like !IdP-entityID!SP-entityID!lq7q48crsqzyqehetxahzcgi/bc= and the entityIDs have the form of a URL) as usernames. 30 characters is far to small to handle this and more over the varchar(100) username field in the various tables like 'usr' will impact on this issue aswell. My guess is that you should be looking atleast 256 or 512 characters for this. PS. This is an issue for both SSP and Shibboleth. This bug was imported from eduforge.org, see: https://eduforge.org/tracker/index.php?func=detailaid=3424group_id=176atid=739 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 683664] Re: access file ...denied in view ...
The triage mentioned above doesn't seem related to my issue, but the symptoms are the same. (See http://mahara.org/interaction/forum/topic.php?id=2467 and http://mahara.org/interaction/forum/topic.php?id=2645#post11611). The problem is the rebuild_artefact_parent_cache_complete routine needing more memory than the config cap will allow. We currently have just short of 3,000 users, and the artifact_parent_cache table is almost 40,000 records (lots of views with directory/subdirectory chains). I actually haven't tested to see how much memory the routine actually requires, but it's definitely well over 512 meg, I've currently set PHP to unlimited memory usage, and, needless to say, I'm scared.(though the Access denied messages are gone). -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/683664 Title: access file ...denied in view ... Status in Mahara ePortfolio: Triaged Bug description: Specs : Operating SystemLinux CentOS MySQL-client versie: 5.1.52 Mahara 1.3.3 What I do : 1. Upload file in My Files 2. make it available in a view OK 1. Make a folder 2. make a subfolder 3. Upload file in subfolder 4. Make folder available (including subfolder) 5. Make folder available in view 6. Click on subfolder with file no download details, only filename 7. Click on filename Access Denied You do not have access to view this page Artefact 91 not in View 9 - What I did meanwhile : - maharaData = 775 - Checked in cpanel permissions, new artefacs maps are 700 - put up Cron job - truncate activity queue table ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 520739] Re: internalmedia flv
Evan: Thanks for the work. I'm thinking this is two problems - 1) successful delivery of the FLV file type as embedded media, and 2) availability of the FLV file type through the Insert media block process. In ver. 1.2.3, the file type does not appear in the list of media. Did that get nailed as well? Thanks again. -- internalmedia flv https://bugs.launchpad.net/bugs/520739 You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Status in Mahara ePortfolio: Fix Committed Bug description: FLV is checked under file/internalmedia/config - however, when adding an Embedded media block when creating a view, an uploaded FLV file is not available from the file selection block. Other media types DO appear there. Mahara 1.2.3 (SSO from Moodle 1.9.4), MySQL, Windows Server 2003. ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
