Writer instructions | |
---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines |
Changing a security model
A security model is always applied in MainView Middleware Administrator (MVMA). Security policies in-place dictates use of a particular model out of the five available.
Changing a security model is meant to be a rare occurrence in MVMA. Because of the risk of potential loss of application work, we recommend a security model change be a one-time procedure. Make sure to read all directions in this section before changing a model.
Please do not add projects, connections or other key system components before changing a security model. If a new security model is applied that uses a different authorization method, users and groups may disappear from projects. It is highly recommended that you change models immediately after installation.
Changing a model
To change a current security model, follow the instructions below. They assume that you have opened the application and navigated to the Administration Console.
Note that these instructions assume change to a model that includes LDAP for either the authentication or the authorization portion of the security model you have chosen to replace the current one.
- Select Security from the Navigation Panel, and then select the relevant Security Model from the drop-down menu. Refer to Steps 4 to 9 in the Implementing-the-LDAP_LDAP-model section for further details.
- Verify that the change has gone smoothly. Refer to Testing-a-new-security-model to confirm success.