Resource name maximum length is not defined in limits

Bug #1798495 reported by Vishakha Agarwal on 2018-10-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Low
Vishakha Agarwal

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.

Changed in keystone:
assignee: nobody → Vishakha Agarwal (vishakha.agarwal)

Fix proposed to branch: master
Review: https://review.openstack.org/611484

Changed in keystone:
status: New → In Progress
wangxiyuan (wangxiyuan) on 2018-10-19
Changed in keystone:
importance: Undecided → Low

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 <email address hidden>
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
Changed in keystone:
milestone: none → stein-1

This issue was fixed in the openstack/keystone 15.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers