The IMM service should provide an updated API where all use of the troublesome
SaNameT type is replaced by the SaStringT type or the SaConstStringT type #625.
Also needed is a new flag value for attribute definitions: SA_IMM_ATTR_DN.
Defining an attribute in an IMM class definition on the SaStringT type and
also setting the flag SA_IMM_ATTR_DN, will mean that the attribute is intended
to hold a value that should be a DN.
Other flags that make sense to also set on such an attribute definition where
SA_IMM_ATTR_RDN if this is the RDN attribute. Just as having SaNameT the type of an RDN attribute indicates that the class is an association class, having SaStringT and SA_IMM_ATTR_DN combined with SA_IMM_ATTR_RDN would also indicate that this is an association class. SA_IMM_ATTR_NO_DANGLING. Currently (OpenSAF 4.5) is only allowed on attributes of type SaNameT, but will of course be allowed also on attributes of type SaStringT if the SA_IMM_ATTR_DN flag is also set. The exception is the RDN attribute which still can not have the SA_IMM_ATTR_NO_DANGLING set. The reason is that the RDN atribute, even if defined on SaNameT, or on SaStringT with SA_IMM_ATTR_DN flag, actually does not contain a simple DN value. The RDN attribute of an association object contains a value on the form X=Y where the right hand side is a DN. Strictly speaking the logical type of an RDN attribute is never a simple DN/reference, even if the type is SaNameT.
All the other flags may also be used in combination with SA_IMM_ATTR_DN, with
the normal meaning.