Maybe try

plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \
         org.dspace.authenticate.IPAuthentication



On Thu, 2014-01-09 at 09:36 -0800, c_sugumaran wrote:
> We would like to allow the particular IP address computer (Here IP
> 10.101.14.54)  only to open our Dspace repository so we have edited the
> following  files and restarted the TOMCAT.   But it is not restricting to
> that IP computer only.  From other computer in the intranet also the Dspace
> is opening.  
> 
> Any one can help us, what are all other to be edited in any other file ?
> 
> Can you give us, the corrected method
> 
> 
> authentication.cfg
> 
> #---------------------------------------------------------------#
> #----------ENABLED AUTHENTICATION METHODS/PLUGINS---------------#
> #---------------------------------------------------------------#
> # This configuration setting contains the listing of all        #
> # currently enabled authentication plugins. DSpace supports an  #
> # Authentication "stack" which allows you to enable multiple    #
> # forms of Authentication at the same time. Enabled             #
> # Authentication plugins are invoked in order until one of them #
> # succeeds.                                                     #
> #---------------------------------------------------------------#
> # Out-of-the-box DSpace Authentication Plugins include:
> #  * Authentication by Password 
> #        Plugin class: org.dspace.authenticate.PasswordAuthentication
> #        Configuration file: authentication-password.cfg
> #  * Shibboleth Authentication
> #        Plugin class: org.dspace.authenticate.ShibAuthentication
> #        Configuration file: authentication-shibboleth.cfg
> #  * LDAP Authentication
> #        LDAP Plugin class: org.dspace.authenticate.LDAPAuthentication
> #        Configuration file: authentication-ldap.cfg
> #  * IP Address Authentication
> #        Plugin class: org.dspace.authenticate.IPAuthentication
> #        Configuration file: authentication-ip.cfg
> #  * X.509 Certificate Authentication
> #        Plugin class: org.dspace.authenticate.X509Authentication
> #        Configuration file: authentication-x509.cfg
> #
> # One or more of the above plugins can be enabled by listing its plugin
> class in
> # the below setting. To configure the enabled plugin(s) visit the
> configuration file(s)
> # listed above. See the DSpace Configuration Documentation for more details.
> #
> # Example Authentication Stack (Using Shibboleth & Authentication by
> Password):
> # plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \
> #         org.dspace.authenticate.ShibAuthentication, \
> #         org.dspace.authenticate.PasswordAuthentication
> 
> plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \
>         org.dspace.authenticate.IPAuthentication, \
>         org.dspace.authenticate.PasswordAuthentication
> 
> 
> 
> 
> authentication-ip.cfgb
> #---------------------------------------------------------------#
> #---------IP-ADDRESS AUTHENTICATION CONFIGURATIONS--------------#
> #---------------------------------------------------------------#
> # Configuration properties used by the IP-Address Based         #
> # Authentication plugin, when it is enabled.                    #
> #---------------------------------------------------------------#
> #
> # In order to enable IP-Address Authentication, you must first ensure the
> # 'org.dspace.authenticate.IPAuthentication' class is added to the 
> # list of enabled AuthenticationMethods in 'authenticate.cfg'.
> # See 'authenticate.cfg' for more info.
> 
> # The following setting allows you to map DSpace Group names to one or more
> IP ranges.
> # If a user arrives at DSpace from one of the IP ranges, they will be added
> to the
> # specified DSpace group for the remainder of their session.
> #
> # ip.GROUPNAME = iprange[, iprange ...]
> #
> # Note if the GROUPNAME contains blanks you must escape it,
> # e.g. Department\ of\ Statistics
> # The 'iprange' may be any of these syntaxes: Full IPs, partial IPs;
> network/netmask; network/CIDR
> #
> ip.LPSC = 10.101.14.54
> 
> 
> In future we would like that the Dpspace to open to from 10.101.14.50 to
> 10.101.14.60 computers not all persons in the intranet.
> 
> can any one help us to inform us, in the above two files, what is wrong ?
> 
> Expecting your early guidance.
> 
> C. Sugumaran
> Scientist / Engr SF
> Doc. Officer, LPSC / ISRO
> Valiamala - Trivandrum
> 
> 
> 
> --
> View this message in context: 
> http://dspace.2283337.n4.nabble.com/IP-AUTHENTICATION-tp4670171.html
> Sent from the DSpace - Tech mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today. 
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette: 
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette



------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to