...
The string value manipulated by get/setUID represents a "userid" or "username" that is sufficiently specific
to be unique within the context of the portal. the GlobalUID referenced above is a version of the same but
with enough additional information to be considered globally unique. For example, the network identifier
"newman" is sufficient within the Yale portal to identify a single user. Since the authentication would be
done against a Kerberos realm, the result of getGlobalUID() in this case would return
newman/@NET.YALE.EDU". In an LDAP/X.500 environment the UID might be either the UID= or CN=
field where the GlobalUID would be the entirely specified distinguished name (LDAP) or Subject field of
an X.509 certificate. [(Note that GlobalUID was incorrectly changed to an integer in the uPortal Beta and
needs to be reinstated as originally intended in order to enable future cross-realm authentication.])
The OpaqueCredentials Interface
...