Steps to reproduce:
      1. Navigate to JIRA Administration > User Management > Create User
      2. Enter the following username with whitespace (sample):
      3. Result: Username with white space is created:

            [JRASERVER-37508] JIRA Allows The Creation of Usernames With Whitespace

            This might have been fixed with https://ecosystem.atlassian.net/browse/APL-1256

            Krystian Brazulewicz added a comment - This might have been fixed with https://ecosystem.atlassian.net/browse/APL-1256

            I was wondering why our Confluence JIRA integration was broken. Thought it is our mistake. Now I discovered this one and APL-1195.

            I know it is not a good practice to allow white space in user names and non-english speakers might note consider funny characters, but the world is heterogeneous!

            Please fix this problem! Should not be rocket science to do as Niels already pointed out!

            Big problem!
            I tried to update the application link by deleting the old one and creating a new one from scratch. Out of convenience I was using my user name and not administrator
            Too bad my name contains white space
            Now I can't even remove the application links anymore due to this stupid bug!

            Fix it! Please!
            Joerg

            Joerg Sauer added a comment - I was wondering why our Confluence JIRA integration was broken. Thought it is our mistake. Now I discovered this one and APL-1195. I know it is not a good practice to allow white space in user names and non-english speakers might note consider funny characters, but the world is heterogeneous! Please fix this problem! Should not be rocket science to do as Niels already pointed out! Big problem! I tried to update the application link by deleting the old one and creating a new one from scratch. Out of convenience I was using my user name and not administrator Too bad my name contains white space Now I can't even remove the application links anymore due to this stupid bug! Fix it! Please! Joerg

            Hi niels.keurentjes,

            Thanks for showing your interest in this fix. Unfortunately, this is currently not in our short-term backlog as we are currently working through higher priority issues in other areas of JIRA.

            Having said that it is still an issue we would like to address in the long term, as it gathers more votes and interest from other customers. Could you please add your vote to this? Please do watch the issue, I will update it as soon as more information is available on it.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi niels.keurentjes , Thanks for showing your interest in this fix. Unfortunately, this is currently not in our short-term backlog as we are currently working through higher priority issues in other areas of JIRA. Having said that it is still an issue we would like to address in the long term, as it gathers more votes and interest from other customers. Could you please add your vote to this? Please do watch the issue, I will update it as soon as more information is available on it. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Is this ever going to be fixed? As proven by https://jira.atlassian.com/browse/BAM-15261 this is a very fundamental bug in your REST/XML layers, which are shared by every Atlassian app. Just tell a developer to add a single 'urlencode' call and all of those bugs will be fixed at once...

            As for 'preventing this in the JIRA Internal Directory': that reminds me of a programmer I once spoke who just solved SQL injection issues by disallowing apostrophes in content as a whole. Needless to say, workarounds are never a substitute for just using proper escaping in the right locations.

            Niels Keurentjes added a comment - Is this ever going to be fixed? As proven by https://jira.atlassian.com/browse/BAM-15261 this is a very fundamental bug in your REST/XML layers, which are shared by every Atlassian app. Just tell a developer to add a single 'urlencode' call and all of those bugs will be fixed at once... As for 'preventing this in the JIRA Internal Directory': that reminds me of a programmer I once spoke who just solved SQL injection issues by disallowing apostrophes in content as a whole. Needless to say, workarounds are never a substitute for just using proper escaping in the right locations.

            We can prevent this in the JIRA Internal Directory, however there's no feasible way we can prevent this coming to JIRA from an LDAP directory. Therefore applinks needs to be able to handle this scenario and a fix for https://ecosystem.atlassian.net/browse/APL-1195 is needed as well.

            CC: mminns

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - We can prevent this in the JIRA Internal Directory, however there's no feasible way we can prevent this coming to JIRA from an LDAP directory. Therefore applinks needs to be able to handle this scenario and a fix for https://ecosystem.atlassian.net/browse/APL-1195 is needed as well. CC: mminns Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            We found out this bug when user reported there's a problem rendering jira issues macro when user's username has a white space. In Confluence when you check the user profile, you'll see that the username contained '+' character e.g Hanis+Khaidir

            The user was created in JIRA and sync to Confluence

            Stack trace in Confluence logs:

            Caused by: java.net.URISyntaxException: Illegal character in query at index 231: http://localhost:8080/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=key+in+%28AAS-101%29&returnMax=true&field=summary&field=type&field=resolution&field=status&field=link&xoauth_requestor_id=Hanis Khaidir
            	at java.net.URI$Parser.fail(Unknown Source)
            	at java.net.URI$Parser.checkChars(Unknown Source)
            	at java.net.URI$Parser.parseHierarchical(Unknown Source)
            	at java.net.URI$Parser.parse(Unknown Source)
            	at java.net.URI.<init>(Unknown Source)
            

            User workaround the problem by changing the usernames in JIRA following this documentation:
            https://confluence.atlassian.com/display/JIRAKB/Cannot+rename+users+despite+upgrading+to+or+installing+JIRA+6

            Although this resulted in a lot of new users being created as explained in the page, but after removing them the problem is resolved.

            Hanis Suhailah (Inactive) added a comment - - edited We found out this bug when user reported there's a problem rendering jira issues macro when user's username has a white space. In Confluence when you check the user profile, you'll see that the username contained '+' character e.g Hanis+Khaidir The user was created in JIRA and sync to Confluence Stack trace in Confluence logs: Caused by: java.net.URISyntaxException: Illegal character in query at index 231: http: //localhost:8080/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=key+in+%28AAS-101%29&returnMax= true &field=summary&field=type&field=resolution&field=status&field=link&xoauth_requestor_id=Hanis Khaidir at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.<init>(Unknown Source) User workaround the problem by changing the usernames in JIRA following this documentation: https://confluence.atlassian.com/display/JIRAKB/Cannot+rename+users+despite+upgrading+to+or+installing+JIRA+6 Although this resulted in a lot of new users being created as explained in the page, but after removing them the problem is resolved.

              Unassigned Unassigned
              hsuhailah Hanis Suhailah (Inactive)
              Affected customers:
              17 This affects my team
              Watchers:
              24 Start watching this issue

                Created:
                Updated: