Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

Testing the Code

Now let's test the code and play with some commands. Before testing the code, remember to enable the plug-in LOG level in the LDAP server, from the administrator's console or from the command line as follows:

CODE EXAMPLE 13 Enabling the Plug-In Log Level

<sunone slapd-sunblueprints>~$ ldapmodify -p 10389 -D "cn=Directory Manager" -w manager0
dn: cn=config
changetype: modify
replace: nsslapd-infolog-area
nsslapd-infolog-area: 65536
^D

Let's try a UNIX command. The language is defined to accept UNIX escape commands such as the following:

! pwd \;
! man cat \;

Many UNIX programs support this useful feature (for example, mail, vi).

The following example executes two commands. Notice that the ! escape symbol is expected at beginning of the line and a terminating '\;' sequence is required. Refer to the triggers.l file and the LEXer specification file for the lexical details of the language.

CODE EXAMPLE 14 Executing Commands

triggers>> !uname -a \;
! man pwd \;
.
Calling extended operation 4.3.2.1
------------- Your input ----------------
!uname -a \;
! man pwd \;

.
-----------------------------------------

------------- Server output ----------------
Statement #0
Error code: 0
Error msg: Unix shell command successfully executed
Linux alfa 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown

Statement #1
Error code: 0
Error msg: Unix shell command successfully executed
PWD(1)                           PWD(1)



NOME
    pwd - stampa il nome della directory di lavoro corrente

SINTASSI
    pwd
    pwd {--help,--version}

DESCRIZIONE
    Questa documentazione non ? mantenuta da lungo tempo e
    potrebbe essere inaccurata o incompleta. La documentazione
    in Texinfo ? ora la fonte autorevole.

    Questa pagina di manuale documenta la versione GNU di pwd.
    pwd stampa il nome della directory corrente risolvendolo
    completamente.  Cio?, tutte le componenti del nome stam-
    pato saranno nomi di directory reali -- nessuna sar? un
    link simbolico.

    Si noti che molte shell Unix forniscono un proprio comando
    pwd interno con funzionalit? simili cosicch? il semplice,
    interattivo comando pwd di solito eseguito sar? quello
    della shell e non questo.

  OPZIONI
    --help Mostra nello standard output un messaggio d'aiuto
       ed esce con successo.

    --version
       Mostra nello standard output informazioni sulla
       versione ed esce con successo.


FSF          GNU Shell Utilities         PWD(1)

--------------------------------------------
Triggers Client
Insert your commands, a line with '.' terminates input

We executed the commands uname -a and man pwd. Both are executed on the server, where Sun Java System Directory Server and the extended operation run. You could use this feature for a minimal remote administration if you like, but our goal was just to show an advanced use of the extended operation. Consider also that this kind of feature could introduce serious security concerns, especially if the remote server runs with root account privileges.

Now let's review the log error file to determine what happened.

CODE EXAMPLE 15 Reviewing the Log File

[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_service_fn - conn=2 op=1 msgId=1 - Entering pb=0x8354d60
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_service_fn - conn=2 op=1 msgId=1 - Request with OID: 4.3.2.1 Value from client: !uname -a \;
! man pwd \;
.
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_parse_client_req - conn=2 op=1 msgId=1 - Entering with params(0x8354d60,0x8118348,0x42b796fc)
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_parse_client_req - conn=2 op=1 msgId=1 - Creating the temporary file for parsing
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_parse_client_req - conn=2 op=1 msgId=1 - Opening the temporary file for parsing
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_parse_client_req - conn=2 op=1 msgId=1 - <<!uname -a \;
! man pwd \;

.>>
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_parse_client_req - conn=2 op=1 msgId=1 - Now parsing...
[..cut...]
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_apply_statements: - conn=2 op=1 msgId=1 - trg_apply_statements(0x8354d60,0x42b796fc, 0x43d1191c)
[...cut..]
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_execute_unixcmd - conn=2 op=1 msgId=1 - Entering (index=0)
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_execute_unixcmd - conn=2 op=1 msgId=1 - Returning
[20/Oct/2003:01:47:58 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_execute_unixcmd - conn=2 op=1 msgId=1 - Entering (index=1)
[20/Oct/2003:01:47:59 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_execute_unixcmd - conn=2 op=1 msgId=1 - Returning
[20/Oct/2003:01:47:59 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_apply_statements: - conn=2 op=1 msgId=1 - Returning 0
[20/Oct/2003:01:47:59 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_service_fn - conn=2 op=1 msgId=1 - Client statements executed
[20/Oct/2003:01:47:59 +0200] - INFORMATION - (PID=3018,ThID=13325) trg_service_fn - conn=2 op=1 msgId=1 - OID sent to client:
Value sent to client:
Statement #0
Error code: 0
Error msg: Unix shell command successfully executed
Linux alfa 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown

Statement #1
Error code: 0
Error msg: Unix shell command successfully executed
PWD(1)                           PWD(1)
...

The code traces heavily, and we can see the full stack of calls:

  • trg_service_fn accepts the extended operation invocation and calls

  • trg_parse_client_req to parse the client command list, then calls

  • trg_apply_statements, which in turn, for every user command, issues a call to an execution routine, in this case

  • trg_execute_unixcmd, which issues popen library call to execute the UNIX command and returns the output to

  • trg_service_fn, which collects all the output from the execution functions in the extended operation response and

  • trg_service_fn returns the data to the client

This patterns repeats for any command issued by a user at the client application prompt; what changes is the actual trg_execute_<command> called.

Now, let's create our first trigger.

CODE EXAMPLE 16 Creating a Trigger

TRIGGERS>> create or replace trigger SunBlueprintsBigTrigger on 'ou=testadd,o=sunblueprints' before ldap_add action ignore;
.
------------- Server output ----------------
Statement #0
Error code: 0
Error msg: Trigger SunBlueprintsBigTrigger successfully added
--------------------------------------------
TRIGGERS>> list all triggers;
.
------------- Server output ----------------
Statement #0
Error code: 0
Error msg: 1 triggers found
SunBlueprintsBigTrigger
--------------------------------------------

The example defines a trigger called SunBlueprintsBigTrigger on the directory entry o=testadd, ou=SunBlueprints to be triggered before the entry is added to the directory information tree (DIT). As the action, we specify IGNORE, which means do nothing or skip the operation.

The list all triggers instruction shows you all the available triggers under ou=triggers,o=sunblueprints, which is where we store them. As a proof of this, perform the following LDAP search:

CODE EXAMPLE 17 Performing an LDAP Search

<sunone slapd-sunblueprints>~$ ldapsearch -p 10389 -D "cd=Trigger Manager" -w manager0 -b "ou=triggers,o=sunblueprints" objectclass=trigger"
dn: cn=SunBlueprintsBigTrigger,ou=triggers,o=sunblueprints
objectClass: trigger
objectClass: top
cn: SunBlueprintsBigTrigger
on: ou=testadd,o=sunblueprints
before: 1
enabled: true
explain: create or replace trigger SunBlueprintsBigTrigger on ou=testadd,ou=sun
 blueprints add action ignore
action: 2
actiondn:

The search reports exactly one entry, our trigger. Note the explanation attribute, which stores the whole create instruction, as typed by the administrator. Now create the entry, and see what happens.

CODE EXAMPLE 18 Creating an Entry

<sunone slapd-sunblueprints>~$ ldapmodify -p 10389 -D "cd=Trigger Manager" -w manager0
dn: ou=testadd, o=sunblueprints
changetype: add
objectclass: organizationalUnit
ou: testadd
description: Ciao mondo! (how Italians say Hello world!)

adding new entry ou=testadd, o=sunblueprints
ldap_add: Operations error
ldap_add: additional info: Trigger SunBlueprintsBigTrigger forbids the creation of entry ou=testadd,o=sunblueprints

It works; we receive the expected message because of the IGNORE action triggered by SunBlueprintsBigTrigger. Reviewing the log file shows the following:

CODE EXAMPLE 19 Verifying the Log File

[21/Oct/2003:02:05:57 +0200] - INFORMATION - (PID=4017,ThID=25625) triggers_pre_add_fn - conn=2 op=1 msgId=30 - Entering
[21/Oct/2003:02:05:57 +0200] - INFORMATION - (PID=4017,ThID=25625) triggers_pre_add_fn - conn=2 op=1 msgId=30 - Looking for triggers...
[21/Oct/2003:02:05:57 +0200] - INFORMATION - (PID=4017,ThID=25625) find_trigger - conn=2 op=1 msgId=30 - Entering(0x8352190, 0x47312008, (&(&(on=ou=testadd,o=sunblueprints)(before=1))(enabled=true)))
[21/Oct/2003:02:05:57 +0200] - INFORMATION - (PID=4017,ThID=25625) find_trigger - conn=2 op=1 msgId=30 - Getting results
[21/Oct/2003:02:05:57 +0200] - INFORMATION - (PID=4017,ThID=25625) find_trigger - conn=2 op=1 msgId=30 - Returning
[21/Oct/2003:02:05:57 +0200] - INFORMATION - (PID=4017,ThID=25625) triggers_pre_add_fn - conn=2 op=1 msgId=30 - Found triggers ou=testadd,o=sunblueprints
...

The routine triggers_pre_add_fn is the add pre-operation function of our pre-operation plug-in. It calls find_trigger to search for triggers. When it finds one, it executes. As a counter proof, now let's delete the trigger, and re-add the test entry:

CODE EXAMPLE 20 Deleting the Trigger and Reading the Test Entry

TRIGGERS>> delete trigger SunBlueprintsBigTrigger;
.
 ------------- Server output ----------------
Statement #0
Error code: 0
Error msg: Trigger SunBlueprintsBigTrigger successfully deleted
 --------------------------------------------
TRIGGERS>> list all triggers;
.
 ------------- Server output ----------------
Statement #0
Error code: 0
Error msg: 1 triggers found
trgme
 --------------------------------------------

Try to add the entry again:

CODE EXAMPLE 21 Adding a Duplicate Entry

<sunone slapd-sunblueprints>~$ ldapmodify -p 10389 -D "cn=Directory Manager" -w manager0
dn: ou=testadd, o=sunblueprints
changetype: add
objectclass: organizationalUnit
ou: testadd
description: Ciao mondo! (how Italians say for Hello world!)

adding new entry ou=testadd, o=sunblueprints

No problem now, because we deleted the trigger on this entry. Our language provides a construct to temporarily disable a trigger instead of removing it.

To disable a trigger, use the following as an example:

CODE EXAMPLE 22 Disabling a Trigger

TRIGGERS>> disable trigger SunBlueprintsBigTrigger;
.
 ------------- Server output ----------------
Statement #0
Error code: 0
Error msg: Trigger SunBlueprintsBigTrigger successfully disabled
 --------------------------------------------

If you repeat the LDAP add of the ou=testadd test entry, it will work. It works because the triggers_pre_add_fn function that is called before the internal add calls the find_trigger with a search filter such as the following:

(&(&(on=ou=testadd,o=sunblueprints)(before=0))(enabled=true))) 

This filter searches expressly for only enabled triggers.

The LDAP triggers language has many other possibilities. Our code example implements only some of them. We invite you to discover the other features and functions.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020