Bugzilla – Attachment 59993 Details for
Bug 17956
Provide additional functionality in the onboarding tool through configuring z-targets, and providing information on setting up SIP and LDAP services
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
Bug 17956 - [follow up] SIP -> SIP2, adding an ordered list to LDAP config
Bug-17956---follow-up-SIP---SIP2-adding-an-ordered.patch (text/plain), 7.96 KB, created by
Liz Rea
on 2017-02-07 22:54:25 UTC
(
hide
)
Description:
Bug 17956 - [follow up] SIP -> SIP2, adding an ordered list to LDAP config
Filename:
MIME Type:
Creator:
Liz Rea
Created:
2017-02-07 22:54:25 UTC
Size:
7.96 KB
patch
obsolete
>From 72e055f5d3dfe138364d060b01f8182672862b45 Mon Sep 17 00:00:00 2001 >From: Liz Rea <liz@catalyst.net.nz> >Date: Tue, 7 Feb 2017 14:30:30 +1300 >Subject: [PATCH] Bug 17956 - [follow up] SIP -> SIP2, adding an ordered list > to LDAP config > >--- > .../prog/en/modules/onboarding/onboardingstep6.tt | 39 +++++++++++----------- > 1 file changed, 20 insertions(+), 19 deletions(-) > >diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep6.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep6.tt >index f3eefc3..93b0f97 100644 >--- a/koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep6.tt >+++ b/koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep6.tt >@@ -13,17 +13,17 @@ > Koha supports the integration of different library services with it.<br> > <h2 align="left"> LDAP user authentication</h2> > LDAP (Lightweight Directory Access Protocol) can be used to authenticate (login/logout) users. If your organisation has an existing authenication system this can be integrated with the Koha ILS, and so when users enter their credentials into Koha their username and password as compared against the user records in your existing user database to find a match.<br> >- <h2 align="left">SIP communication protocol between self checkout machines and server</h2> >- SIP (Session Initiation Protocol) is a communication protocol used between ACS (Automated Circulation System in this case the Koha server) and SC (Self Checkout machines). If your library/institution has self checkout machines to checkin/checkout items then you will need to configure Koha to use SIP.<br><br> >+ <h2 align="left">SIP2 communication protocol between self checkout machines and server</h2> >+ SIP2 (Session Initiation Protocol) is a communication protocol used between ACS (Automated Circulation System in this case the Koha server) and SC (Self Checkout machines). If your library/institution has self checkout machines to checkin/checkout items then you will need to configure Koha to use SIP.<br><br> > </div> > <div id="checkbox"> > <form name="showservice" method="post" action="onboarding.pl"> > <input type="hidden" name="op" value="learnservice"/> > <input type="hidden" name="step" value="6"/> >- <h1 align="left"> Does your institution use SIP, or LDAP? </h1> >+ <h1 align="left"> Does your institution use SIP2, or LDAP? </h1> > <div> > <input type="radio" name="service" value="LDAP"> LDAP <br> >- <input type="radio" name="service" value="SIP"> SIP <br> >+ <input type="radio" name="service" value="SIP"> SIP2 <br> > </div> > <input type="submit" class="action" value="Submit"> > </form> >@@ -32,20 +32,21 @@ > </div> > [% IF (op == "learnservice") && (service == "LDAP") %] > <h1 align="left"> Setting up LDAP with Koha</h1> >- If your organisation has an existing database of user records that are used for authentication then setting up the LDAP service with Koha is a good idea because all user records would be stored in a single central location.<br> >+ If your organisation has an existing database of user records that are used for authentication, then setting up the LDAP service with Koha is a good idea because all user records would be stored in a single central location.<br> > LDAP can be used to log into both the Koha staff interface and OPAC.<br><br> > Follow these steps to set up LDAP with Koha:<br><br> >- <b>1. In your Linux terminal navigate to the directory containing the koha-conf.xml file. This will be either:</b><br> >+ <ol> >+ <li>In your Linux terminal navigate to the directory containing the koha-conf.xml file. This will be either:</li> > <ul> > <li> /etc/koha/sites/<instance-name>/koha-conf.xml<br></li> > <li> /etc/koha/koha-conf.xml<br></li> > </ul> > <i> cd /etc/koha/sites/kohadev/</i><br><br> >- <b>2. Open the koha-conf.xml file as root</b><br> >+ <li>Open the koha-conf.xml file as root</li> > <i> sudo vi koha-conf.xml</i><br><br> >- <b>3. Scroll down to line 295 and change it to:</b><br> >+ <li>Scroll down to line 295 and change it to:</li> > <i><useldapserver>1</useldapserver></i><br><br> >- <b>4. Write in the follwing information:</b><br> >+ <li>Write in the follwing information:</li> > <i><ldapserver id="ldapserver"></i><br> > <i><hostname>localhost</hostname></i><br> > <i><base>dc=metavore,dc=com</base></i><br> >@@ -57,8 +58,8 @@ > <i><anonymous_bind>0</anonymous_bind></i><br> > <i><principal_name>%s@my_domain.com</principal_name></i><br> > <i><update_password>1</update_password></i><br><br> >- <b>5. The following fields to write in (called maping fields) are optional. What they do is link the Koha database columns with the columns in your organisations user database.</b><br> >- e.g. the database column firstname is matched with the LDAP element givename<br> >+ <li>The following fields to write in (called mapping fields) are optional. What they do is link the Koha database columns with the columns in your organisations user database.</li> >+ e.g. the database column firstname is matched with the LDAP element givenname<br> > <i><mapping></i><br> > <i><firstname is="givenname" ></firstname></i><br> > <i><surname is="sn" ></surname></i><br> >@@ -72,13 +73,13 @@ > <i><categorycode is="employeetype" >PT</categorycode></i><br> > <i><phone is="telephonenumber"></phone></i><br> > <i></mapping></i><br> >- >+</ol> > <h2> Learn about further LDAP configuration</h2> > <a href="https://perldoc.koha-community.org/C4/Auth_with_ldap.html" target="_target">LDAP documentation</a> > > [% ELSIF (op == "learnservice") && (service == "SIP") %] >- <h1 align="left"> Setting up SIP with Koha</h1> >- If you installed Koha using debain packages then setting up SIP is easy, simply follow these steps:<br><br> >+ <h1 align="left"> Setting up SIP2 with Koha</h1> >+ If you installed Koha using debain packages then setting up SIP2 is easy, simply follow these steps:<br><br> > <b>1. In your Linux terminal (in the Koha root directory) write in:</b><br> > <i>sudo koha-enable-sip <instancename></i><br><br> > <b> 2. Navigate to the directory containing SIPConfig.xml</b><br> >@@ -89,12 +90,12 @@ > <b>3.1. Edit the port values in the service sections at the top of the SIPconfig.xml file, making sure that the two port values have the same IP address but different port numbers.</b><br><br> > <b>3.2. Enter an account. This account must have the same username and password as an account you have created in the Koha staff interface. Also make sure that the account is set to having 'circulate' permissions only.</b><br><br> > <b>3.3. Enter an institution. As with account this institution's ID must match the branchcode of a library created in the Koha staff interface</b><br><br> >- <b>4. In your Linux terminal start SIP by writing in:</b><br> >+ <b>4. In your Linux terminal start SIP2 by writing in:</b><br> > <i>sudo koha-start-sip <instancename></i><br><br> >- <h2> Learn how to test SIP at:<h2> >- <a href="https://wiki.evergreen-ils.org/doku.php?id=evergreen-admin:sip_support#patron_information" target="_target"> Evergreen SIP support</a><br><br> >- <h2> Important security notice about using SIP </h2> >- To ensure your SIP traffic (the request and response messages sent between you and the SIP server) are secure you must use a stunnel or VPN. >+ <h2> Learn how to test SIP2 at:<h2> >+ <a href="https://wiki.evergreen-ils.org/doku.php?id=evergreen-admin:sip_support#patron_information" target="_target"> Evergreen SIP2 support</a><br><br> >+ <h2> Important security notice about using SIP2 </h2> >+ To ensure your SIP2 traffic (the request and response messages sent between you and the SIP2 server) are secure you must use a stunnel or VPN. > [% END %] > > >-- >1.9.1
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
|
Splinter Review
Attachments on
bug 17956
:
59903
|
59904
|
59905
|
59906
|
59907
|
59908
|
59993
|
59995
|
59996
|
60000
|
62061
|
64614
|
65447
|
65448
|
68813