MCS from version 1.3.0
Table of Contents
...
...
Create SAML Configuration Application in Okta
...
Go to the Oktawebsite.
Create an account if you don’t have one.
Follow Okta’s instructions on their website.
Log in to your Okta account.
Follow Okta’s instructions for signing in.
...
Steps to Create the SAML Configuration Application in Okta
Navigate to Applications → Applications in the left sidebar.
Click the Create App Integration button.
Select SAML 2.0 and click Next.
Provide an App Name and click .
Click Next.
Configure the SAML settings in the Configure SAML tab:
Single Sign-On URL: Enter the MCS Login URL Route prefixed with
https://{Your_MCS_IP}/.
Example:Code Block https://{Your_MCS _IP}/api/5.0/auth/saml/login/callback
| Note |
|---|
Note: In the link above, replace |
Audience URI (SP Entity ID): Enter a unique ID. (This must match the Entity ID in MCS).
Name ID Format: Select Persistent.
Scroll down and click Next.
Fill in the Feedback tab:
In the App Type field, enable This is an internal app that we have created.
Click Finish.
...
Create Groups and Users in the SAML Configuration Application
| Expandnote | |
|---|---|
| title | Why Are Groups Important?The user's role in MCS is determined by their group in Okta when logging Users who need access to MCS must have a role defined in MCS and belong to a corresponding group in Okta (associated with the SAML Configuration Application) with the same name. When users log in via Okta, as MCS does not recognize the user directly. store their credentials or role information, as the login occurs through Okta. To bridge this, Okta sends the group name to MCS during the login process. MCS matches the group name to a role with the same name, granting the appropriate permissions based on the group-to-role mapping. Each user must belong to exactly one group in Okta, which corresponds to exactly one role in MCS. Users without a group role or assigned to multiple groups will not be able to access the systemlog in, as their role cannot be resolved. |
Steps to Create Groups in Okta
Navigate to Directory → Groups in the left sidebar.
Click Add Group.
Provide a Name and an optional Description for the group.
Refresh the page to view the new group.
Repeat for additional groups if needed.
| Infonote |
|---|
Note: |
...
Assign Group Attribute Statements in the SAML Configuration Application
Navigate to Applications → Applications.
Find the SAML Configuration Application you previously created in Okta.
Click the name of your SAML Configuration Application.
Navigate to the General tab in the SAML Configuration Application.
Scroll to the SAML Settings section and click Edit.
In the Edit SAML Integration, in the General Settings tab:
Click on the Next button to get to the Configure SAML tab.
Scroll down in the SAML Settings to the Group Attribute Statements (optional).
Enter group in the Name field. (This must be spelled exactly as "group").
Leave Name Format as Unspecified.
Choose a filter (e.g., Equals or Starts With) and provide the appropriate value based on your group's name.
Enter the name of the group you created in Okta, based on the filter you selected in the previous step.
| Info |
|---|
Note: In the Filter field, it is recommended to select Starts With and then enter the prefix for all the groups you created in Okta for use with MCS. |
| Note |
|---|
Note: |
...
Example of the Filter field:
If using the Equals filter, type the exact group name.
If using the Starts With filter, type the group name prefix.
| Warning |
|---|
Note: You cannot click Add Another to assign multiple groups because, in version 1.3.0, MCS expects only one group attribute statement with the name group, and Okta allows only a single group attribute statement with that name. If you want to use the Equals filter, you can only configure one group with the group attribute statement named group. To associate multiple groups with MCS for different roles, you must use other filters, such as Starts with, and ensure all your groups have names that share a common prefix. For example, the following is an invalid configuration:  |
Click Next and finish the configuration.
| Note |
|---|
Important NotesIf a user logs in via SAML, the group name in the Identity Provider must match the role name in MCS. Users must belong to a group in Okta to log in to MCS, with the group's name being assigned as their role in MCS. |
Scroll down and click Next.
Fill in the Feedback tab:
In the App Type field, enable This is an internal app that we have created.
Click Finish.
...
Assign Users to Groups in Okta
...
Navigate to Applications → Applications.
Find the SAML Configuration Application you previously created in Okta.
Click the name of your SAML Configuration Application.
Navigate to the Assignments tab in the SAML Configuration Application.
Click Assign → Assign to Groups.
Assign the relevant groups to the SAML Configuration Application.
Click on Done to save the changes.
...
Steps to Configure SAML in MCS
Navigate to Applications → Applications.
Find the SAML Configuration Application you previously created in Okta.
Click the name of your SAML Configuration Application.
Go to the Sign On tab at the top of the page.
Click the View SAML Setup Instructions button on the right side of the page, located under SAML Setup.
Copy the Identity Provider Single Sign-On URL field for later use.
Copy the X.509 Certificate field for later use. (Use the value between BEGIN CERTIFICATE and END CERTIFICATE).
Click on the menu icon.
A display of all the available widgets will open.
Navigate to Management → Identity Providers.
Fill in the required fields:
Entity ID / Issuer: Use the Audience URI (SP Entity ID) field you configured when setting up the SAML Configuration Application in Okta.
Entrypoint / IDP URL: Paste the Identity Provider Single Sign-On URL field you copied in step 7.
Certificate: Paste the X.509 Certificate field you copied in step 8.
Click Save to complete the configuration.
...
You and your users can now log in to MCS using Okta via SAML, in addition to the basic login method.
...
Create a Role in MCS
When creating a group in Okta (associated with the SAML Configuration Application), you must also create a corresponding role with the same name (label) in MCS. Users who require access to MCS must have a role defined in MCS and belong to a group in Okta with the same name.
| Expand | ||
|---|---|---|
| ||
This setup is crucial because when a user logs into MCS via Okta, MCS does not have access to the user's credentials or role information. Since the login occurs through Okta and not directly through MCS, the user's data is not stored in MCS. To resolve this, Okta sends the group information to MCS during the login process. MCS then uses the group name sent by Okta to identify the associated role within MCS that has the same name (label) as the group's name. This ensures the user is granted the correct permissions based on their role in MCS, as determined by the group-to-role mapping. |
Create one role in MCS for each group you created in Okta and associated with the SAML Configuration Application:
Ensure that the role has the same name (label) as the group.
Refer to the guide How to Create a New Role to create each role.
...