EID can't contain slashes ("/")
Activity
Matthew Jones April 24, 2018 at 10:35 AM
Bulk closing issues that have not been updated since 2015 and earlier. Please reopen if this is still an issue and you have new information or if this is a feature you'd like to still have consideration for.
Matthew Jones March 3, 2011 at 8:39 AM
I agree that something should be done internally to encode these url unsafe characters in userids. The openid example is a good case as many providers like google user the openid of "http://www.google.com/profiles/username".
It seems the best way is going to be to urlencode the userid so that they're all supported. We could use the standard and encode "/" as "%2F" but we also have to make sure to encode "%" as "%25". If the % is a problem, we could use any other symbol (like say "2F") but we'd have to make sure to encode the "" everywhere as well, and provide a conversion for actual "-" characters.
This seems like something that would certainly be nice to fix though.
Jean-François Lévêque March 3, 2011 at 8:12 AM
AFAICT, Alan was using an internal account, so no EID was involved.
amberg1 February 16, 2011 at 6:30 AM
On qa1-nl.sakaiproject.org
2.8 beta 5
Created a new account test/123 on the from page. You get logged in automatically and then you see the work site. After that the URL's do not work as for example ~/test/123 does not make sense.
The user account exists and you can login again later
Ian Boston January 29, 2009 at 2:28 AM
I am unassigning this issue as it gives the wrong impression. I dont have enough hours in the day to look at this issue at the moment and keeping it assigned to me give the reporter hope that I might be able to look at it. I am very sorry. If this issue is a real blocker for production then I would suggest you look for resource in the community to fix the problem, I am happy to respond to emails and guide. Where the code base is Rwiki or Search, I have absolutely no problem with someone else working on the code, this after all is a community.
Details
Priority
MajorAffects versions
Fix versions
Components
Assignee
UnassignedUnassignedReporter
Matthew BuckettMatthew Buckett
Details
Details
Priority
Major
Although the user service can create users with EIDs that contain slashes("/") other parts of sakai don't seem to work with them.
This came up on sakai-dev:
http://thread.gmane.org/gmane.comp.cms.sakai.devel/8610/
Now it would seem that we should just be able to encode slashes as %2F in URLs but this doesn't work when the %2F is in the path info. To get tomcat to accept %2F in path info you need to add an additional flag to tomcat
-Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true
this is documented on:
http://tomcat.apache.org/security-5.html#Fixed in Apache Tomcat 5.5.22, 5.0.SVN
but the portal parses the path based on the container decoded URL (getPathInfo()) which means %2F has already been turned into /. If we want to allow "/" in EIDs then we should get the portal to use the undecoded URL and then decode it after splitting it.
This issues may well affect other parts of Sakai that put the EID in the URL (access, webdav).