And I need to reconfigure all my other machines to read from Argus and
I am so not touching the SE[*], I'm not insane, just slightly mad.
Otherwise, what Andrew says.
[*] Honestly even if I wanted to I have no idea how to make it work.
The way the user mapping is done on the SE is completely different to
the rest of the cluster and with Argus insisting on the user having
the same id all over the site this will just not work without breaking
stuff.
On 17 December 2013 11:44, Stephen Burke <[log in to unmask]> wrote:
> Testbed Support for GridPP member institutes [mailto:TB-
>> [log in to unmask]] On Behalf Of Daniela Bauer said:
>> The CRL revocation is a cron job that runs in the background, leaves a
>> tiny footprint and does not require any extra hardware and/or
>> re-configuring of services. It's an rpm I can pull out of a repo and
>> install anywhere I like.
>> I would all for it to have central banning done in a similar way :-)
>
> Given that you would be installing Argus anyway for central management of authz, that's pretty much what is happening - you configure your Argus to read the ban list and that's it.
>
> Stephen
>
> --
> Scanned by iCritical.
--
Sent from the pit of despair
-----------------------------------------------------------
[log in to unmask]
HEP Group/Physics Dep
Imperial College
London, SW7 2BW
Tel: +44-(0)20-75947810
http://www.hep.ph.ic.ac.uk/~dbauer/
|