Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cleanup information about old Mattermost versions #7062

Merged
merged 1 commit into from
Apr 11, 2024
+6 −9
Merged

Cleanup information about old Mattermost versions #7062

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions source/onboard/sso-saml-onelogin.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ Create a OneLogin connection app for Mattermost SSO

Attribute parameters map attributes between OneLogin and Mattermost. For more information on which attributes are configurable, see our :ref:`documentation on SAML configuration settings <saml-enterprise>`.

*Email* attributes are required. For Mattermost servers running version 3.3 and earlier, ``FirstName`` and ``LastName`` attributes are also required.
*Email* attributes are required.

a. Select the **Parameters** tab.
b. Select **Add Parameter**.
Expand Down Expand Up @@ -143,8 +143,6 @@ Configure SAML Sign-On for Mattermost

The **Email Atttribute** field and the **Username Attribute** field are required, and should match the values that you entered earlier when you configured the SAML Test Connector on OneLogin.

For Mattermost servers running version 3.3 and earlier, ``FirstName`` and ``LastName`` attributes are also required.

.. image:: ../../source/images/okta_13_mattermost_attributes.png
:alt: On the System Console SAML page, set attributes for the SAML Assertions used to update user information in Mattermost. Both Email Attribute and Username Attribute are required, and should match the values entered when configuring the SAML Test Connector in OneLogin.

Expand Down
11 changes: 5 additions & 6 deletions source/scale/high-availability-cluster.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,12 +39,11 @@ To ensure your instance and configuration are compatible with high availability,

Back up your Mattermost database and file storage locations before configuring high availability. For more information about backing up, see :doc:`../deploy/backup-disaster-recovery`.

1. Upgrade Mattermost Server to version 4.0 or later. See :doc:`../upgrade/upgrading-mattermost-server`.
2. Set up a new Mattermost server with version 4.0 or later by following one of our **Install Guides**. This server must use an identical copy of the configuration file, ``config.json``. Verify the servers are functioning by hitting each independent server through its private IP address.
3. Modify the ``config.json`` files on both servers to add ``ClusterSettings``. See the :ref:`high availability configuration settings <configure/environment-configuration-settings:high availability>` documentation for details.
4. Verify the configuration files are identical on both servers then restart each machine in the cluster.
5. Modify your NGINX setup so that it proxies to both servers. For more information about this, see `proxy server configuration`_.
6. Open **System Console > Environment > High Availability** to verify that each machine in the cluster is communicating as expected with green status indicators. If not, investigate the log files for any extra information.
1. Set up a new Mattermost server by following one of our **Install Guides**. This server must use an identical copy of the configuration file, ``config.json``. Verify the servers are functioning by hitting each independent server through its private IP address.
2. Modify the ``config.json`` files on both servers to add ``ClusterSettings``. See the :ref:`high availability configuration settings <configure/environment-configuration-settings:high availability>` documentation for details.
3. Verify the configuration files are identical on both servers then restart each machine in the cluster.
4. Modify your NGINX setup so that it proxies to both servers. For more information about this, see `proxy server configuration`_.
5. Open **System Console > Environment > High Availability** to verify that each machine in the cluster is communicating as expected with green status indicators. If not, investigate the log files for any extra information.

Add a server to the cluster
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down
Loading