Internationalization ensures that data integrity is maintained while passing through the CSI core.
The core CSI classes do not provide any character set conversions. All string type values are expected to be encoded in Java standard UCS-16. Any providers that receive or send character-based information in any other character set are responsible for character set conversions.
The following examples show how the API handles character sets:
The XML configuration provider retrieves configuration data from the XML file. It uses standard Java APIs to read and process the XML data. Any non-ASCII data embedded in the XML file is properly handled and converted to strings using an active Java XML parser (JAXP).
The LDAP attributer uses the JNDI LDAP provider to retrieve attribute data about specific subjects. Exact string references are returned from the JNDI LDAP provider, and the CSI core does not inspect the string.
The login module requests any credentials from the supplied callback. The transmission of credentials to the login module is done through the JAAS callback mechanism, requiring the login module to request any credentials from the supplied callback.