Hi,
well, if you think that xrdhttpvoms should populate one more
field (group) we can do it and publish pretty quickly to epel.
How should it be populated ? Shall the group names start with
a slash ?
Cheers
Fabrizio
On 08/20/2017 09:50 PM, xrootd-dev wrote:
> It would appear that the voms plugin used by xrootd authentication
> populates te group field while the HTTP one does not (or populates it in a
> different way). This I deduce because you said:
>
> g /atlas /beegfs/grid/atlas/atlaslocalgroupdisk
> ```
> Changing that to:
> ```
> u * /beegfs/grid/atlas/atlaslocalgroupdisk
> ```
> let's things work fine, but of course I do not want that.
>
> The authentication rule works perfectly fine via the xrootd protocol.
>
> So, the question is why is this he case?
>
> Yes, to switch to using o and r as well as composite rules (i.e. ones that
> "and" o and r, among others), will be available in 4.7.0.
>
> Andy
>
> On Sun, 20 Aug 2017, olifre wrote:
>
>>> LCMAPS provides the username mapping and extraction, then maps VOMS groups to the Xrootd group names.
>>
>> This sounds like a nice alternative! I looked at `xrdhttpvoms` since it seemed to be more lightweight.
>>
>> I'll have a look after my holidays are over - unless xrootd 4.7 comes out in the meanwhile and let's `xrdhttpvoms` magically
> work when using `o` ;-).
>>
>> --
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly or view it on GitHub:
>> https://github.com/xrootd/xrootd/issues/566#issuecomment-323602010
>>
>> ########################################################################
>> Use REPLY-ALL to reply to list
>>
>> To unsubscribe from the XROOTD-DEV list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <https://github.com/xrootd/xrootd/issues/566#issuecomment-323607626>, or mute
> the thread <https://github.com/notifications/unsubscribe-auth/AFIaTyvV234WQczGu3jLC_IrkOHA33bfks5saI4ggaJpZM4O7mEG>.
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ffurano in #566: Hi,\n\n well, if you think that xrdhttpvoms should populate one more\nfield (group) we can do it and publish pretty quickly to epel.\n\n How should it be populated ? Shall the group names start with\na slash ?\n\nCheers\nFabrizio\n\n\n\nOn 08/20/2017 09:50 PM, xrootd-dev wrote:\n\u003e It would appear that the voms plugin used by xrootd authentication\n\u003e populates te group field while the HTTP one does not (or populates it in a\n\u003e different way). This I deduce because you said:\n\u003e \n\u003e g /atlas /beegfs/grid/atlas/atlaslocalgroupdisk\n\u003e ```\n\u003e Changing that to:\n\u003e ```\n\u003e u * /beegfs/grid/atlas/atlaslocalgroupdisk\n\u003e ```\n\u003e let's things work fine, but of course I do not want that.\n\u003e \n\u003e The authentication rule works perfectly fine via the xrootd protocol.\n\u003e \n\u003e So, the question is why is this he case?\n\u003e \n\u003e Yes, to switch to using o and r as well as composite rules (i.e. ones that\n\u003e \"and\" o and r, among others), will be available in 4.7.0.\n\u003e \n\u003e Andy\n\u003e \n\u003e On Sun, 20 Aug 2017, olifre wrote:\n\u003e \n\u003e\u003e\u003e LCMAPS provides the username mapping and extraction, then maps VOMS groups to the Xrootd group names.\n\u003e\u003e\n\u003e\u003e This sounds like a nice alternative! I looked at `xrdhttpvoms` since it seemed to be more lightweight.\n\u003e\u003e\n\u003e\u003e I'll have a look after my holidays are over - unless xrootd 4.7 comes out in the meanwhile and let's `xrdhttpvoms` magically\n\u003e work when using `o` ;-).\n\u003e\u003e\n\u003e\u003e --\n\u003e\u003e You are receiving this because you are subscribed to this thread.\n\u003e\u003e Reply to this email directly or view it on GitHub:\n\u003e\u003e https://github.com/xrootd/xrootd/issues/566#issuecomment-323602010\n\u003e\u003e\n\u003e\u003e ########################################################################\n\u003e\u003e Use REPLY-ALL to reply to list\n\u003e\u003e\n\u003e\u003e To unsubscribe from the XROOTD-DEV list, click the following link:\n\u003e\u003e https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV\u0026A=1\n\u003e \n\u003e —\n\u003e You are receiving this because you were mentioned.\n\u003e Reply to this email directly, view it on GitHub \u003chttps://github.com/xrootd/xrootd/issues/566#issuecomment-323607626\u003e, or mute\n\u003e the thread \u003chttps://github.com/notifications/unsubscribe-auth/AFIaTyvV234WQczGu3jLC_IrkOHA33bfks5saI4ggaJpZM4O7mEG\u003e.\n\u003e \n"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/566#issuecomment-323673009"}}}
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
