← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1798495] Re: Resource name maximum length is not defined in limits

 

Reviewed:  https://review.openstack.org/611484
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=2e85dc47c9301b00f89bd44955534f8d9631e3d6
Submitter: Zuul
Branch:    master

commit 2e85dc47c9301b00f89bd44955534f8d9631e3d6
Author: Vishakha Agarwal <agarwalvishakha18@xxxxxxxxx>
Date:   Wed Oct 17 16:43:15 2018 +0530

    Set min and max length for resource_name
    
    This patch addresses the problem of HTTP 500 on
    create and set of limit with lengthy resource_name.
    It sets the minLength and maxLength in schema for
    resource_name and if the string length of resource_
    name exceeds the defined schema it will raise 404.
    Includes test case too.
    
    Change-Id: If408e81edec81c649c42bd4907156fbcdbc967ee
    Closes-Bug: #1798495


** Changed in: keystone
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1798495

Title:
  Resource name maximum length is not defined in limits

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  When giving resource_name while creating/updating registered or
  project limits a user can provide a lengthy string which raises 500.
  It should give 400 bad request when it passes a string more than max
  length.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1798495/+subscriptions


References