Project

General

Profile

Actions

Task #2693

closed

Initialization of mock target system for product integration tests

Added by Ondrej Husník about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ondrej Husník
Category:
Test
Target version:
Start date:
02/26/2021
Due date:
% Done:

100%

Estimated time:
12.00 h
Owner:

Description

The goal is to prepare and configure target systems which will be conform with needs of the test scenarios specified in #2636 and will be runnable from JUnit.


Related issues

Related to IdStory Identity Manager - Task #2675: Automation of product integration tests - prerequisitiesClosedOndrej Husník02/08/2021

Actions
Related to IdStory Identity Manager - Task #2792: Develop evaluation and source data modification methods for IdM Integration testClosedOndrej Husník05/04/2021

Actions
Actions #1

Updated by Ondrej Husník about 3 years ago

  • Related to Task #2675: Automation of product integration tests - prerequisities added
Actions #2

Updated by Vít Švanda about 3 years ago

  • Target version changed from 11.0.0 to 11.1.0
Actions #3

Updated by Ondrej Husník almost 3 years ago

  • Status changed from New to In Progress
Actions #4

Updated by Ondrej Husník almost 3 years ago

  • % Done changed from 0 to 90

Implementation of the Ldap server by 'com.unboundid.ldap' is used and run as target test system. Connection to it from outside (e.g. using Directory Studio) is also possible.
Unfortunately provisioning to the target system keeps failing with the exception:

org.identityconnectors.framework.common.exceptions.ConnectorException: javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Unable to add entry 'uid=ldapUser,ou=people,dc=bcv,dc=cz' because it violates the provided schema:  The entry contains object class organizationalPerson
 which is not defined in the schema.  The entry contains object class person
 which is not defined in the schema.  The entry contains object class top
 which is not defined in the schema.]; remaining name 'uid=ldapUser,ou=people,dc=bcv,dc=cz'
    at net.tirasa.connid.bundles.ldap.schema.LdapSchemaMapping.create(LdapSchemaMapping.java:329)
    at net.tirasa.connid.bundles.ldap.modify.LdapCreate$1.access(LdapCreate.java:134)

I wasn't successful in finding the cause of it therefore I decide to use the system in read-only mode with provisioning queue at this moment and evaluate attribute changes from queue. Reasons why changes are not written into destination system can be investigated later. Chosen solution is sufficient for our test cases.

Actions #5

Updated by Ondrej Husník almost 3 years ago

  • Related to Task #2792: Develop evaluation and source data modification methods for IdM Integration test added
Actions #6

Updated by Tomáš Doischer almost 3 years ago

My guess is you need to set the schema to LDAP, see here for some tips: https://www.javatips.net/api/com.unboundid.ldap.sdk.schema.schema

Actions #7

Updated by Ondrej Husník almost 3 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100

Implementation of the ldap target system has been done to the extent described above. A hint to overcome the failing schema: the schema setting could be exported from a tool such as Directory studio and used as the configuration of the ldap server used in tests.

Actions

Also available in: Atom PDF