Modify the OpenLDAP schema These steps detail a schema modification to OpenLDAP 2.3 provided by one of our customers that helped them integrate with their instance. Before you beginRole required: admin About this task Caution: The customization described here was developed for use in specific instances, and is not supported by ServiceNow. This method is provided as-is and should be tested thoroughly before implementation. Post all questions and comments regarding this customization to our community forum. To modify the OpenLDAP schema for integration with the instance: Procedure Create a custom attribute. attribute ( 220.127.116.11.4.1.3403000.2.1.8 NAME 'servnowid' ORDERING caseIgnoreOrderingMatch EQUALITY caseIgnoreMatch SYNTAX '18.104.22.168.4.1.1422.214.171.124.15' ) Include the attribute in the selected objectclass OID. objectclass ( 126.96.36.199.4.1.3403000.2.2.1 NAME 'BcfUserIdentifiers' SUP top AUXILIARY MAY ( uniqid $ unixid $ servnowid ) ) In OpenLDAP 2.3, you can dynamically change the server configurations, but you can only extend the schema. You cannot modify or delete the existing schema. Instead of creating another objectclass for this attribute in the dynamic configuration, use the static configuration file, slapd.conf. In slapd.conf, include indexing for the new attribute in the bdb section of your main database backend. database bdb (configs here) .... index servnowid pres (other indexes here) ..... As root, run slapindex to index this attribute to make it available in search filters. Make sure that the OpenLDAP daemon is not running or is in read-only mode before starting slapindex.