Client-side Authentication APIs

You can set the preferred client authentication mechanisms by using the following APIs. The API extensions for Java consist of overloaded variants of existing session-creation methods.

• nSessionFactory

  public static nSession create(nSessionAttributes attr, 
     String username, String password)

  public static nSession create(nSessionAttributes attr, 
     nReconnectHandler handler, String username, String password)

  public static nSession createMultiplexed(nSession session, 
     String user, String passwd)

  public static nSession createMultiplexed(nSessionAttributes sessionAttributes, 
     String userName, String passwd)

• nRealmAdmin
  Note: This API has been deprecated in Universal Messaging 10.7.

  Constructor - 
  nRealmAdmin(nSessionAttributes sAttr, String username, String password)

  Constructor - 
  nRealmAdmin(nSessionAttributes sAttr, String username, String password, 
     boolean followMaster)

• nRealmNode

  Constructor - 
  nRealmNode(nSessionAttributes sAttr, String username, String passwd)

• JNDI

  If you're using the NirvanaContextFactory class (loads the Universal Messaging provider for JMS) as the value of the standard java.naming.factory.initial context-environment key, then the standard context-environment keys java.naming.security.principal and java.naming.security.credentials should be assigned the username and password, respectively.

  This is a standard JNDI configuration and is compatible with all JNDI-based providers.