Bug 2132 – Server responds with "Valid credentials could not be found..."

Bug 2132 - Server responds with "Valid credentials could not be found..."

Summary:

Server responds with "Valid credentials could not be found..."

Status:	RESOLVED FIXED

Product:	GridFTP
Component:	GridFTP
Version:	development
Platform:	PC Linux

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Mike Link

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2004-10-22 11:50 by Tom Fredian
Modified:	2004-10-22 17:01 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Tom Fredian 2004-10-22 11:50:21

Using the newer globus-gridftp-server from the HEAD of the cvs repository the 
server responds with the following:

"500-Valid credentials could not be found in any of the possible locations 
specified by the credential search order.
500-
500-Attempt 1
500-
500-globus_credential: Error reading host credential
500-globus_sysconfig: File is not owned by current user: /etc/grid-
security/hostcert.pem is not owned by current user
500-
500-Attempt 2
500-
500-globus_credential: Error reading proxy credential
500-globus_sysconfig: File does not exist: /tmp/x509up_u1004 is not a valid 
file
500-
500-Attempt 3
500-
500-globus_credential: Error reading user credential
500-OpenSSL Error: pem_lib.c:401: in library: PEM routines, function 
PEM_do_header: bad password read
500-
500 End.

The client command issued is:

# globus-url-copy file:///file-spec gsiftp://host/file-spec

The same behavior occurs when globus-gridftp-server is run from xinetd or in 
daemon mode from a terminal using:

# globus-gridftp-server -s -p 2811

------- Comment #1 From Tom Fredian 2004-10-22 14:07:34 -------

The problem will ony show up if there is no proxy certificate in /tmp for the
user on the server side. The easiest way to test this is to map your DN to
another account on the server which has not done a grid-proxy-init.

------- Comment #2 From Mike Link 2004-10-22 17:01:14 -------

This has been fixed in a development branch, it will be merged to the trunk
within a few days.

Mike