<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>brianwatrous Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>brianwatrous Tracker</description>
    <pubDate>Thu, 23 Nov 2023 12:23:37 GMT</pubDate>
    <dc:date>2023-11-23T12:23:37Z</dc:date>
    <item>
      <title>Pages, not steps</title>
      <link>https://communities.vmware.com/t5/VMware-Education-Services/Pages-not-steps/m-p/2875063#M924</link>
      <description>&lt;P&gt;Finally realized why my students keep calling pages in the VLP lab manuals "steps". It is because the VLP manual calls pages steps. Sigh...&lt;/P&gt;&lt;P&gt;(See attachment)&lt;/P&gt;&lt;P&gt;In the attached screenshot, the top of the lab manual says "Step 70".&lt;/P&gt;&lt;P&gt;In my lingo, 70 isn't a step number. It is a "page" number.&lt;/P&gt;&lt;P&gt;I'll suggest to the VLP team that they change the UI to say "page" number.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Oct 2021 15:58:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Education-Services/Pages-not-steps/m-p/2875063#M924</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2021-10-28T15:58:49Z</dc:date>
    </item>
    <item>
      <title>${backToLoginLabel}</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/backToLoginLabel/m-p/2231110#M18961</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Running standalone vRO appliance, version 8.0.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Attempting to log in to &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://vro_fqdn/orchestration-ui" rel="nofollow"&gt;http://vro_fqdn/orchestration-ui&lt;/A&gt;&lt;SPAN&gt;, received the following error:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Screen Shot 2020-01-16 at 11.56.08 AM.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/16601i5226FAA0C0FCFEAF/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2020-01-16 at 11.56.08 AM.png" alt="Screen Shot 2020-01-16 at 11.56.08 AM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue appears to be related to the standalone vRO appliance date/time not being properly time sync'ed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See also... &lt;A href="https://communities.vmware.com/thread/610718"&gt;vCenter 6.7U2 / VRO 7.6 Orchestrator Client SSO Issue&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jan 2020 20:00:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/backToLoginLabel/m-p/2231110#M18961</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2020-01-16T20:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: help with finding action gethostfolder</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/help-with-finding-action-gethostfolder/m-p/1695263#M12888</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi. I'm Brian (from the Orchestrator videos). Thanks for watching. Glad to hear how excited you are about demoing Orchestrator!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Jörg is correct that some of the actions in the video come from a package that was created for the Orchestrator course (&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://mylearn.vmware.com/mgrreg/courses.cfm?ui=www_edu&amp;amp;a=one&amp;amp;id_subject=38842"&gt;http://mylearn.vmware.com/mgrreg/courses.cfm?ui=www_edu&amp;amp;a=one&amp;amp;id_subject=38842&lt;/A&gt;&lt;SPAN&gt;). I am so accustomed to having those actions at my disposal that I didn't stop to realize that viewers like you don't have them. The error is mine.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As Jörg said in his reply to your post, we are working to make the package available. Thank you for your patience.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jan 2013 22:12:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/help-with-finding-action-gethostfolder/m-p/1695263#M12888</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2013-01-18T22:12:35Z</dc:date>
    </item>
    <item>
      <title>Orchestrator video tutorials online</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Orchestrator-video-tutorials-online/m-p/2674616#M22513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;vCenter Orchestrator video tutorials are now available online at &lt;A href="http://vmwarelearning.com"&gt;http://vmwarelearning.com&lt;/A&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2012 00:59:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Orchestrator-video-tutorials-online/m-p/2674616#M22513</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2012-12-13T00:59:11Z</dc:date>
    </item>
    <item>
      <title>Re: WebService / Workflow ID / find</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/WebService-Workflow-ID-find/m-p/2625806#M21453</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;Christophe Decanini wrote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or if you have a wf workflow attribute : wf.id&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's what I assumed the code would be, but before I typed in the code, I checked the API Explorer. The API Explorer doc for the workflow object doesn't list a property called "id". Went with the doc instead of my intuition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bolstered by your post, I did a "wf.id" in my workflow, and it worked as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, Christophe.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 20:55:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/WebService-Workflow-ID-find/m-p/2625806#M21453</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2012-11-07T20:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: WebService / Workflow ID / find</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/WebService-Workflow-ID-find/m-p/2625803#M21450</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for all the preceding tips, but...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Given a workflow object, is there a way to programatically get that workflow's Id? I expected there to be a property in the workflow object called id, but there is no such property.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 20:27:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/WebService-Workflow-ID-find/m-p/2625803#M21450</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2012-11-07T20:27:44Z</dc:date>
    </item>
    <item>
      <title>Configuring the Microsoft plug-in</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-the-Microsoft-plug-in/m-p/1667381#M12687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a document which explains how to configure the Microsoft plug-in? I don't see any info in the Orchestrator docs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;EM&gt;vCenter Orchestrator Administration Guide (vCenter Orchestrator 4.0.1)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;  &lt;EM&gt;vCenter Orchestrator Installation and Configuration Guide (vCenter Orchestrator 4.0.1)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;  &lt;EM&gt;vCenter Orchestrator Developer's Guide (vCenter Orchestrator 4.0.1)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am aware of that Active Directory requires the username DN to be specified in the form CN=vmoadmin,CN=Users,DC=example,DC=com (as discussed in this &lt;A href="http://communities.vmware.com/message/1119466"&gt;post&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error I'm receiving occurs when I configure the MS plug-in in the Orchestrator Configuration tool. The error message is "User or password or default domain is not correct.".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The file I've attached illustrates my AD structure and the values I'm using in the configuration of the MS plug-in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S. The following is quite possibly irrelevant, but I've noticed that if I attempt to log in as EXAMPE\vmoadmin at the console of my AD server, I receive the error "The local policy of this system does not permit you to logon interactively". I don't expect the error is related, but I figured I should offer that tidbit of info just in case.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 May 2010 20:59:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-the-Microsoft-plug-in/m-p/1667381#M12687</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2010-05-18T20:59:10Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSH plug-in</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-SSH-plug-in/m-p/2062144#M16519</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've made progress following your suggestion, Stuart. Thanks so far.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Previously I couldn't get the SSH plugin to do anything at all because it couldn't authenticate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I can get the SSH plugin working partially, but now when I try to set an SSH:Folder variable, I can open the SSH plugin, and I can open the host. But when I try to see what's in the root folders on the host, I end up with the following error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    java.net.ConnectException: Connection refused: connect&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone have any suggestions why I can't see the contents of the root folders?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 May 2010 12:58:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-SSH-plug-in/m-p/2062144#M16519</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2010-05-16T12:58:37Z</dc:date>
    </item>
    <item>
      <title>Configuring SSH plug-in</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-SSH-plug-in/m-p/2062142#M16517</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Could someone elaborate on what the 'note' (see below) means in the section titled &lt;EM&gt;Configure the SSH Plug-In&lt;/EM&gt; in the &lt;A href="http://www.vmware.com/pdf/vco_401_install_config_guide.pdf"&gt;vCenter Orchestrator Installation and Configuration Guide&lt;/A&gt;? I'm trying to get the SSH plug-in working, but it appears to fail during authentication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any insight you can provide.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Configure the SSH Plug-In&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;You can set up the SSH plug-in to ensure encrypted connections.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;Procedure&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;1. Log in to the Orchestrator configuration interface as vmware.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;2. Click SSH.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;3. Click New connection.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;4. In the Host name text box, enter the host to access with SSH through Orchestrator.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;NOTE: The username and password are not required because Orchestrator uses&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;the credentials of the currently logged-in user to run SSH commands. You must&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;reproduce the accounts you want to work on SSH on target hosts from the LDAP&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;server.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;5. Click Apply changes.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;     &lt;STRONG&gt;The host is added to the list of SSH connections.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;6. (Optional) Configure an entry path on the server.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;     &lt;STRONG&gt;a. Click New root folder.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;     &lt;STRONG&gt;b. Enter the new path and click Apply changes.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;The SSH host is available in the Inventory view of the Orchestrator smart client.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 May 2010 15:32:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-SSH-plug-in/m-p/2062142#M16517</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2010-05-13T15:32:26Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring VMO to use OpenLDAP</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-VMO-to-use-OpenLDAP/m-p/221483#M22</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The formatting of the LDIF file in the example above is incorrect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need a blank line before each dn: entry.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 09 May 2010 20:38:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-VMO-to-use-OpenLDAP/m-p/221483#M22</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2010-05-09T20:38:26Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring VMO to use OpenLDAP</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-VMO-to-use-OpenLDAP/m-p/221482#M21</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm configuring VMO to use OpenLDAP (running on RedHat Enterprise Linux 3). I was experiencing failures in my attempts to configure the &lt;STRONG&gt;LDAP&lt;/STRONG&gt; and &lt;STRONG&gt;Plugins&lt;/STRONG&gt; tabs within the VMware Orchestrator Configuration utility. Specifically, the failures were occuring when attempting to use the "Test Login" capability (of the &lt;STRONG&gt;LDAP&lt;/STRONG&gt; tab) and when attempting to authenticate to LDAP from the &lt;STRONG&gt;Plugins&lt;/STRONG&gt; tab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I fixed the problem by adding the "uid" line to my ldif file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've included my ldap.conf, slapd.conf, and ldif files below to provide another sample OpenLDAP configuration for others in the future.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, it wasn't clear to me during my attempts to get VMO and OpenLDAP configured to work together it wasn't clear to me what credentials that I needed to supply on the &lt;STRONG&gt;LDAP&lt;/STRONG&gt; and &lt;STRONG&gt;Plugins&lt;/STRONG&gt; tabs. What ultimately worked was using "vmoAdmin" (the &lt;U&gt;short&lt;/U&gt; name for my &lt;U&gt;LDAP user account&lt;/U&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;ldap.conf&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;# $OpenLDAP: pkg/ldap/libraries/libldap/ldap.conf,v 1.4.8.6 2000/09/05 17:54:38 kurt Exp $ &lt;BR /&gt; # &lt;BR /&gt; # LDAP Defaults &lt;BR /&gt; # &lt;BR /&gt; # See ldap.conf(5) for details &lt;BR /&gt; # This file should be world readable but not world writable. &lt;BR /&gt; #BASE dc=example, dc=com &lt;BR /&gt; #URI ldap://ldap.example.com ldap://ldap-master.example.com:666 &lt;BR /&gt; #SIZELIMIT 12 &lt;BR /&gt; #TIMELIMIT 15 &lt;BR /&gt; #DEREF  never &lt;BR /&gt; HOST 127.0.0.1 &lt;BR /&gt; BASE dc=example,dc=com &lt;BR /&gt; URI ldap://localhost &lt;BR /&gt; TLS_REQCERT&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;slapd.conf&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.8.8.7 2001/09/27 20:00:31 kurt Exp $ &lt;BR /&gt; # &lt;BR /&gt; # See slapd.conf(5) for details on configuration options. &lt;BR /&gt; # This file should NOT be world readable. &lt;BR /&gt; # &lt;BR /&gt; include  /etc/openldap/schema/core.schema &lt;BR /&gt; include  /etc/openldap/schema/cosine.schema &lt;BR /&gt; include  /etc/openldap/schema/inetorgperson.schema &lt;BR /&gt; include  /etc/openldap/schema/nis.schema &lt;BR /&gt; include  /etc/openldap/schema/redhat/autofs.schema &lt;BR /&gt; include  /etc/openldap/schema/redhat/kerberosobject.schema &lt;BR /&gt; password-hash &lt;SPAN __jive_macro_name="smd5"&gt;&lt;/SPAN&gt; &lt;BR /&gt; # Define global ACLs to disable default read access. &lt;BR /&gt; # Do not enable referrals until AFTER you have a working directory &lt;BR /&gt; # service AND an understanding of referrals. &lt;BR /&gt; #referral ldap://root.openldap.org &lt;BR /&gt; #pidfile //var/run/slapd.pid &lt;BR /&gt; #argsfile //var/run/slapd.args &lt;BR /&gt; # Create a replication log in /var/lib/ldap for use by slurpd. &lt;BR /&gt; #replogfile /var/lib/ldap/master-slapd.replog &lt;BR /&gt; # Load dynamic backend modules: &lt;BR /&gt; # modulepath /usr/sbin/openldap &lt;BR /&gt; # moduleload back_ldap.la &lt;BR /&gt; # moduleload back_ldbm.la &lt;BR /&gt; # moduleload back_passwd.la &lt;BR /&gt; # moduleload back_shell.la &lt;BR /&gt; # &lt;BR /&gt; # The next three lines allow use of TLS for connections using a dummy test &lt;BR /&gt; # certificate, but you should generate a proper certificate by changing to &lt;BR /&gt; # /usr/share/ssl/certs, running "make slapd.pem", and fixing permissions on &lt;BR /&gt; # slapd.pem so that the ldap user or group can read it. &lt;BR /&gt; # TLSCertificateFile /usr/share/ssl/certs/slapd.pem &lt;BR /&gt; # TLSCertificateKeyFile /usr/share/ssl/certs/slapd.pem &lt;BR /&gt; # TLSCACertificateFile /usr/share/ssl/certs/ca-bundle.crt &lt;BR /&gt; # &lt;BR /&gt; # Sample Access Control &lt;BR /&gt; # Allow read access of root DSE &lt;BR /&gt; # Allow self write access &lt;BR /&gt; # Allow authenticated users read access &lt;BR /&gt; # Allow anonymous users to authenticate &lt;BR /&gt; # &lt;BR /&gt; #access to dn="" by * read &lt;BR /&gt; #access to * &lt;BR /&gt; # by self write &lt;BR /&gt; # by users read &lt;BR /&gt; # by anonymous auth &lt;BR /&gt; # &lt;BR /&gt; # if no access controls are present, the default is: &lt;BR /&gt; # Allow read by all &lt;BR /&gt; # &lt;BR /&gt; # rootdn can always write! &lt;BR /&gt; ####################################################################### &lt;BR /&gt; # ldbm database definitions &lt;BR /&gt; ####################################################################### &lt;BR /&gt; database ldbm &lt;BR /&gt; suffix  "dc=example,dc=com" &lt;BR /&gt; #suffix  "o=My Organization Name,c=US" &lt;BR /&gt; rootdn  "cn=ldapadmin,dc=example,dc=com" &lt;BR /&gt; #rootdn  "cn=Manager,o=My Organization Name,c=US" &lt;BR /&gt; # Cleartext passwords, especially for the rootdn, should &lt;BR /&gt; # be avoided.  See slappasswd(8) and slapd.conf(5) for details. &lt;BR /&gt; # Use of strong authentication encouraged. &lt;BR /&gt; # rootpw  vmware &lt;BR /&gt; # The MD5 password below is 'vmware' &lt;BR /&gt; rootpw  &lt;SPAN __jive_macro_name="SMD5"&gt;cXICgynhE87XFanNV9bOA+EYBlY= &lt;BR /&gt; # rootpw  secret &lt;BR /&gt; # rootpw  &lt;SPAN __jive_macro_name="crypt"&gt;&lt;/SPAN&gt;ijFYNcSNctBYg &lt;BR /&gt; # The database directory MUST exist prior to running slapd AND &lt;BR /&gt; # should only be accessible by the slapd/tools. Mode 700 recommended. &lt;BR /&gt; directory /var/lib/ldap &lt;BR /&gt; # Indices to maintain &lt;BR /&gt; index objectClass,uid,uidNumber,gidNumber,memberUid eq &lt;BR /&gt; index cn,mail,surname,givenname   eq,subinitial &lt;BR /&gt; # Replicas to which we should propagate changes &lt;BR /&gt; #replica host=ldap-1.example.com:389 tls=yes &lt;BR /&gt; # bindmethod=sasl saslmech=GSSAPI &lt;BR /&gt; # authcId=host/ldap-master.example.com@EXAMPLE.COM

 


&lt;U&gt;ldif&lt;/U&gt;

&lt;/SPAN&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;dn: dc=example,dc=com &lt;BR /&gt; dc: example &lt;BR /&gt; description: This is an example company. &lt;BR /&gt; objectClass: dcObject &lt;BR /&gt; objectClass: organization &lt;BR /&gt; o: Example &lt;BR /&gt; dn: ou=Employees,dc=example,dc=com &lt;BR /&gt; ou: Employees &lt;BR /&gt; description: All the employees in Example, Inc. &lt;BR /&gt; objectClass: organizationalUnit &lt;BR /&gt; dn: ou=Groups,dc=example,dc=com &lt;BR /&gt; ou: Groups &lt;BR /&gt; description: Groups in Example, Inc. &lt;BR /&gt; objectClass: organizationalUnit &lt;BR /&gt; dn: cn=vmoAdmin,ou=Employees,dc=example,dc=com &lt;BR /&gt; objectClass: person &lt;BR /&gt; objectClass: OrganizationalPerson &lt;BR /&gt; objectClass: inetOrgPerson &lt;BR /&gt; cn: vmoAdmin &lt;BR /&gt; sn: vmoAdmin &lt;BR /&gt; uid: vmoAdmin &lt;BR /&gt; userpassword: &lt;/P&gt;&lt;/BLOCKQUOTE&gt;cXICgynhE87XFanNV9bOA+EYBlY= &lt;BR /&gt; dn: cn=vmoAdmins,ou=Groups,dc=example,dc=com &lt;BR /&gt; objectClass: groupOfNames &lt;BR /&gt; cn: vmoAdmins &lt;BR /&gt; member: cn=vmoAdmin,ou=Employees,dc=example,dc=com&lt;P&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Nov 2008 18:39:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Configuring-VMO-to-use-OpenLDAP/m-p/221482#M21</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2008-11-03T18:39:29Z</dc:date>
    </item>
    <item>
      <title>Re: Online Training - Phone issue</title>
      <link>https://communities.vmware.com/t5/VMware-Education-Services/Online-Training-Phone-issue/m-p/1160518#M270</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've been using Skype with great success this week to attend a live online delivery of the I&amp;amp;C course. And my Skype balance hasn't lowered even a penny because the call is toll free.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Oct 2008 23:08:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Education-Services/Online-Training-Phone-issue/m-p/1160518#M270</guid>
      <dc:creator>brianwatrous</dc:creator>
      <dc:date>2008-10-24T23:08:16Z</dc:date>
    </item>
  </channel>
</rss>

