[
http://jira.amdatu.org/jira/browse/AMDATU-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10806#comment-10806
]
Koos Gadellaa commented on AMDATU-261:
--------------------------------------
In a similar vein, having a space in the username makes it impossible to use
(and remove) the user.
For example: 'http://openid.luminis.net/users/koosg' works fine, but
'http://openid.luminis.net/users/koosg ' (note the space at the end) doesnt.
I have no problem with not accepting usernames with spaces, but these are
actually made/created and cannot be removed ('Role cannot be found').
I think at least a notification that the username was unacceptable (or support
spaces in some (maybe visible) way)
> useradmin restlets cannot handle urls as username -> this crashes wink(!)
> -------------------------------------------------------------------------
>
> Key: AMDATU-261
> URL: http://jira.amdatu.org/jira/browse/AMDATU-261
> Project: Amdatu
> Issue Type: Bug
> Reporter: Koos Gadellaa
> Assignee: Marcel Offermans
> Priority: Critical
> Fix For: 0.1.0
>
>
> A bit of a weird exception occuring, so I'll explain a bit first.
> We're using OpenId for login, and to use that in Amdatu we (currently)
> automaticly create users with the username equal to the openid identity. I.e.
> for google my openid identity is
> https://www.google.com/accounts/o8/id?id=AItOawkQnSOdRj3W7ZaQf_kW6f-hmuktTi3JRlc,
> so that becomes my username (and similarly,
> https://openid.luminis.net/users/koosg for the luminis openid server).
> When logging in with this user everything works fine, however, when adding
> the useradmin gadget and trying to use it a stackoverflow occurs:
> java.lang.StackOverflowError
> at java.util.regex.Pattern.sequence(Pattern.java:1885)
> at java.util.regex.Pattern.expr(Pattern.java:1752)
> at java.util.regex.Pattern.compile(Pattern.java:1460)
> at java.util.regex.Pattern.<init>(Pattern.java:1133)
> at java.util.regex.Pattern.compile(Pattern.java:823)
> at java.lang.String.split(String.java:2292)
> at
> org.apache.wink.common.internal.UriBuilderImpl.path(UriBuilderImpl.java:555)
> at
> org.apache.wink.common.internal.UriBuilderImpl.schemeSpecificPart(UriBuilderImpl.java:886)
> at
> org.apache.wink.common.internal.UriBuilderImpl.path(UriBuilderImpl.java:565)
> at
> org.apache.wink.common.internal.UriBuilderImpl.schemeSpecificPart(UriBuilderImpl.java:886)
> at
> org.apache.wink.common.internal.UriBuilderImpl.path(UriBuilderImpl.java:565)
> at
> org.apache.wink.common.internal.UriBuilderImpl.schemeSpecificPart(UriBuilderImpl.java:886)
> at
> org.apache.wink.common.internal.UriBuilderImpl.path(UriBuilderImpl.java:565)
> This comes straight from the restlet (i.e. calling the restservice with the
> proper values) this error occurs. Hence, the problem lies with the
> rest-services.
> I created a wink issue for this
> (https://issues.apache.org/jira/browse/WINK-331) which was promptly fixed,
> but I'm not sure if this is the actual issue.
> After some more testing, I found out that it actualy is related to the user:
> when i add the user, the restlet crashes (even if I'm not logged in with that
> specific user). When I remove that user (all by hand), the restlet works
> again.
> It is somewhat strange that wink gives this error; i'm guessing something
> wrong is fed back to wink.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
