Difference between revisions of "Talk:CNM MediaWiki IAM"

From CNM Wiki
Jump to: navigation, search
(Created page with "==Potential contractors proposal==")
 
Line 1: Line 1:
==Potential contractors proposal==
+
===Potential contractors proposal===
 +
 
 +
:Several applicants reached out with their proposals from the job posting on UpWork. Below is a proposal made by one of the potential contractors for CNM MediaWiki IAM task.
 +
 
 +
==Contractor NS==
 +
:I have researched about it and get some points as follow -
 +
:LDAP:Authentication integration with MediaWiki
 +
:1. Installing required extensions : "LDAPAuthentication2" and "PluggableAuth."
 +
:2. Configuring LDAP settings: LocalSettings.php file involves specifying the LDAP server address, port, authentication method, base DN, and search attributes
 +
:3. Testing the LDAP connection and verifying it
 +
:4. Making LDAP the primary authentication method of MediaWiki by making LDAPAuthentication2 extension the authentication method.
 +
:The above points are calculated considering an organization already have an existing LDAP server.
 +
:If the organization does not have a ldap server, then we will have to create one specifically for an organization.
 +
:Process for creating LDAP server -
 +
:We will be using docker to create LDAP server and I've worked on it before but I was not able to access the server as an admin because the credentials I was using were incorrect.
 +
:1. Setting up LDAP server using docker
 +
:2. Getting into the server and setting it up according to our requirements. (This is a rough idea as I was not able to get to this step. It could take even less or more depending upon the requirements and obstacles)
 +
:Additional usages of a LDAP server -
 +
:Other than serving as an authentication method, an ldap server can also be used for the following:-
 +
:1. Directory Services: it can act as a central repository for all your files and information .
 +
:2. Managing Data and Information of users. (incl. Address book and Contact management )
 +
:3. Single Sign-On (SSO)- it can help us authenticate users once and make them access information across different platforms and service providers. Users will not have to create different accounts for each platform/service.
 +
:So My ballpark estimates is around 40 hours for this above steps. Please let me know if you have any query regarding this.

Revision as of 15:56, 9 August 2023

Potential contractors proposal

Several applicants reached out with their proposals from the job posting on UpWork. Below is a proposal made by one of the potential contractors for CNM MediaWiki IAM task.

Contractor NS

I have researched about it and get some points as follow -
LDAP:Authentication integration with MediaWiki
1. Installing required extensions : "LDAPAuthentication2" and "PluggableAuth."
2. Configuring LDAP settings: LocalSettings.php file involves specifying the LDAP server address, port, authentication method, base DN, and search attributes
3. Testing the LDAP connection and verifying it
4. Making LDAP the primary authentication method of MediaWiki by making LDAPAuthentication2 extension the authentication method.
The above points are calculated considering an organization already have an existing LDAP server.
If the organization does not have a ldap server, then we will have to create one specifically for an organization.
Process for creating LDAP server -
We will be using docker to create LDAP server and I've worked on it before but I was not able to access the server as an admin because the credentials I was using were incorrect.
1. Setting up LDAP server using docker
2. Getting into the server and setting it up according to our requirements. (This is a rough idea as I was not able to get to this step. It could take even less or more depending upon the requirements and obstacles)
Additional usages of a LDAP server -
Other than serving as an authentication method, an ldap server can also be used for the following:-
1. Directory Services: it can act as a central repository for all your files and information .
2. Managing Data and Information of users. (incl. Address book and Contact management )
3. Single Sign-On (SSO)- it can help us authenticate users once and make them access information across different platforms and service providers. Users will not have to create different accounts for each platform/service.
So My ballpark estimates is around 40 hours for this above steps. Please let me know if you have any query regarding this.