AVEVA Identity Manager

Important! This section is only applicable when you upgrade from a version earlier than Wonderware Recipe Manager Plus 2014 R2 (v2.0)

With the implementation of AVEVA Identity Manager (AIM), please make a note of the following points after upgrade:

• Depending on the SSL Certificate used, the hostname to access the AVEVA Recipe Management site may be different. This will need to be updated in any user created Start Menu Shortcuts, Browser favorites, or AVEVA InTouch applications that integrate with AVEVA Recipe Management.

• Self-signed certificate selection during the configuration will use the server hostname

• Other certificate selections during the configuration will typically use the longer site name with DNS suffix (server.mydomain.com)

• IP addresses and Localhost are no longer supported in the URL

• Windows integrated security is no longer supported - users must login with AIM

If you are using AVEVA InTouch application integrated with AVEVA Recipe Management, please expect the login process to be different. Also, the Logout process has changed and will need some minor changes to AVEVA InTouch application. For more information, see the User Guide on Integrating with AVEVA InTouch.

The AIM Admin user does not need to be configured in the AVEVA Recipe Management User editor and given privileges (this was required previous to version 2.0). You can remove this user from the AVEVA Recipe Management User editor unless there is a specific need.

Note: When you upgrade from any of the earlier versions of Wonderware Recipe Manager Plus 2014 R3 (v3.0) or Wonderware Recipe Manager Plus 2014 R3 SP1 (v3.5), ArchestrA Security Token Service (ASTS) is replaced with AVEVA Identity Manager (AIM). All the clients registered earlier with ASTS will be registered once again with AIM during configuration of Server Components and Client Connection Configuration features