Ticket #356 (closed Bug report: invalid)

Opened 12 years ago

Last modified 12 years ago

Database access configuration refuses to accept Host name supplied

Reported by: dondruce@… Owned by:
Priority: low Milestone: Not yet assigned to a Milestone
Component: Auth server, Authentication, permissions and access control Version:
Keywords: localhost Cc:

Description

I have created several Captive Auth Servers. Each an every time, I have problems in understanding and configuring the Host setting when I get to the Database access configuration acreen.  in the installation process

The default is "localhost" I have tried changing it, and I can not get to the Database connection screen unless I leave the default "localhost" in the Host box.

Attachments

Database_access_configuration.JPG Download (111.7 KB) - added by dondruce@… 12 years ago.
Success and Failure views - localhost and captiveserver
Database access configuration.JPG Download (165.2 KB) - added by dondruce@… 12 years ago.
What I think would be clearer
Database Configuration.JPG Download (27.2 KB) - added by dondruce@… 12 years ago.
If I have this correct, perhaps this would help others
Database connection folly July 24, 07 alt.JPG Download (74.6 KB) - added by dondruce@… 12 years ago.
Problem text seems to have changed see msg on mailing list

Change History

Changed 12 years ago by dondruce@…

Success and Failure views - localhost and captiveserver

Changed 12 years ago by dondruce@…

To clarify my text. See attached file Database_access_configuration.JPG (Screen Shot)

I interpreted the line "By clicking Next, your configuration will be automaticaly saved" to mean that:

If I click on the Next button, my configuration which I interpret to be the Host - the DB Name - the Username and the Password settings that I gave would be automatically saved .

In the example, I expected that the Host would be named captiveserver DB Name would be database Username would be user Password would be password.

Changed 12 years ago by dondruce@…

What I think would be clearer

Changed 12 years ago by dondruce@…

If I have this correct, perhaps this would help others

Changed 12 years ago by dondruce@…

Problem text seems to have changed see msg on mailing list

Changed 12 years ago by benoitg

  • status changed from new to closed
  • resolution set to invalid

None of those are bugs. Providing a hostname that does not resolve anywhere will not work, and there is nothing we can do about it. Same with a user that fails authentication for any reason. In both case the underlying problem (which we cannot detect) must be fixed.

Note: See TracTickets for help on using tickets.