Sponsored Content
Special Forums Cybersecurity Single ldap account, different passwords? Post 302886712 by Blackacid on Monday 3rd of February 2014 09:24:57 AM
Old 02-03-2014
Appreciate the feedback. That has definitely been considered, but apparently also gunned down as not "cost effective". I my initial plan is what I need to stick with. I just need to convince the management this is the better approach. I suspect that if I draft out the cost of 4 LDAP servers and the time required to manage those servers will be a compelling argument... or maybe if they really want it, they'll pony up the cash. Smilie
 

2 More Discussions You Might Find Interesting

1. AIX

How do I enable 16MB pages for an account that uses LDAP?

With an account that uses "Login AUTHENTICATION GRAMMAR" = "LDAP", I get this when trying to enable 16 MB page support: -bash-3.00# chuser capabilities=CAP_BYPASS_RAC_VMM,CAP_PROPAGATE trbld Error changing "capabilities" to "CAP_BYPASS_RAC_VMM,CAP_PROPAGATE" : Value is invalid. I also tried... (1 Reply)
Discussion started by: mdyeager
1 Replies

2. UNIX for Dummies Questions & Answers

One account with multiple passwords

Hi I am currently using saslauthd to authenticate users onto an imap server (cyrus). I need to have it so that a user can logon to an account with multiple passwords (even just two would work). Is this at all possible within linux? Right now I am using the shadow file for authentication with... (2 Replies)
Discussion started by: duonut
2 Replies
RDF::Query::Plan::Service(3pm)				User Contributed Perl Documentation			    RDF::Query::Plan::Service(3pm)

NAME
RDF::Query::Plan::Service - Executable query plan for remote SPARQL queries. VERSION
This document describes RDF::Query::Plan::Service version 2.908. METHODS
Beyond the methods documented below, this class inherits methods from the RDF::Query::Plan class. "new ( $endpoint, $plan, $silent, $sparql, [ \%logging_keys ] )" Returns a new SERVICE (remote endpoint call) query plan object. "<$endpoint"> is the URL of the endpoint (as a node object). "<$plan"> is the query plan representing the query to be sent to the remote endpoint (needed for cost estimates). "<$sparql"> is the serialized SPARQL query to be sent to the remote endpoint. Finally, if present, "<%logging_keys"> is a HASH containing the keys to use in logging the execution of this plan. Valid HASH keys are: * bf - The bound/free string representing C<<$plan>> "new_from_plan ( $endpoint, $plan, $context )" Returns a new SERVICE query plan object. "<$endpoint"> is the URL of the endpoint (as a string). "<$plan"> is the query plan representing the query to be sent to the remote endpoint. The exact SPARQL serialization that will be used is obtained by getting the originating RDF::Query::Algebra object from "<$plan">, and serializing it (with the aid of the RDF::Query::ExecutionContext object "<$context">). "execute ( $execution_context )" "next" "close" "endpoint" "sparql" Returns the SPARQL query (as a string) that will be sent to the remote endpoint. "lhs" "silent" Returns a boolean value indicating whether the service plan will ignore errors. "pattern" Returns the query plan that will be used in the remote service call. "distinct" Returns true if the pattern is guaranteed to return distinct results. "ordered" Returns true if the pattern is guaranteed to return ordered results. "plan_node_name" Returns the string name of this plan node, suitable for use in serialization. "plan_prototype" Returns a list of scalar identifiers for the type of the content (children) nodes of this plan node. See RDF::Query::Plan for a list of the allowable identifiers. "plan_node_data" Returns the data for this plan node that corresponds to the values described by the signature returned by "plan_prototype". "graph ( $g )" "explain" Returns a string serialization of the query plan appropriate for display on the command line. AUTHOR
Gregory Todd Williams <gwilliams@cpan.org> perl v5.14.2 2012-01-31 RDF::Query::Plan::Service(3pm)
All times are GMT -4. The time now is 06:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy