1 / 7

Security Command Line Tools

Security Command Line Tools. C.Witzig, SWITCH christoph.witzig@switch.ch. A bit of history. Goal: A set of useful command line tools for site admins Not user authZ recommendation #3, OSG-EGEE coordination meeting Document at https://edms.cern.ch/document/931846 General remarks:

lelia
Télécharger la présentation

Security Command Line Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Security Command Line Tools C.Witzig, SWITCH christoph.witzig@switch.ch

  2. A bit of history • Goal: A set of useful command line tools for site admins • Not user • authZ recommendation #3, OSG-EGEE coordination meeting • Document at https://edms.cern.ch/document/931846 • General remarks: • Should be simple • Clearly differentiate between commands that • Make changes (with option --noaction) • Do only return information • API specs may have to be modified during implementation security command line tools

  3. Cmds • task_removal: Given a credential find currently running jobs (and optionally remove them) • check_connection • authz_check: given a credential, return authZ answer (permit/deny/undetermined) • cred_mapping: mapping of a credential to UID/GID(s) • ban_user: banning a user/DN/FQAN security command line tools

  4. Job lookup-by-subject in BLAH Francesco Prelz (francesco.prelz@mi.infn.it) September 15th, 2009 security command line tools

  5. Summary As requested by Christoph W., a tool was added to scan and list all jobs stored in the BLAH job registry that: Were submitted with credentials belonging to a specified subject Are in a given state according to the BLAH job registry This tool (blah_job_registry_scan_by_subject) was included in BLAH stable branch 1.14 (versions 1.14.x). Here’s the usage string: Usage: blah_job_registry_scan_by_subject (<-s (proxy subject)>|<-h (proxy subject hash>) [-j job_status[\|job_status]] "Optional arg1 format" arg1 "Optional arg2 format" arg2, etc. Available job status for -j option: - unexpanded (0) - idle (1) - running (2) removed (3) - completed (4) - held (5) The tool can be used to generate and run administrative actions that need to run on all jobs that belong to a given subject. Job lookup-by-subject in BLAH 5

  6. Role of the BLAH registry Jobstatus Jobsubmission, removal A MD5 hash of the submitter subject was added to this persistent job status cache Job lookup-by-subject in BLAH 6

  7. Usage examples Here’s a few usage examples for blah_job_registry_scan_by_subject Generate a script to qdel all running jobs: $ blah_job_registry_scan_by_subject -s '/C=IT/O=INFN/OU=Personal Certificate/L=Milano/CN=Francesco Prelz' –j run "qdel %s\n" BatchJobId qdel 36490.atlfarm006.mi.infn.it qdel 36491.atlfarm006.mi.infn.it etc. etc. This can be piped directly into a shell: $ blah_job_registry_scan_by_subject -s '/C=IT/O=INFN/OU=Personal Certificate/L=Milano/CN=Francesco Prelz' –j run "qdel %s\n" BatchJobId | /bin/sh Delete jobs in a generic way via SUDO and a BLAHPD standalone instance: $ blah_job_registry_scan_by_subject -s '/C=IT/O=INFN/OU=Personal Certificate/L=Milano/CN=Francesco Prelz' –j run "BLAH_SET_SUDO_ID #%d\n" SubmitterUid "BLAH_JOB_CANCEL %d " Njobs "%s\n" BlahJobId | /opt/glite/bin/blahpd -s Job lookup-by-subject in BLAH 7

More Related