User manual NOVELL IDENTITY MANAGER DRIVER FOR ID PROVIDER 3.6.1 IMPLEMENTATION

[. . . ] novdocx (en) 13 May 2009 AUTHORIZED DOCUMENTATION implementation Guide Novell® 3. 6. 1 June 05, 2009 Identity Manager Driver for ID Provider www. novell. com Identity Manager 3. 6 ID Provider Driver Implementation Guide novdocx (en) 13 May 2009 Legal Notices Novell, Inc. , makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. , makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. [. . . ] Specify the TCP port the RMI service listens on. The defined standard port for RMI is 1099. If that port is already in use (you see errors in the trace when you start the driver), use a different port lower than 1024. This configuration assumes a port of 1199 to avoid common port conflicts. Enables the backward compatibility mode when migrating an existing ID-Server configuration to run with the new ID Provider driver. Setting this to True allows you to keep using legacy ID policies, which do not use the new schema that ships with the ID Provider. RMI server 172. 17. 2. 117 RMI port 1199 Use legacy ID-server schema? False Creating a New Driver 19 novdocx (en) 13 May 2009 Parameter Default Value Description Trace level ALL This is not the driver trace level, but the ID Provider trace level. The levels are: OFF: Tracing is turned off. INFO: Displays only informational messages. ALL: Displays all messages. 3. 2 Creating ID Policies An ID Policy container is a repository for ID policies and is used in conjunction with the ID Provider driver. An ID policy allows the ID Provider driver to generate unique IDs. When the ID Provider driver receives an ID request from a client, it generates an ID based on the ID policy specified in the request and passes it to the client. By default, there are three ID policies that are created when the driver is imported. You can use these policies or create your own. The default policies are: pid: The pid policy generates unique ids between the range of 100000 to 2000000000. It also adds the prefix of PID to each unique ID. wfid: The wfid policy generates unique ids between the range of 10000000 to 99999999. It also adds the prefix of WFID to each unique ID for the workforce ID. woid: The woid policy generates unique ids between the range of 100000 to 2000000000. It also adds the prefix of WOID to each unique ID. To create an ID policy: 1 In Designer, right-click the ID Policy container in the Outline tab, then click New > ID Policy. The ID Policy container is created when the ID Provider driver is created. The ID Policy container can only reside under the ID Provider driver. [. . . ] The associations for this driver are based of the driver name. If the driver object is renamed, all of the associations on each object are renamed as well and this can take a long time. Broker IP Address:Port The URL (Uniform Resource Locator) for the Sonic MQ broker. For example: tcp://10. 0. 0. 2:10012 Broker Name Broker Password Default message expiration (milliseconds) The name of the user used to authenticate to the Sonic MQ broker. The password of the authentication user for the Sonic MQ broker. [. . . ]