• Home
• App Integrations
• Single Sign-On Integrations
• Mediawiki Single Sign-On

Mediawiki Single Sign-On SSO

---

Single Sign-On (SSO) solution by miniOrange provides secure Single Sign-On access into Mediawiki using a single set of login credentials. You can log into Mediawiki using miniOrange credentials or Azure AD credentials or any of your existing identity providers. With miniOrange SSO services, along with Mediawiki you can also login into other On-Premise and Cloud Applications using your existing Identity Providers/User Store (Azure Active Directory, Okta, Ping) credentials . Follow the given setup guide to integrate SAML SSO for your Mediawiki account.

miniOrange and Mediawiki Single Sign-On (SSO) integration supports the following features:

• SP Initiated Single Sign-On (SSO)
• IdP Initiated Single Sign-On (SSO)

Follow the Step-by-Step Guide given below for Mediawiki Single Sign-On (SSO)

1. Configure Mediawiki in miniOrange

• Login into miniOrange Admin Console.
• Go to Apps and click on Add Application button.



• In Choose Application, select SAML/WS-FED from the application type dropdown.



• Search for Mediawiki in the list, if you don't find Mediawiki in the list then, search for custom and you can set up your application in Custom SAML App.

• Enter the SP Entity ID or Issuer : <YOUR_MEDIAWIKI_BASE_URL>/extensions/SamlSingleSignOnAuth/
• Enter the ACS URL : <YOUR_MEDIAWIKI_BASE_URL>
• Click on Next to proceed further.



• In the Attribute Mapping tab configure the following attributes as shown in the image below.



• To upload respective app logo for a Custom SAML App, click on Upload Logo tab.



• Click on Save.

Get IdP Metadata Details to upload to Mediawiki:

• Go to Apps >> Manage Apps.
• Search for your app and click on the select in action menu against your app.
• Click on Metadata to get metadata details, which will be required later. Click on Show SSO Link to see the IDP initiated SSO link for Mediawiki.



• Here you will see 2 options, if you are setting up miniOrange as IDP copy the metadata details related to miniOrange from the 1st section, if you already have an external IDP or User Store (OKTA, AZURE AD, ADFS, ONELOGIN, GOOGLE APPS) you should get the metadata from the 2nd Section as shown below.



• Click on the Download Certificate button to download the metadata.xml file which you will require in Step 2.

2. Configure SSO in Mediawiki

• Download the miniOrange SAML 2.0 SSO extension zip for MediaWiki.
• In your MediaWiki FTP under extensions directory, extract the extension zip.
• Add the following code at the bottom of LocalSettings.php (root folder of MediaWiki)

			# miniOrange SAML Extension settings
			# Loads SAML extension
			# For 1.25 and above
			wfLoadExtension( 'SamlSingleSignOnAuth' );

			# For 1.24 and below
			require_once "extensions/SamlSingleSignOnAuth/SamlSingleSignOnAuth.php";

			# Enter IDP Name
			$wgMoSamlIdpName = 'miniOrange';

			# Enter SAML Issuer URL or Entity ID
			$wgMoSamlIssuer = 'https://login.xecurify.com/moas';

			# Enter SAML Login URL or ACS(Assertion Consumer Service) URL here 
			$wgMoSamlLoginURL = 'https://login.xecurify.com/moas/idp/samlsso';

			# Set binding type for login. Two possible values - HttpRedirect and HttpPost
			$wgMoSamlLoginBindingType = 'HttpRedirect';

			# Enter certificate information.
			$wgMoSamlX509CertDesc = '-----BEGIN CERTIFICATE-----
			. . . . 
			. . . . 
			. . . .
			-----END CERTIFICATE-----';

			# Only set to true if SAML is brokered through miniOrange
			$wgMoSamlIsBrokerOn = false;

			# OPTIONAL - Enter Relay State if applicable
			$wgMoSamlRelayState = '';

			# Set true if Response is signed, set false by default
			$wgMoSamlIsResponseSigned = false;

			# Set true if Assertion is signed, set true by default
			$wgMoSamlIsAssertionSigned = true;

			# Set this to true if you want to update user with incoming attributes whenever user logs in
			$wgMoSamlUpdateUser = true;

			# Auto create user if the user does not exist
			$wgMoSamlCreateUser = true;

			# Map attributes
			$wgMoSamlEmailAttr = 'email';
			$wgMoSamlUsernameAttr = 'username';
			$wgMoSamlFNameAttr = 'fname';
			$wgMoSamlLNameAttr = 'lname';
			$wgMoSamlGroupAttr = 'role';

			# Set default group for users
			$wgMoSamlDefaultGroup = 'user';

			# OPTIONAL - Set this to override $wgServer as site URL in the extension. Please make sure this is 
			# the URL where MediaWiki is hosted and '/extensions/SamlSingleSignOnAuth/' can be appended to it.
			$wgMoSamlServer = 'https://<MEDIAWIKI_DOMAIN>/mediawiki';		
		




• Provide the required settings (i.e. Entity ID, Single SignOn Service Url, Certificate Fingerprint) and save it.

  wgMoSamlIdpName	Enter the name of the IDP here. Eg. miniOrange
  wgMoSamlIssuer	Enter the Issuer/Entity ID of IDP here. Eg. https://login.xecurify.com/moas
  wgMoSamlLoginURL	Enter the SAML Login URL or ACS(Assertion Consumer Service) URL of IDP here. Eg. https://login.xecurify.com/moas/idp/samlsso
  wgMoSamlX509CertDesc	Open the certificate in Notepad and copy/paste the entire content here.
  wgMoSamlIsBrokerOn	Set to true if miniOrange is broker for another IDP. Set to false by default.
  wgMoSamlRelayState	Enter the Relay State URL of IDP here.
  wgMoSamlIsResponseSigned	Set true if Response is signed by IDP. Set false by default.
  wgMoSamlIsAssertionSigned	Set true if Response is signed by IDP. Set true by default.
  wgMoSamlUpdateUser	Set this to true if you want to update user with incoming attributes whenever user logs in
  wgMoSamlCreateUser	Set this to true if you want to auto create users. If you want to restrict access to only registered users, set this to false.
  wgMoSamlEmailAttr	Enter the Attribute Name that contains MediaWiki Email. Use NameID if Email is in Subject element.
  wgMoSamlUsernameAttr	Enter the Attribute Name that contains MediaWiki Username. Use NameID if Username is in Subject element.
  wgMoSamlFNameAttr	OPTIONAL - Enter the Attribute Name that contains MediaWiki First Name.
  wgMoSamlUsernameAttr	OPTIONAL - Enter the Attribute Name that contains MediaWiki Last Name.
  wgMoSamlGroupAttr	Enter the Attribute Name that contains MediaWiki Group/Role.
  wgMoSamlDefaultGroup	This is the MediaWiki default group/role name to which users will be mapped.
  wgMoSamlServer	OPTIONAL - This is the URL where MediaWiki is hosted and '/extensions/SamlSingleSignOnAuth/' can be appended to it. Eg. https://<MEDIAWIKI_DOMAIN>/mediawiki

3. Test SSO Configuration

Test SSO login to your Mediawiki account with miniOrange IdP:

Using SP Initiated Login

• Go to your Mediawiki URL, here you will be either asked to enter the username or click on the SSO link which will redirect you to miniOrange IdP Sign On Page.



• Enter your miniOrange login credential and click on Login. You will be automatically logged in to your Mediawiki account.

Using IDP Initiated Login

• Login to miniOrange IdP using your credentials.



• On the Dashboard, click on Mediawiki application which you have added, to verify SSO configuration.





Not able to configure or test SSO?


Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

4. Configure Your User Directory (Optional)

miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Microsoft Entra ID, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.

• Setup miniOrange as IDP
• Setup AD as User Directory
• Setup External IDP

• To add your users in miniOrange there are 2 ways:

1. Create User in miniOrange

2. Bulk Upload Users

1. Create User in miniOrange

• Click on Users >> User List >> Add User.



• Here, fill the user details without the password and then click on the Create User button.



• After successful user creation a notification message "An end user is added successfully" will be displayed at the top of the dashboard.



• Click on Onboarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.



• Now, Open your email id. Open the mail you get from miniOrange and then click on the link to set your account password.
• On the next screen, enter the password and confirm password and then click on the Single Sign-On (SSO) reset password button.



• Now, you can log in into miniOrange account by entering your credentials.

2. Bulk Upload Users in miniOrange via Uploading CSV File.

• Navigate to Users >> User List. Click on Add User button.



• In Bulk User Registration Download sample csv format from our console and edit this csv file according to the instructions.



• To bulk upload users, choose the file make sure it is in comma separated .csv file format then click on Upload.



• After uploading the csv file successfully, you will see a success message with a link.
• Click on that link you will see list of users to send activation mail. Select users to send activation mail and click on Send Activation Mail. An activation mail will be sent to the selected users.

• Click on External Directories >> Add Directory in the left menu of the dashboard.



• Select Directory type as AD/LDAP.



1. STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
2. STORE LDAP CONFIGURATION ON PREMISE: Choose this option if you want to keep your configuration in your premise and only allow access to AD inside premises. You will have to download and install miniOrange gateway in your premise.




• Enter LDAP Display Name and LDAP Identifier name.
• Select Directory Type as Active Directory.
• Enter the LDAP Server URL or IP Address against LDAP Server URL field.
• Click on Test Connection button to verify if you have made a successful connection with your LDAP server.



• In Active Directory, go to the properties of user containers/OU's and search for Distinguished Name attribute.



• Enter the valid Bind account Password.
• Click on Test Bind Account Credentials button to verify your LDAP Bind credentials for LDAP connection.



• Search Base is the location in the directory where the search for a user begins. You will get this from the same place you got your Distinguished name.



• Select a suitable Search filter from the drop-down menu. If you use User in Single Group Filter or User in Multiple Group Filter, replace the <group-dn> in the search filter with the distinguished name of the group in which your users are present. To use custom Search Filter select "Write your Custom Filter" option and customize it accordingly.



• You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Save button to add user store.




Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.

Attribute	Description
Activate LDAP	All user authentications will be done with LDAP credentials if you Activate it
Sync users in miniOrange	Users will be created in miniOrange after authentication with LDAP
Fallback Authentication	If LDAP credentials fail then user will be authenticated through miniOrange
Allow users to change password	This allows your users to change their password. It updates the new credentials in your LDAP server
Enable administrator login	On enabling this, your miniOrange Administrator login authenticates using your LDAP server
Show IdP to users	If you enable this option, this IdP will be visible to users
Send Configured Attributes	If you enable this option, then only the attributes configured below will be sent in attributes at the time of login



• Click on Save. After this, it will show you the list of User stores. Click on Test Connection to check whether you have enter valid details. For that, it will ask for username and password.



• On Successful connection with LDAP Server, a success message is shown.
• Click on Test Attribute Mapping.



• Enter a valid Username. Then, click on Test. Mapped Attributes corresponding to the user are fetched.



• After successful Attribute Mapping Configuration, go back to the ldap configuration and enable Activate LDAP in order to authenticate users from AD/LDAP.

Refer our guide to setup LDAPS on windows server.

User Import and Provisioning from AD

• Go to Settings >> Product Settings in the Customer Admin Account.



• Enable the "Enable User Auto Registration" option and click Save.



• (Optional) To send a welcome email to all the end users that will be imported, enable the "Enable sending Welcome Emails after user registration" option and click Save.



• From the Left-Side menu of the dashboard select Provisioning.



• In Setup Provisioning tab select Active Directory in the Select Application drop-down.
• Toggle the Import Users tab, click on Save button.



• On the same section, switch to Import Users section.
• Select Active Directory from the dropdown and click on the Import Users tab, to import all the users from Active Directory to miniOrange.



• You can view all the Users you have imports by selecting Users >> User List from Left Panel.



• All the imported users will be auto registered.
• These groups will be helpful in adding multiple 2FA policies on the applications.

miniOrange integrates with various external user sources such as directories, identity providers, and etc.

• Okta
• ADFS
• Ping
• AWS Cognito
• Many more

Not able to find your IdP or Need help setting it up?

Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

5. Adaptive Authentication with Mediawiki

A. Restricting access to Mediawiki with IP Blocking

You can use adaptive authentication with Mediawiki Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

You can configure Adaptive Authentication with IP Blocking in following way:

• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.



• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.





Action for behavior Change Options :




Attribute	Description
Allow	Allow user to authenticate and use services if Adaptive authentication condition is true.
Challenge	Challenge users with one of the three methods mentioned below for verifying user authenticity.
Deny	Deny user authentications and access to services if Adaptive authentication condition is true.




Challenge Type Options :




Attribute	Description
User second Factor	The User needs to authenticate using the second factor he has opted or assigned for such as OTP over SMS PUSH Notification OTP over Email And 12 more methods.
KBA (Knowledge-based authentication)	The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further.
OTP over Alternate Email	User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further.



• Now Enable Enable IP Restriction option from the IP RESTRICTION CONFIGURATION section to configure custom IP range.



• Select the Action you want to perform if the IP address is out of the range. i.e. Allow, Challenge & Deny.
• Specify the IP Address range for which you want above setting to reflect. You can add more than one IP Address ranges by clicking on following button +.
• Scroll to the end and click on save.

B. Adaptive Authentication with Limiting number of devices.

Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.

You can configure Adaptive Authentication with Device Restriction in following way


• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.




• Scroll down to Device Configuration section and enable Allow User to Register Device option to allow users to register their devices.
• Enter the Number of Devices which are allowed to register in field next to Number of Device Registrations Allowed
• Choose Action if number of devices exceeded (This will override your setting for Action for behavior Change.)
1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
2. Deny : Deny users access to the system
• Enable option Send email alerts to Users if number of Device registrations exceeded allowed count if you want to alert the user about no of devices exceeding the limit. Save the configuration.

C. Add Adaptive Authentication policy to Mediawiki.

• Login to Self Service Console >> Policies.
• Click on Edit option for predefined app policy.



• Set your application name in the Application and select password as Login Method.
• Enable Adaptive Authentication on Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step and click on save.

D.Notification and Alert Message.

This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :

• Get email alerts if users login from unknown devices or locations : Admin need to enable this option to enable receiving alerts for different alert options.
  
  
  

Option	Description
Challenge Completed and Device Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
Challenge Completed but Device Not Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
Challenge Failed	Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.






• Next subsection is Send email alerts which allows us to enable or disable alerts for admin and end-users. To enable alerts for admins, you can enable the “Administrators” switch button.




• In case you want multiple admins accounts to receive alerts then you can enable the option for admin and then enter the admin emails separated by a ‘,’ in the input field next to Administrators email to receive alerts label. To enable alerts for the end-users, you can enable the “End Users” switch button.
• In case you want to customize the deny message that end user receive in case his authentication denied due to adaptive policy, you can do this by entering the message inside “Deny message for Adaptive Authentication” text box.


How to add a trusted Device

1. When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

External References

• Single Sign-On (SSO)
• What is Single Sign-On (SSO) and How does SSO Work?
• Other Integrations
• Know more about Bluehost Single Sign-On (SSO)