PEP Java Client Library Design


  1. Absolute minimal set of dependencies:
    • hessian
    • object model
    • httpclient (and deps)
    • voms-java-api (and deps)
  2. A very simple PEP client API (based on the KISS principle).
  3. The PEP-J should be easily configurable, using only API calls (no need for configuration file).
  4. It should hide the transport logic from the calling application, by using httpclient inside the client.
  5. It should provide easy HTTPS/TLS client authN configuration (using VOMS API?).
  6. It should be easy to configure the HTTP keep-alive. CREAM developers want to create one client and reuse it to spare the HTTPS/client authN overhead.
  7. It should be clear how multithreading is handled.
  8. It should be easily extendable with the notion of profiles.
  9. Interfaces should be used as much as possible, where applicable.
  10. It should provide simple PIP and OH handling functionalities.
  11. It should provides at least a simple example.
  12. It should be built/released for glite 3.2 first, but also for glite 3.1 (as an internal patch)
  13. It should be easy to build request object. Some sort of RequestBuilder is required.
    • to populate the subject starting from a certificate (which cert format?)
    • provide convenience methods to set resource and action ids
  14. Nonblocking calls is not a priority.
  15. We don't need a CLI at all. This functionality is already available in pepcli.


List of dependencies available in ETICS what can be used:

  • bouncycastle.DEFAULT: bouncycastle v. 1.42
  • jakarta-commons-cli.DEFAULT: jakarta-commons-cli v. 1.0
  • jakarta-commons-codec.DEFAULT: jakarta-commons-codec v. 1.3
  • jakarta-commons-collections.DEFAULT: jakarta-commons-collections v. 3.2
  • jakarta-commons-configuration.DEFAULT: jakarta-commons-configuration v.1.4
  • jakarta-commons-httpclient.DEFAULT: jakarta-commons-httpclient v. 3.0.1
  • jakarta-commons-lang.DEFAULT: jakarta-commons-lang v. 2.3
  • jakarta-commons-logging.DEFAULT: jakarta-commons-logging v. 1.1
  • junit.DEFAULT: junit v. 3.8.1
  • log4j.DEFAULT: log4j v. 1.2.13-1
  • glite-security-trustmanager_R_2_5_5_1_GL32
  • glite-security-util-java_R_2_5_5_1_GL32
  • glite-security-voms-api-java_R_1_8_12_1_GL32

VOMS Java API version is still 1.8.12, I really don't know why the version 1.9.14 is not yet available?!?

The Hessian library is still missing, but I will request its integration in ETICS. But which version 3.2.1 or 4.0.3 to request?

API Prototype

// create PEP-J configuration 
PEPClientConfiguration config= new PEPClientConfiguration();
// other config params

// create PEP-J client
PEPClient client= new PEPClient(config);

// create XACML request

// authorize 
Response resp= client.authorize(request);

// parse XACML response

-- ValeryTschopp - 02-Mar-2010

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2016-07-05 - MaartenLitmaath
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback