Implement Anonymous Authentication

When using anonymous authentication, users log in as guests and do not need to provide a password. Each guest user assumes the profile defined by the Public group.

This dynamically created guest user is not the same as the "Guest" user which is visible in the User Manager.

Guest users inherit security settings, including privileges and permissions, project access, security filter, and connection map information, from the Public/Guest group; they are not part of the Everyone group.

By default, guest users have no privileges; you must assign this group any privileges that you want the guest users to have. Privileges that are grayed out in the User Editor are not available by default to a guest user. Other than the unavailable privileges, you can determine what the guest user can and cannot do by modifying the privileges of the Public/Guest user group and by granting or denying it access to objects. For more information, see Controlling Access to Functionality: Privileges and Controlling Access to Objects: Permissions.

All objects created by guest users must be saved to public folders and are available to all guest users. Guest users may use the History List, but their messages in the History List are not saved and are purged when the guest users log out.

To Enable Anonymous Access to a Project Source

By default, anonymous access is disabled at both the server and the project levels.

1. In Developer, log into the project source with a user that has administrative privileges.
2. From the folder List, select Administration.
3. From the File menu, select Properties.
4. In the Security tab, click Add.
5. Select the Public/Guest group.
6. In the Access Permission list, select Connect.
7. Click OK.
8. Follow the procedure in Configuring the Authentication Mode for a Project Source and select Anonymous authentication. When users log into this project source, they are now automatically logged in as guest users and not prompted for a login or password.