<commit_before><?xml version="1.0" encoding="UTF-8"?>
<!--
  ~ Copyright (c) 2011 Evolveum
  ~
  ~ The contents of this file are subject to the terms
  ~ of the Common Development and Distribution License
  ~ (the License). You may not use this file except in
  ~ compliance with the License.
  ~
  ~ You can obtain a copy of the License at
  ~ http://www.opensource.org/licenses/cddl1 or
  ~ CDDLv1.0.txt file in the source code distribution.
  ~ See the License for the specific language governing
  ~ permission and limitations under the License.
  ~
  ~ If applicable, add the following below the CDDL Header,
  ~ with the fields enclosed by brackets [] replaced by
  ~ your own identifying information:
  ~
  ~ Portions Copyrighted 2011 [name of copyright owner]
  -->


<!--

This file is an example of Resource definition. It defines an LDAP resource
using an Identity Connector Framework LDAP connector. It contains configuration
for use with stock OpenDJ and OpenDS servers.

This resource definition contains also definition to enable synchronization and
especially an expression that is using a lookup of value from an configuration
object.

-->

<objects xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema"
         xmlns:icfs="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-1.xsd"
         xmlns:my="http://myself.me/schemas/whatever"
         xsi:schemaLocation="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd ../../infra/schema/src/main/resources/xml/ns/public/common/common-1.xsd">


    <resource oid="ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2">

        <!-- Resource name. It will be displayed in GUI.  -->
        <name>Localhost OpenDJ</name>

        <description>
            LDAP resource using an Identity Connector Framework LDAP connector. It contains configuration
            for use with stock OpenDJ and OpenDS servers.

            This resource definition contains also definition to enable synchronization and
            especially an expression that is using a lookup of value from an configuration
            object.
        </description>

        <connectorRef type="ConnectorType">
            <description>
                Reference to the ICF LDAP connector. This is dynamic reference, it will be translated to
                OID during import.
            </description>
            <and>
                <type uri="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd#ConnectorType"/>
                <equal>
                    <value>
                        <connectorType>org.identityconnectors.ldap.LdapConnector</connectorType>
                    </value>
                </equal>
            </and>
        </connectorRef>

        <!-- Resource namespace. This is important. All resource schema elements should be in this namespace. -->
        <namespace>http://midpoint.evolveum.com/xml/ns/public/resource/instance/ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2
        </namespace>

        <!-- Configuration section contains configuration of the connector,
             such as hostnames and passwords -->
        <configuration
                xmlns:icfcldap="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/bundle/org.forgerock.openicf.connectors.ldap.ldap/org.identityconnectors.ldap.LdapConnector"
                xmlns:icfc="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/connector-schema-1.xsd">

            <!-- Configuration specific for the LDAP connector -->
            <icfcldap:configurationProperties>
                <icfcldap:port>1389</icfcldap:port>
                <icfcldap:host>localhost</icfcldap:host>
                <icfcldap:baseContexts>dc=example,dc=com</icfcldap:baseContexts>
                <icfcldap:principal>uid=idm,ou=Administrators,dc=example,dc=com</icfcldap:principal>
                <icfcldap:credentials>
                    <clearValue>secret</clearValue>
                </icfcldap:credentials>
                <icfcldap:modifiersNamesToFilterOut>uid=idm,ou=Administrators,dc=example,dc=com
                </icfcldap:modifiersNamesToFilterOut>
                <icfcldap:vlvSortAttribute>uid</icfcldap:vlvSortAttribute>
                <icfcldap:usePagedResultControl>true</icfcldap:usePagedResultControl>
                <icfcldap:accountOperationalAttributes>ds-pwp-account-disabled</icfcldap:accountOperationalAttributes>
            </icfcldap:configurationProperties>

            <!-- Generic ICF configuration -->

            <icfc:connectorPoolConfiguration>
                <icfc:minEvictableIdleTimeMillis>120000</icfc:minEvictableIdleTimeMillis>
                <icfc:minIdle>1</icfc:minIdle>
                <icfc:maxIdle>10</icfc:maxIdle>
                <icfc:maxObjects>10</icfc:maxObjects>
                <icfc:maxWait>150000</icfc:maxWait>
            </icfc:connectorPoolConfiguration>

            <icfc:producerBufferSize>100</icfc:producerBufferSize>

            <icfc:timeouts>
                <icfc:create>-1</icfc:create>
                <icfc:get>-1</icfc:get>
                <icfc:update>-1</icfc:update>
                <icfc:delete>-1</icfc:delete>
                <icfc:test>-1</icfc:test>
                <icfc:scriptOnConnector>-1</icfc:scriptOnConnector>
                <icfc:scriptOnResource>-1</icfc:scriptOnResource>
                <icfc:authentication>-1</icfc:authentication>
                <icfc:search>-1</icfc:search>
                <icfc:validate>-1</icfc:validate>
                <icfc:sync>-1</icfc:sync>
                <icfc:schema>-1</icfc:schema>
            </icfc:timeouts>

        </configuration>

        <!-- Resource schema definition.
             It defines all the object classes that are available to midPoint
             (accounts, groups, ...).

             This should be direct mapping of ICF schema (and therefore also
             LDAP schema). This is not supposed to be customized during deployment
             unless the underlying LDAP schema is non-standard (also see below).
             
             This schema is normally generated from the resource on the first use.
             Therefore it is not needed to provide the schema here during import. 
             This example has a schema definition to show how it looks like and also to
             demonstrate that it can be provided during import if needed. -->
        <schema>

            <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                        xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd"
                        xmlns:icfs="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-1.xsd"
                        xmlns:r="http://midpoint.evolveum.com/xml/ns/public/resource/resource-schema-1.xsd"
                        elementFormDefault="qualified"
                        targetNamespace="http://midpoint.evolveum.com/xml/ns/public/resource/instance/ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2">
                <xsd:import namespace="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd"/>
                <xsd:import
                        namespace="http://midpoint.evolveum.com/xml/ns/public/resource/instance/ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2"/>
                <xsd:import
                        namespace="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-1.xsd"/>
                <xsd:complexType name="AccountObjectClass"><commit_msg>fixed opendj resource definition. idea is removing "unused" namespaces<commit_after><?xml version="1.0" encoding="UTF-8"?>
<!--
  ~ Copyright (c) 2011 Evolveum
  ~
  ~ The contents of this file are subject to the terms
  ~ of the Common Development and Distribution License
  ~ (the License). You may not use this file except in
  ~ compliance with the License.
  ~
  ~ You can obtain a copy of the License at
  ~ http://www.opensource.org/licenses/cddl1 or
  ~ CDDLv1.0.txt file in the source code distribution.
  ~ See the License for the specific language governing
  ~ permission and limitations under the License.
  ~
  ~ If applicable, add the following below the CDDL Header,
  ~ with the fields enclosed by brackets [] replaced by
  ~ your own identifying information:
  ~
  ~ Portions Copyrighted 2011 [name of copyright owner]
  -->


<!--

This file is an example of Resource definition. It defines an LDAP resource
using an Identity Connector Framework LDAP connector. It contains configuration
for use with stock OpenDJ and OpenDS servers.

This resource definition contains also definition to enable synchronization and
especially an expression that is using a lookup of value from an configuration
object.

-->

<objects xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema"
         xmlns:ri="http://midpoint.evolveum.com/xml/ns/public/resource/instance/ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2"
         xmlns:icfs="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-1.xsd"
         xmlns:my="http://myself.me/schemas/whatever"
         xsi:schemaLocation="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd ../../infra/schema/src/main/resources/xml/ns/public/common/common-1.xsd">


    <resource oid="ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2">

        <!-- Resource name. It will be displayed in GUI.  -->
        <name>Localhost OpenDJ</name>

        <description>
            LDAP resource using an Identity Connector Framework LDAP connector. It contains configuration
            for use with stock OpenDJ and OpenDS servers.

            This resource definition contains also definition to enable synchronization and
            especially an expression that is using a lookup of value from an configuration
            object.
        </description>

        <connectorRef type="ConnectorType">
            <description>
                Reference to the ICF LDAP connector. This is dynamic reference, it will be translated to
                OID during import.
            </description>
            <and>
                <type uri="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd#ConnectorType"/>
                <equal>
                    <value>
                        <connectorType>org.identityconnectors.ldap.LdapConnector</connectorType>
                    </value>
                </equal>
            </and>
        </connectorRef>

        <!-- Resource namespace. This is important. All resource schema elements should be in this namespace. -->
        <namespace>http://midpoint.evolveum.com/xml/ns/public/resource/instance/ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2</namespace>

        <!-- Configuration section contains configuration of the connector,
             such as hostnames and passwords -->
        <configuration
                xmlns:icfcldap="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/bundle/org.forgerock.openicf.connectors.ldap.ldap/org.identityconnectors.ldap.LdapConnector"
                xmlns:icfc="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/connector-schema-1.xsd">

            <!-- Configuration specific for the LDAP connector -->
            <icfcldap:configurationProperties>
                <icfcldap:port>1389</icfcldap:port>
                <icfcldap:host>localhost</icfcldap:host>
                <icfcldap:baseContexts>dc=example,dc=com</icfcldap:baseContexts>
                <icfcldap:principal>uid=idm,ou=Administrators,dc=example,dc=com</icfcldap:principal>
                <icfcldap:credentials>
                    <clearValue>secret</clearValue>
                </icfcldap:credentials>
                <icfcldap:modifiersNamesToFilterOut>uid=idm,ou=Administrators,dc=example,dc=com
                </icfcldap:modifiersNamesToFilterOut>
                <icfcldap:vlvSortAttribute>uid</icfcldap:vlvSortAttribute>
                <icfcldap:usePagedResultControl>true</icfcldap:usePagedResultControl>
                <icfcldap:accountOperationalAttributes>ds-pwp-account-disabled</icfcldap:accountOperationalAttributes>
            </icfcldap:configurationProperties>

            <!-- Generic ICF configuration -->

            <icfc:connectorPoolConfiguration>
                <icfc:minEvictableIdleTimeMillis>120000</icfc:minEvictableIdleTimeMillis>
                <icfc:minIdle>1</icfc:minIdle>
                <icfc:maxIdle>10</icfc:maxIdle>
                <icfc:maxObjects>10</icfc:maxObjects>
                <icfc:maxWait>150000</icfc:maxWait>
            </icfc:connectorPoolConfiguration>

            <icfc:producerBufferSize>100</icfc:producerBufferSize>

            <icfc:timeouts>
                <icfc:create>-1</icfc:create>
                <icfc:get>-1</icfc:get>
                <icfc:update>-1</icfc:update>
                <icfc:delete>-1</icfc:delete>
                <icfc:test>-1</icfc:test>
                <icfc:scriptOnConnector>-1</icfc:scriptOnConnector>
                <icfc:scriptOnResource>-1</icfc:scriptOnResource>
                <icfc:authentication>-1</icfc:authentication>
                <icfc:search>-1</icfc:search>
                <icfc:validate>-1</icfc:validate>
                <icfc:sync>-1</icfc:sync>
                <icfc:schema>-1</icfc:schema>
            </icfc:timeouts>

        </configuration>

        <!-- Resource schema definition.
             It defines all the object classes that are available to midPoint
             (accounts, groups, ...).

             This should be direct mapping of ICF schema (and therefore also
             LDAP schema). This is not supposed to be customized during deployment
             unless the underlying LDAP schema is non-standard (also see below).
             
             This schema is normally generated from the resource on the first use.
             Therefore it is not needed to provide the schema here during import. 
             This example has a schema definition to show how it looks like and also to
             demonstrate that it can be provided during import if needed. -->
        <schema>

            <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                        xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd"
                        xmlns:tns="http://midpoint.evolveum.com/xml/ns/public/resource/instance/ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2"
                        xmlns:icfs="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-1.xsd"
                        xmlns:r="http://midpoint.evolveum.com/xml/ns/public/resource/resource-schema-1.xsd"
                        elementFormDefault="qualified"
                        targetNamespace="http://midpoint.evolveum.com/xml/ns/public/resource/instance/ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2">
                <xsd:import namespace="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd"/>
                <xsd:import
                        namespace="http://midpoint.evolveum.com/xml/ns/public/resource/instance/ef2bc95b-76e0-48e2-86d6-3d4f02d3e1a2"/>
                <xsd:import
                        namespace="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-1.xsd"/>
                <xsd:complexType name="AccountObjectClass">
{'fraction_non_alphanumeric': 0.1066913548716639, 'fraction_numerical': 0.02260247733367386, 'mean_word_length': 2.3100169061707523, 'pattern_counts': {'":': 0, '<': 203, '<?xml version=': 2, '>': 203, 'https://': 0, 'lorem ipsum': 0, 'www.': 8, 'xml': 62}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '825510', 'n_tokens_mistral': 4824, 'n_tokens_neox': 4471, 'n_words': 892}