Skip past navigation linksSecure Global Desktop Administration Guide > Arrays, servers and load balancing > The Secure Global Desktop datastore and Tarantella Federated Naming

The Secure Global Desktop datastore and Tarantella Federated Naming

Read this topic to...
  • Understand what Tarantella Federated Naming is and what it's used for.

The Secure Global Desktop datastore is the sum of all the information used by the various components of Secure Global Desktop. The datastore includes:

The diverse sources of this information are all accessed in the same way, using TFN (Tarantella Federated Naming) names.

Each object in the datastore has a unique TFN name. TFN names include a component identifying the source of the information: the namespace. TFN names commonly have this form:

Skip past command syntax or program code.../namespace/name-within-namespace

The ... indicates the "root" of TFN. Each namespace may use a different naming scheme. The namespace part of the TFN name acts as a "gateway" to that naming scheme.

For example, an object in the ENS organizational hierarchy might have this name:

Skip past command syntax or program code.../_ens/o=Indigo Insurance/ou=Marketing/cn=Cust-o-Dat

The _ens indicates the ENS part of the datastore: the ENS namespace. Within ENS, the object's name is o=Indigo Insurance/ou=Marketing/cn=Cust-o-Dat, indicating an object with common name Cust-o-Dat, belonging to the organizational unit Marketing, which in turn belongs to the organization Indigo Insurance.

Other namespaces might use a different naming scheme. For example, a similar object stored on an LDAP directory server might have this name:

Skip past command syntax or program code..../_service/sco/tta/ldapcache/cn=Cust-o-Dat,ou=Marketing,o=Indigo Insurance

Here the order of the hierarchy is reversed, and is comma-separated rather than slash-separated. However, the syntax is different only within the LDAP namespace.

Why do TFN names matter?

Some command-line tools for configuring Secure Global Desktop require you to name objects to work with. In many cases the flexibility of Secure Global Desktop means you can name objects from many different parts of the datastore.

For example, if you're using tarantella passcache to add a new password cache entry, you need to name the resource you're caching the password for. This might be the name of an ENS host object or a DNS name, for example. In both cases you need to give the name that Secure Global Desktop uses: the TFN name.

Commonly used namespaces

Namespace Example Description
ENS .../_ens/o=Indigo Insurance/ou=Marketing/cn=Cust-o-Dat

The ENS namespace, containing objects with Secure Global Desktop-specific behavior.

LDAP .../_service/sco/tta/ldapcache/cn=Cust-o-Dat,ou=Marketing,o=Indigo Insurance

Objects in an LDAP directory server.

DNS .../_dns/verona.indigo-insurance.com

Hosts on the network.

Related topics