Project

General

Profile

Actions

Bug #6536

open

LDAP: Trying to create an LDAP instance with the name 'Internal' returns confusing message.

Added by Dominic Cleal almost 10 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Authentication
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1097683
Description of problem:
When trying to create/associate an LDAP source that has the name "Internal", user is told that the name "has already been taken" -- this despite perhaps never having set up an LDAP source before at all.

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140508.1

How reproducible:

Steps to Reproduce:
1. Attempt to create a new LDAP source. Give this source the name "Internal"
2. Fill in other details; submit
3. View results.

Actual results:

name cannot be used because "has already been taken"

Expected results:

I assume that the term "Internal" might probably be reserved or something, not sure. In any case, we should tell users they can't use that term, or provide some context indicating why exactly "Internal" can't be used.

Additional info:

Actions #1

Updated by Dominic Cleal almost 10 years ago

  • Category set to Authentication
  • Assignee deleted (Dominic Cleal)
Actions #2

Updated by The Foreman Bot over 9 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 1.7.2
  • Pull request https://github.com/theforeman/foreman/pull/1830 added
Actions #3

Updated by Dominic Cleal almost 8 years ago

  • Status changed from Ready For Testing to New
  • Pull request deleted (https://github.com/theforeman/foreman/pull/1830)
Actions #4

Updated by Tomer Brisker almost 6 years ago

  • Target version deleted (1.7.2)
Actions

Also available in: Atom PDF