I was reading a bit about this (I manage a LDAP server, but I am far from a specialist) and the format is actually too flexible: Any UTF-8 encoding with up to 64 characters.
I suspect basic punctation marks would be enough. Though I could see a Windows based SSO system (AD) accepting spaces and maybe even that being a usual convention (just speculating here).
But _s and .s are probably very common across existing installations.
On 2016-08-08 11:21, James Taylor wrote:
I don't think there is any good reason. Public username's main purpose originally was to generate slugs for URLs so we left out "-". Shouldn't break anything to add it.
On Mon, Aug 8, 2016 at 12:24 PM, Björn Grüning bjoern.gruening@gmail.com wrote:
Does anyone know why we have this restriction? Can we change it?
Am 08.08.2016 um 17:31 schrieb Tiago Antao:
Sorry, that was what I meant and explained myself poorly.
This is actually a very serious problem if one wants to integrate Galaxy in an existing SSO environment based on LDAP.
Tiago
On 2016-08-08 09:28, Nicola Soranzo wrote:
Actually it's Galaxy (not the LDAP integration) that doesn't allow underscores in usernames, in fact if you try to register a new user on e.g. usegalaxy.org and the username has an underscore, you'll get this error:
Public name must contain only lowercase letters, numbers and "-". It also has to be shorter than 255 characters but longer than 2.
Cheers, Nicola
On 08/08/16 16:08, Tiago Antao wrote:
Hi,
A serious problem that I have found with Galaxy integration with LDAP is that it does not allow underscores in the user name, and that is very common with production LDAP servers.
On 2016-08-08 09:01, Nicola Soranzo wrote:
Hi Miuki, the file config/auth_conf.xml.sample contains examples and documentation of possible values that you have to put in your config/auth_conf.xml , unfortunately a lot depends on what LDAP/Active Directory server you are using and how it is configured. You may need to ask advice to the system administrators of your LDAP server. If you have specific questions/problems, feel free to ask here on the mailing list and/or on the IRC channel.
Cheers, Nicola
On 01/08/16 20:45, Yip, Miu ki wrote: > Hi, > > I’m trying to configure a new instance of Galaxy and I want to > use > LDAP for user authentication. I have taken a look at this wiki > page: > https://wiki.galaxyproject.org/Admin/Config/ExternalUserAuth > > I followed the instructions and when I looked into the > auth_conf.xml file, I was unsure of what exactly Galaxy is > looking > for when trying to connect with LDAP. Are there specific options > that I must give it? May I ask how Galaxy uses LDAP to > authenticate > users? > > Thank you, > Miuki Yip > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > https://lists.galaxyproject.org/ > > To search Galaxy mailing lists use the unified search at: > http://galaxyproject.org/search/mailinglists/
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/