Page Operations
Browse Space
Objectives
The Fortress test plans are really a set of informal case studies and scenarios that would be ideal for Beta testers to consider when exercising the new functionality in the Fortress release. If there is insufficient documentation to get started, or things seem confusing please comment to that effect on the relevant section of the Fortress notes and/or within the farcry-beta group.
Security
Security is completely overhauled. Everything to do with Security needs a work out.
Relevant documentation:
FarCry User Directory
FarCry has its own built in user directory. Create users and groups.
How do I create a central FarCry user directory for multiple applications to share?
 | Steps needed. |
TODO notes:
- create a central farcry application; we will share this applications user directory
- create some users
- create a second farcry application
- create a user directory component that looks to the central farcry application for directory information
FarCry Roles & Permissions
Create a new role, and assign permissions. Map your new role to a user group and test that it works.
How do I change what menus and tabs are available in the webtop for a specific role?
TODO:
- create a new role, or nominate an existing role (for example, "contributors")
- assign a user group from an available user directory
- assign relevant permissions
- login in as a user with that role
- confrim that the webtop has been built accordingly
Build a User Directory
Fortress allows users to build external user directory connectivity for FarCry solutions easily both in plugins and projects. Beta testers should try and construct an external user directory perhaps to LDAP, ActiveDirectory, OpenID, hard-coded users/passwords, external database schema.
Apply Webskin Security to Your Views
Fortress allows you to secure access to specific views across your entire application including both display and edit handlers. Try enforcing view levelsecurity within your application.
