[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
Hi Jeffrey, 1.4.0 will be going out today, so you might want to upgrade to that. Otherwise, you can apply these two commits over your copy of 1.3 installation: 5f1ad871938686be816b2e4816e9221b43e5461c 4b152ba57eacaa106b1aeef7b1f3e9a346863018 Cheers, Francois -- 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
** Changed in: mahara Status: Fix Committed = Fix Released -- 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 Released 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
** Changed in: mahara Assignee: (unassigned) = Hugh Davenport (hugh-catalyst) ** Changed in: mahara Status: Confirmed = In Progress -- 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
What needs to be done here: - increase the field in the DB (and update upgrade script, etc.) - only let admins change a username to one larger than 30 characters - if user change their own username (i.e. internal auth), then they are limited to 30 characters ** Changed in: mahara Assignee: PiersHarding (piersharding) = (unassigned) -- 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
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 548165] Re: Increase length of username column to 255 to support shibboleth/SSO userIDs
I'd quite like to get Piers Harding's opinion on this before we just go ahead with it. I think he found a workaround for this in the saml auth plugin using the remoteusername field instead of the username. If that could work, it'd have the advantage of keeping usernames human-readable, which most non-SSO sites would prefer. But it may be that it's not appropriate to use that field for ldap. -- 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
Alright, let's assign it to Piers so that he can give us some feedback. ** Changed in: mahara Assignee: François Marier (fmarier) = PiersHarding (piersharding) -- 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
** Changed in: mahara Status: Triaged = Incomplete -- 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
