Hi,
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
Great, thanks Nicola!
Am 08.08.2016 um 23:53 schrieb Nicola Soranzo:
> There is one already: https://github.com/galaxyproject/galaxy/issues/2593
>
> I may take a stab at it in the next days.
>
> Cheers,
> Nicola
>
> Björn Grüning ha scritto
>
>>
>>
>> Am 08.08.2016 um 20:14 schrie
There is one already: https://github.com/galaxyproject/galaxy/issues/2593
I may take a stab at it in the next days.
Cheers,
Nicola
Björn Grüning ha scritto
>
>
>Am 08.08.2016 um 20:14 schrieb Tiago Antao:
>> I was reading a bit about this (I manage a LDAP server, but I am far
>> fr
Am 08.08.2016 um 20:14 schrieb Tiago Antao:
> 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
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 an
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
wrote:
> Does anyone know why we have this restriction? Can we change it?
>
> Am
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.
>
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
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
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
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 sy
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 wh
12 matches
Mail list logo
