Argus: Policy Enforcement Point Daemon (PEP)

In the Argus authorization framework the Policy Enforcement Point is implemented as a client-server architecture. The PEP Daemon is the server component and there are different lightweight PEP clients available: C client, Java client, GSI PEP Callout client, ...

• Argus PEP Server Installation
  • EMI Installation
• Argus PEP Server: Configuration
  • Configuration File
  • Basic Configuration Options
  • Advanced Configuration Options
• Argus PEP Server: Operation
  • EMI
  • Starting & Stopping the Service
  • Service Information
  • Logging and Logs
• Argus PEP Server: Troubleshooting
  • PEP Daemon Returns “Stale” Results
  • Testing a policy without submitting a job
• Argus PEP Server Policy Information Points (PIP)
  • Request Validator PIP
  • OpenSSL Subject Converter PIP
  • Grid Authorization Profile PIP
  • Common XACML Authorization Profile PIP
  • Other Policy Information Points (PIP)
• Argus PEP Clients
  • pepcli
  • PEP Java Client Command Line
• Argus PEP Client Library: C API
  • Documentation
  • PEP XACML Object Model
  • Basic Example
  • Complex Example
  • Multi-threaded Programming
  • Processing Authorization Decision
• Argus PEP Client: Java Programming Interface
  • Javadoc
  • PEP XACML Object Model
  • Basic Example
  • Processing Authorization Decision
  • GUI
• Argus GSI PEP Callout
  • Module Description
  • Configuration
  • Troubleshooting
• Argus PEP Server Obligation Handlers
  • Grid Map POSIX Account Mapping Obligation Handler