Print

Print


Hi again,

  since there was a recent naming transition xrootd4->xrootd I thought it was a good idea
to recompile libxrdhttpvoms and refurbish the setup of littlexrdhttp, as t was old-ish (Sept)

  I advise you to refresh as well, so we can exclude any weird compatibility problem among versions.
  If you are using the lcgdm-cbuild repository (where you likely took the VOMS extractor from)
then you have everything latest and greatest if you update.

  Please make sure that you install "xrootd" stuff and not "xrootd4", and do a 'yum clean all' before...

  Said this, it worked straight here, this is the log that I get when connecting with a VOMS proxy:

---------------
141127 16:41:51 8449 XrdInet: Accepted connection from [log in to unmask]
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp: received dlen: 16
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp: received dump: 22 03 01 01 18 01 00 01 14 03 03 84 119 70 64 00
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp: This does not look like http at pos 0
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp: This may look like https
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp: Protocol matched. https: 1
141127 16:41:51 8449 XrdProtocol: matched protocol XrdHttp
141127 16:41:51 8449 ?:27@lxplus0085 XrdPoll: FD 27 attached to poller 1; num=1
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp:  Process. lp:0x7f0654001278 reqstate: 0
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp:  Setting host: [::ffff:188.184.71.156]
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp:  Entering SSL_accept...
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp:  SSL_accept returned :1
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp:  Extracting auth info.
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp:  SSL_get_peer_certificate returned :0x7f0650000f70
141127 16:41:51 8449 ?:27@lxplus0085 sysXrdHttp:  Setting link name: /DC=ch/DC=cern/OU=Organic 
Units/OU=Users/CN=furano/CN=644746/CN=Fabrizio Furano/CN=proxy
141127 16:41:51 8449 /DC=ch/DC=cern/OU=Organ@lxplus0085 sysXrdHttp:  SSL_get_verify_result returned :0
---------------

  and this is how I am recognized by littlexrdhttp, you should get a similar thing:

<span id="requestby">Request by /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=furano/CN=644746/CN=Fabrizio Furano/CN=proxy ( VO: 
dteam DN: /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=furano/CN=644746/CN=Fabrizio Furano/CN=proxy Role: 
/dteam/Role=NULL/Capability=NULL )

---------------


  Fabrizio

On 11/27/2014 03:07 PM, Fabrizio Furano wrote:
> Hi,
>
> On 11/27/2014 12:53 PM, [log in to unmask] wrote:
>> Hi,
>>
>>> The security extractor enables clients with VOMS proxy certificates to connect. For normal client user certificates you
>>> don't need it.
>>
>> Ah, right, I think I get it. So if I'm using an ordinary user cert (in a browser for instance) the XrdHTTP server does the
>> authentication without the sec extractor.
>
>
>   Yes, correct
>
>
>> Can it do any authorisation?
>  >
>
>
>   The authorization is performed by any XrdAcc your server is configured with.
>
>   What XrdHTTP does is just to fill an internal structure with the client credentials
> and then forward it to the rest of the framework.
>
>
>> From the email (https://listserv.slac.stanford.edu/cgi-bin/wa?A2=ind1410&L=XROOTD-L&D=0&P=632) last month it looks like you
>> were waiting for the grid mapfile feature to be added.
>
>
>   I was waiting for it to be made available in the xrootd framework, as it was a sort of 'private' thing
> of the xrootd protocol implementation.
>   That was done, and I have provided XrdHTTP with the capability of using it.
>
>   XrdHTTP honors the mapfile that you provide to it.
>
>
>>
>>> Your config file looks fine to me, and the only error that I see in the log is
>>> 141126 10:38:47 8292 ofs_opendir: unnamed.1:[log in to unmask] Unable to open directory /dteam/; permission
>>> denied
>>> From this I am not able to tell whether the request was denied by some authorization module in ofs, libRadosOss or
>>> anything else.
>>> Could you please restart the server with the -d option and redo this little read test?
>>> Which credentials is your test client using to do the test ? User cert? VOMS proxy?
>>
>> Right, so that test was me pointing my browser with my user cert loaded at the XrdHTTP server and hoping some VOMS magic would
>> happen.
>
>
>   That VOMS magic may happen only if you have a proper mapfile recognizing your DN.
>
>
>> I now realise that is not how it works (I think). I got davix-get working with my voms proxy cert (I confirmed it on your
>> littlexrdhttp server),
>
>
>   Were you able to spot your VOMS roles in the HTML strings it returns?
>
>
>> and then tried it on mine (with the -d option and the security extractor loaded). As far as I could see the server showed no
>> signs or recognising my proxy cert:
>>
>> <span id="requestby">Request by unnamed.9:44@gdss541 ( [::ffff:130.246.179.6]:59926 )</span></p>
>> <p>Powered by XrdHTTP v20140918-cf01cb4 (CERN IT-SDC)</p>
>>
>> The command I used was:
>>
>> davix-get -k -E /tmp/x509up_u33141 https://gdss541.gridpp.rl.ac.uk:1094/
>
>   My impression is that it's behaving as if no XrdHTTPVOMS was loaded, and it's not allowing me to connect with my proxy.
>   You should see some related log lines in the startup phase. Could you please post the log of the startup phase ?
>
>
>
>>
>> I've attached the log. The " 140350031914752:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:703:Expecting:
>> CERTIFICATE" bit looks fishy to me, but I don't know what the logs from a successful davix-get look so I could be looking in
>> the wrong place entirely.
>
>
>   You're looking at the right place, and indeed they are fishy. This is the behavior without VOMS extractor when a client
> provides a proxy.
>
>
>>
>> Thanks for the help, are there any other tests I can run that might make things clearer?
>
>   Yes, please post the startup phase of the server (with the -d switch). In the meantime I am refurbishing littlexrdhttp,
> because I had a version from September, and many things have changed since that moment.
>
> Fabrizio

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1