Ticket #381 (closed task: fixed)

Opened 15 years ago

Last modified 14 years ago

[S] Custom Credential Repository interface for BODC

Reported by: pjkersha Owned by: pjkersha
Priority: desirable Milestone: PROD Step2
Component: security Version:
Keywords: security, Credential Repository Cc:


The Session Manager uses a Credential Repository to store Attribute Certificates acquired by users during user sessions. It acts as a back-up to a user's session wallet content.

The default Credential Repository uses a MySQL database. BODC would like to use Oracle instead. Write an alternative Credential Repository plugin to interface with Oracle.

Change History

comment:1 Changed 14 years ago by pjkersha

  • Status changed from new to assigned
  • Siva has written test code to connect to the BODC Oracle server using the cx_Oracle Python bindings
  • The Session Manager is now changed so that it can be configured with a plugin to the Credential Repository API so that the BODC can use their a custom interface to Oracle.

comment:2 Changed 14 years ago by lawrence

  • Milestone changed from BETA to BETA+Security

comment:3 Changed 14 years ago by pjkersha

  • Status changed from assigned to closed
  • Resolution set to fixed

The Credential Repository is not an essential part of the Session Manager. Its main use is enable user's CredentialWallets to be cached on disk so that in the event of a restart of the service their credentials can be restored.

The Session Manager now has an API to the Credential Repository. Data Providers can provide a plugin interface to a database or other form of sotre if required but it is not essential. The default plugin assumes that credential do not need to be cached in this way.

Note: See TracTickets for help on using tickets.