Would the 409 error code is enough to trigger the default error behavior in the UX? The same red X icon would probably suffice to let users know we don't like their choice.
e On Wed, Jun 27, 2012 at 11:38 AM, Erik Froese <[email protected]> wrote: > Hey all, > > We've recently found that creating a user with the name Admin causes > some bad stuff to happen, namely, you can't log in through the UX as > admin anymore. > I think it might be time to add some logic in order to prevent bad > usernames from being created in the system. > > Could we add this to the user.exists.html endpoint? > > /system/userManager/user.exists.html?userid=$username > > HTTP responses: > 204 (OK No Content): A User with that username (or case-variant) > exists on the system. > 404 (Not found): User name is valid and can be used to create a new > user authorizable. > ** 409 (Conflict): The user name is used or conflicts with internal > configuration (aka evil names regex or list) > > My hand it up to JIRA and implement this. It shouldn't take very long > to add a regex property to the LiteUserExistsServlet.java > > Erik _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
