LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  November 2014

XROOTD-L November 2014

Subject:

Re: Another HTTPS authorisation question

From:

Fabrizio Furano <[log in to unmask]>

Reply-To:

Support use of xrootd by HEP experiments <[log in to unmask]>

Date:

Thu, 27 Nov 2014 17:27:14 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (143 lines)

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

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use