Skip to main content

Subscriber URIs

The following lists the URI formats for subscribers by type.

IIS7

  • Application Pools:

    • WAMUserName://LM/W3SVC – The default application pool’s identity

    • WAMUserName://LM/W3SVC/<poolname> – Application pool "<poolname>"’s identity; for example:

      WAMUserName://LM/W3SVC/TestPool

  • Microsoft FTP Site Anonymous Authentication User:

    • AnonymousUserName://LM/MSFTPSVR – Top level default anonymous authentication user for FTP sites

    • AnonymousUserName://LM/MSFTPSVR/<ftpsite>; – The anonymous authentication user for FTP site <ftpsite>; for example:

      AnonymousUserName://LM/MSFTPSVR/myftpsite

  • Virtual Directory Anonymous Authentication User:

    • AnonymousUserName://MACHINE/WEBROOT/APPHOST – Top level default anonymous authentication user for HTTP sites

    • AnonymousUserName://MACHINE/WEBROOT/APPHOST/<httpsite> – The anonymous authentication user for HTTP site <httpsite>; for example:

      AnonymousUserName://LM/MSFTPSVR/myhttpsite

    • AnonymousUserName://MACHINE/WEBROOT/APPHOST/<httpsite>/path/to/folder – The anonymous authentication user for a specific sub-folder of HTTP site <httpsite>; for example:

      AnonymousUserName://LM/MSFTPSVR/myhttpsite/this/is/a/folder

  • Physical Path Credentials for a Virtual Directory or Site

    • UNCUserName://<sitename>:/:/ – Physical path credentials for the root level of HTTP site <sitename>; for example:

      UNCUserName://My Web Site:/:/

    • UNCUserName://<sitename>:/:/<vdir> – Physical path credentials for the virtual directory <vdir> of HTTP site <sitename>;

      UNCUserName://My Web Site:/:/MyVirutalDir

    • UNCUserName://<sitename>:/:/<vdir1>/path/to/<vdir2> – Physical path credentials for the virtual directory <vdir2> of HTTP site <sitename>; for example:

      UNCUserName://My Web Site:/:/MyVirutalDir/path/to/MyOtherVdir

Services

For services the URI is simply the service name. Note this is not the "display name" that you see by default in services.msc. To see this value:

  1. Start the services.msc program.

  2. Right click on Properties.

  3. Select the General tab.

    The value listed for Service name is the complete URI for the service.

Tasks

Task Scheduler V2.0 tasks could be at the root of the task scheduler hierarchy or in a sub-folder. For tasks at the root, the URI is simply the task name. For tasks in a sub-folder the URI is fully specified path relative to the root of the task scheduler hierarchy.

Windows Server 2008 Task URI Examples:

  • This is a v1 task.job – Windows Server 2008 V1.0 compatibility task

  • ThisIsARootv2Task – Windows Server 2008 V2.0 task, at the root level

  • This\Task\Is\In\A\Folder – Windows Server 2008 V2.0 task in a sub folder

While it is technically possible to create a V1.0 task in a sub-folder on Windows Server 2008, this is not supported by Bravura Privilege , because the API provided by Microsoft does not support this. See Updating cached credentials (notification) .

DCOM

URIs for DCOM objects are simply GUIDs. The particular GUID for a DCOM URI is the DCOM object’s "Application ID".

To see the Application ID for a DCOM object do the following:

  1. Open the dcomcnfg Windows program.

  2. Browse to My Computer > DCOM Config.

  3. Right click on the DCOM object of interest.

  4. Click Properties.

  5. Select the General table.

    The GUID is listed next to each application ID.

The URI must include { and } surrounding the application ID GUID as this corresponds directly to the registry key where it is configured.

Some examples:

  • {0bd2fd17-0874-443c-b001-6c6d29580b05}

  • {1a9f7926-1281-45c9-b454-6b9bdc064fb7}

COM+ Applications

URIs for COM+ applications follows a similar structure to DCOM objects, with the difference being that the URI has COM+: prepended to it.

To see the Application ID for a COM+ application, do the following:

  1. Open the dcomcnfg Windows program.

  2. Browse to My Computer > COM+ Applications.

  3. Right click on the COM+ application of interest.

  4. Click Properties.

  5. Select the General table.

    The GUID is listed next to each application ID.

The URI must include COM+:{ and } surrounding the application ID GUID as this corresponds directly to the registry key where it is configured.

Some examples:

  • COM+:{7B4E1F3C-A702-11D2-A336-00C04F7978E0}

  • COM+:{7EE3D513B-93A7-4e90-9458-7F8602547363}

ODBC DSNs

For ODBC DSN the URI is the system DSN password which is stored in the registry hive

  • {HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI} (32-bit ODBC data sources on 32-bit machines, 64-bit ODBC data sources on 64-bit machines)

  • {HKEY_LOCAL_MACHINE\Wow6432Node\SOFTWARE\ODBC\ODBC.INI} (32-bit ODBC data sources on 64-bit machines)

In this section: