Fields such as the "Crowd server" field (ambiguous as to just what constitutes a valid entry here as well -- hostname? IP address? URL?) don't do any basic validation and will accept any random string with no form error upon storing the data. User only finds out if what he entered might be correct upon trying to log into Drupal and then being blocked (except for uid 1) because of misconfiguration, and/or failure of crowd module to even be able to contact Crowd successfully, even when correctly configured.

At a minimum, some basic validation should be done, and better, a test button provided to check whether entered values result in crowd module actually being able to contact Crowd. See all issue #1030238: Module reports WSDL successfully cached upon failure wherein crowd module claims to have successfully cached WSDL when in fact it has not.

Comments

ebeyrent’s picture

Assigned: Unassigned » ebeyrent
rjacobs’s picture

Status: Active » Closed (won't fix)

Due to limited maintainer resources and the fact that some focus is shifting to the 2.x branch I'm taking the liberty of closing 1.x issues that are older than 2 years. This will make monitoring the queues a bit easier. If anyone feels this is a problem, please re-open.

rjacobs’s picture

Assigned: ebeyrent » Unassigned