On Wed, Sep 28, 2016 at 10:55 PM Adrian Turjak <adri...@catalyst.net.nz> wrote:
> I think with PKI tokens we had worse to worry about! > > At any rate, would be great to know, and if there isn't a strong reason > against it we can make project name 255 for some more flexibility. > It's nice for UI's like horizon and openstackclient to have reasonable expectations around max length. AFAIK, 64 characters is arbitrary and intended to cover the 99% use case. Other than trying to use DN's as user names and such, I believe this is the first objection I've ever seen to 64 characters. > > Plus although there is no true official standard, most projects in > OpenStack seem to use 255 as the default for a lot of string fields. > Weirdly enough, a lot of projects seem to use 255 even for project.id, > which seeing as it's 64 in keystone, and a uuid4 anyway, seems like a bit > of a waste. > > > > On 29/09/16 16:19, Steve Martinelli wrote: > > We may have to ask Adam or Dolph, or pull out the history textbook for > this one. I imagine that trying to not bloat the token was definitely a > concern. IIRC User name was 64 also, but we had to increase to 255 because > we're not in control of name that comes from external sources (like LDAP). > > On Wed, Sep 28, 2016 at 11:06 PM, Adrian Turjak <adri...@catalyst.net.nz> > wrote: > > Hello Keystone Devs, > > Just curious as to the choice to have the project name be only 64 > characters: > > https://github.com/openstack/keystone/blob/master/keystone/resource/backends/sql.py#L241 > > Seems short, and an odd choice when the user.name field is 255 characters: > > https://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql_model.py#L216 > > Is there a good reason for it only being 64 characters, or is this just > something that was done a long time ago and no one thought about it? > > Not hugely important, just seemed odd and may prove limiting for > something I'm playing with. > > Cheers, > Adrian Turjak > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- -Dolph
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev