← Back to team overview

mahara-contributors team mailing list archive

[Bug 548165] Re: Increase length of username column to 255 to support shibboleth/SSO userIDs

 

Hi Jeffrey,

The bug was marked as "incomplete" because we asked a question and the
original submitter didn't respond.

But now that youv'e confirmed that it is still needed, we'll schedule
that fix for the next release.

Cheers,
Francois

** Changed in: mahara
    Milestone: None => 1.4.0

** Changed in: mahara
       Status: Incomplete => Confirmed

** Changed in: mahara
     Assignee: (unassigned) => François Marier (fmarier)

-- 
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
  username@xxxxxxxxxx) is not provider to the SP, the SP can either use
  the SAML1 eduPersonTargetedID attribute (which looks like
  e54710df7638d6c9@xxxxxxxxxx) 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=detail&aid=3424&group_id=176&atid=739