You are here: Resources > FIDIS Deliverables > HighTechID > D3.11: Report on the Maintenance of the IMS Database > 
Annex 2: Feed Back in Detail  Title:
HIPATH SICURITY DIRX FEEDBACK
 KeePass Password Safe feedback

 

HiPath SIcurity DirX Feedback

 

HiPath SIcurity Identity Management System 

 

Verification of data – Instructions  

 

Please indicate with a Yes/No in the respective field of the following table the correctness / completeness of the data held in our database. If you find that the data is not correct and/or complete, please proceed with making the appropriate corrections / additions by appropriately filling in the next field (“Correction / Completion”). 

 

For a description / definition of each field, you can refer at Table B. 

 

TABLE A – Verification of Data 

Data held in database 

Yes/No 

Correction / Completion 

  1.  

Evaluation of IMS 

    1.  

Evaluator:  

Christian Krause 

 

 

    1.  

Organisation:  

ICCP 

 

 

    1.  

Date of evaluation:  

20-Jan-2006 

 

 

  1.  

Identification of IMS 

    1.  

Sources of information:  

http://www.siemens.de/directory

Yes 

http://www.siemens.com/hipath-sicurity 

    1.  

Version:  

7.0 

Yes 

 

    1.  

Manufacturer:  

Siemens 

No 

Siemens AG 

    1.  

Nature:  

international 

Yes 

 

    1.  

Country:  

Germany 

Yes 

 

    1.  

Regions:  

Global 

Yes 

 

    1.  

Language:  

ENGLISH,GERMAN 

Yes 

 

    1.  

State:  

Available 

Yes 

 

    1.  

Open/Closed:  

Closed IMS: the scope of the identities is restricted to the IMS context. 

Yes 

 

  1.  

Platform & Environment 

    1.  

Requirements:  

Intel Server Platform or SPARC, 1GB RAM, 700+MB HD, Windows, Solaris, Red Hat, SuSE 

Yes 

 

    1.  

Number of users:  

n.a. 

Yes 

 

    1.  

Standards:  

LDAPv3, DSMLv2, DAP, DSP, DISP, IDM, X.500, X.509, X521 

Yes 

 

    1.  

Description of Server - Side components:  

DirX is a meta directory allowing interoperability between directory services. To achieve this the directory service’s data is reproduced in the meta directory. 

No 

Server components are: Identity Server, Agents and Connectors, Identity Store. The Identity Server provides a comprehensive runtime environment for event-triggered and scheduled provisioning workflows. Agents and connectors provision and synchronize accounts/groups in target systems. The Identity Store is an LDAPv3 directory server. 

    1.  

Description of methods:  

n.a. 

No 

DirX Identity provides provisioning and synchronization based on a metadirectory technology. 

    1.  

Descriptor of Client -
Side components:

n.a. 

No 

The Identity Web Center is the component that enables user self-service and delegated administration from a Web browser. 

    1.  

Seals:  

No  

Yes 

 

    1.  

Which seal:  

 

 

 

    1.  

Third party:  

no 

Yes 

 

    1.  

Which third party:  

 

 

 

    1.  

Features:  

Among other identity management-features meta directories faciltate single sign-on. 

No 

Web-based user self-service and delegated administration, password management, user management, cross-platform provisioning and metadirectory functionality. The provisioning of users and their access rights in various target systems is driven by a powerful, centralized privilege management component which deals with the business roles, permissions, user groups, and includes a flexible policy and workflow engine. In addition, comprehensive scheduling, monitoring and auditing are available. 

    1.  

Screenshot picture:  

HiPath SIcurity dirx_screen.png

 

 

    1.  

Flowchart:  

HiPath SIcurity dirx-flow.png

 

 

  1.  

Cost 

    1.  

Price:  

 

 

    1.  

Comment to the Cost:  

depends on product 

No 

Product pricing depends on the number of managed identities 

  1.  

Type & Class of IMS 

    1.  

Type of IMS:  

Type 1: IMS for account management. 

Yes 

 

    1.  

Class of IMS:  

Class 1: Pure IMS which main objective is to support or implement identity management functionality. 

Yes 

 

    1.  

Functionality:  

metadirectory, account management, single sign-on 

No 

metadirectory, account management, password management 

  1.  

Suggestions:  

Meta directories in general connect different directory services. Data from one directory service is available for another. To achieve this, data is reproduced in a central database. 

 

 

 

 

 

Annex 2: Feed Back in Detail  fidis-wp3-del3.11.report_ims_database_02.sxw  KeePass Password Safe feedback
10 / 15