|
Mac Dev Center
Mac OS X Reference Library Networking, Internet, & Web: Services & Discovery Directory Service Framework Reference
|
DirServices.h |
| Includes: | <AvailabilityMacros.h> <DirectoryService/DirServicesTypes.h> |
Directory Services introduction text.
dsAddAttribute |
tDirStatus dsAddAttribute ( tRecordReference inRecordReference, tDataNodePtr inNewAttribute, tAccessControlEntryPtr inNewAttributeAccess, tDataNodePtr inFirstAttributeValue ) ;
Add an attribute type to a record.
dsAddAttributeValue |
tDirStatus dsAddAttributeValue ( tRecordReference inRecordReference, tDataNodePtr inAttributeType, tDataNodePtr inAttributeValue ) ;
Add data to a record.
dsAddChildPIDToReference |
tDirStatus dsAddChildPIDToReference ( tDirReference inDirRef, SInt32 inValidChildPID, UInt32 inValidAPIReferenceToGrantChild ) ;
dsCloseAttributeList |
tDirStatus dsCloseAttributeList ( tAttributeListRef inAttributeListRef ) ;
dsCloseAttributeValueList |
tDirStatus dsCloseAttributeValueList ( tAttributeValueListRef inAttributeValueListRef ) ;
dsCloseDirNode |
tDirStatus dsCloseDirNode ( tDirNodeReference inDirNodeReference ) ;
inDirNodeReferenceDirectory node reference obtained from dsOpenDirNode
Tear down a directory node session.
dsCloseDirService |
tDirStatus dsCloseDirService ( tDirReference inDirReference ) ;
inDirReferenceDirectory Services API reference to be closed
dsCloseRecord |
tDirStatus dsCloseRecord ( tRecordReference inRecordReference ) ;
dsCreateRecord |
tDirStatus dsCreateRecord ( tDirNodeReference inDirNodeReference, tDataNodePtr inRecordType, tDataNodePtr inRecordName ) ;
dsCreateRecordAndOpen |
tDirStatus dsCreateRecordAndOpen ( tDirNodeReference inDirNodeReference, tDataNodePtr inRecordType, tDataNodePtr inRecordName, tRecordReference *outRecordReference ) ;
dsDeleteRecord |
tDirStatus dsDeleteRecord ( tRecordReference inRecordReference ) ;
dsDoAttributeValueSearch |
tDirStatus dsDoAttributeValueSearch ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, tDataListPtr inRecordTypeList, tDataNodePtr inAttributeType, tDirPatternMatch inPatternMatchType, tDataNodePtr inPattern2Match, UInt32 *inOutMatchRecordCount, tContextData *inOutContinueData ) ;
inDirNodeReferenceDirectory node reference obtained from dsOpenDirNode.
inOutDataBufferA client-allocated buffer to hold the data results.
inRecordTypeListThe list of record types to search over.
inAttributeTypeWhich attribute type we are to match on.
inPatternMatchTypeThe matching criteria used.
inPattern2MatchValue to match for the above attribute type.
inOutMatchRecordCountHow many records we found that met the match criteria. However, also a limit of the maximum records returned as provided by the client. If zero or less, then assuming no limit on number of records to be returned.
inOutContinueDataPointer to a tContextData variable. If (*inOutCountinueData == 0) there is no more data. Otherwise can be used in the next call to the same routine to get the remainder of the information. If client does not use non-NULL continue data, then dsReleaseContinueData should be called to clean up.
Use dsGetRecordEntry, dsGetAttributeEntry, and dsGetAttributeValue to parse the inOutDataBuffer parameter for results.
dsDoAttributeValueSearchWithData |
tDirStatus dsDoAttributeValueSearchWithData ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, tDataListPtr inRecordTypeList, tDataNodePtr inAttributeMatchType, tDirPatternMatch inPatternMatchType, tDataNodePtr inPatternToMatch, tDataListPtr inAttributeTypeRequestList, dsBool inAttributeInfoOnly, UInt32 *inOutMatchRecordCount, tContextData *inOutContinueData ) ;
inOutDataBufferA client-allocated buffer to hold the data results.
inRecordTypeListThe list of record types to search over.
inAttributeMatchTypeWhich attribute type we are to match on.
inPatternMatchTypeThe matching criteria used.
inPatternToMatchValue to match for the above attribute type.
inAttributeTypeRequestListWhat type of attributes do we want for each record.
inAttributeInfoOnlyDo we want attribute information only, or values too.
inOutMatchRecordCountHow many records we found that met the match criteria. However, also a limit of the maximum records returned as provided by the client. If zero or less, then assuming no limit on number of records to be returned.
dsDoDirNodeAuth |
tDirStatus dsDoDirNodeAuth ( tDirNodeReference inDirNodeReference, tDataNodePtr inDirNodeAuthName, dsBool inDirNodeAuthOnlyFlag, tDataBufferPtr inAuthStepData, tDataBufferPtr outAuthStepDataResponse, tContextData *inOutContinueData ) ;
inDirNodeAuthOnlyFlagIndicates if the client wishes to use the results of this authentication process as their identity for this directory session (inDirNodeReference) for directory node access authorization. If the flag value is "false", then at the completion of the auth process both the Directory Services API and the Plug-in should use this "identity" to grant or deny access for all future directory service calls. If the flag value is "true", then at the completion of of the auth process no identity information will be used by the directory services or Plug-in for authorization purposes. A file server just wishing to authenticate a user, but not change how/who it is accessing the directory as would set this parameter to "true".
Do an authentication session with the given authentication type. When a authentication is successful the error code 'eDSNoErr' is returned and the outAuthStepDataResponse parameter will contain a correctly formed kDS1AttrAuthCredential value. This AuthCredential can be used for future authentications for this and other directory nodes in the directory system. Not all directory nodes will support authenticating in this manner, but most should. In addition the current kDS1AttrAuthCredential value can always be obtained via dsGetDirNodeInfo call with kDS1AttrAuthCredential as one of the requested attributes. Directory Nodes that support using a kDS1AttrAuthCredential will list DSAuthCredential as a support authentication method. Support authentication methods can be determined by calling dsGetDirNodeInfo and requesting the kDSNAttrAuthMethod attribute for that directory node. NOTE: it is important to note that while some Directory Nodes may support the attempt of using a kDS1AttrAuthCredential to authenticate, when the Directory Node plug-in decodes the Credential the authentication attempt may still fail for plug-in specific reasons (the plug-in may find the level of original authentication insufficient for it's requirements or configuration, or the credential may have expired and is no longer valid). In addition when using a kDS1AttrAuthCredential to authentication to a different directory node than the original kDS1AttrAuthCredential was generated, the level of access granted by the directory node plug-in may not match the level in the original directory node. Access granted to the contents of a directory node is entirely at the descretion of the directory node plug-in and the directory system it represents.
dsDoDirNodeAuthOnRecordType |
tDirStatus dsDoDirNodeAuthOnRecordType ( tDirNodeReference inDirNodeReference, tDataNodePtr inDirNodeAuthName, dsBool inDirNodeAuthOnlyFlag, tDataBufferPtr inAuthStepData, tDataBufferPtr outAuthStepDataResponse, tContextData *inOutContinueData, tDataNodePtr inRecordType ) ;
inDirNodeAuthOnlyFlagIndicates if the client wishes to use the results of this authentication process as their identity for this directory session (inDirNodeReference) for directory node access authorization. If the flag value is "false", then at the completion of the auth process both the Directory Services API and the Plug-in should use this "identity" to grant or deny access for all future directory service calls. If the flag value is "true", then at the completion of of the auth process no identity information will be used by the directory services or Plug-in for authorization purposes. A file server just wishing to authenticate a user, but not change how/who it is accessing the directory as would set this parameter to "true".
inRecordTypeThe record type to perform the auth against for the inDirNodeAuthName. If this is passed in as NULL then call will be routed as dsDoDirNodeAuth() which assumes a record type of kDSStdRecordTypeUsers.
Do an authentication session with the given authentication type on the specified record type. When a authentication is successful the error code 'eDSNoErr' is returned and the outAuthStepDataResponse parameter will contain a correctly formed kDS1AttrAuthCredential value. This AuthCredential can be used for future authentications for this and other directory nodes in the directory system. Not all directory nodes will support authenticating in this manner, but most should. In addition the current kDS1AttrAuthCredential value can always be obtained via dsGetDirNodeInfo call with kDS1AttrAuthCredential as one of the requested attributes. Directory Nodes that support using a kDS1AttrAuthCredential will list DSAuthCredential as a supported authentication method. Support authentication methods can be determined by calling dsGetDirNodeInfo and requesting the kDSNAttrAuthMethod attribute for that directory node. NOTE: it is important to note that while some Directory Nodes may support the attempt of using a kDS1AttrAuthCredential to authenticate, when the Directory Node plug-in decodes the Credential the authentication attempt may still fail for plug-in specific reasons (the plug-in may find the level of original authentication insufficient for it's requirements or configuration, or the credential may have expired and is no longer valid). In addition when using a kDS1AttrAuthCredential to authentication to a different directory node than the original kDS1AttrAuthCredential was generated, the level of access granted by the directory node plug-in may not match the level in the original directory node. Access granted to the contents of a directory node is entirely at the descretion of the directory node plug-in and the directory system it represents.
dsDoMultipleAttributeValueSearch |
tDirStatus dsDoMultipleAttributeValueSearch ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, tDataListPtr inRecordTypeList, tDataNodePtr inAttributeType, tDirPatternMatch inPatternMatchType, tDataListPtr inPatterns2Match, UInt32 *inOutMatchRecordCount, tContextData *inOutContinueData ) ;
inOutDataBufferA client-allocated buffer to hold the data results.
inRecordTypeListThe list of record types to search over.
inAttributeTypeWhich attribute type we are to match on.
inPatternMatchTypeThe matching criteria used.
inPatterns2MatchThe list of values to match for the above attribute type.
inOutMatchRecordCountHow many records we found that met the match criteria. However, also a limit of the maximum records returned as provided by the client. If zero or less, then assuming no limit on number of records to be returned.
Use dsGetRecordEntry, dsGetAttributeEntry, and dsGetAttributeValue to parse the inOutDataBuffer parameter for results.
dsDoMultipleAttributeValueSearchWithData |
tDirStatus dsDoMultipleAttributeValueSearchWithData ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, tDataListPtr inRecordTypeList, tDataNodePtr inAttributeMatchType, tDirPatternMatch inPatternMatchType, tDataListPtr inPatternsToMatch, tDataListPtr inAttributeTypeRequestList, dsBool inAttributeInfoOnly, UInt32 *inOutMatchRecordCount, tContextData *inOutContinueData ) ;
inOutDataBufferA client-allocated buffer to hold the data results.
inRecordTypeListThe list of record types to search over.
inAttributeMatchTypeWhich attribute type we are to match on.
inPatternMatchTypeThe matching criteria used.
inPatternsToMatchThe list of values to match for the above attribute type.
inAttributeTypeRequestListWhat type of attributes do we want for each record.
inAttributeInfoOnlyDo we want attribute information only, or values too.
inOutMatchRecordCountHow many records we found that met the match criteria. However, also a limit of the maximum records returned as provided by the client. If zero or less, then assuming no limit on number of records to be returned.
dsDoPlugInCustomCall |
tDirStatus dsDoPlugInCustomCall ( tDirNodeReference inDirNodeReference, UInt32 inCustomRequestCode, tDataBufferPtr inCustomRequestData, tDataBufferPtr outCustomRequestResponse ) ;
Used for custom direct communications with plugs-ins.
dsFindDirNodes |
tDirStatus dsFindDirNodes ( tDirReference inDirReference, tDataBufferPtr inOutDataBufferPtr, tDataListPtr inNodeNamePattern, tDirPatternMatch inPatternMatchType, UInt32 *outDirNodeCount, tContextData *inOutContinueData ) ;
inDirReferenceDirectory reference established with dsOpenDirService
inOutDataBufferPtrContains a client allocated buffer to store results. Data is extracted with dsGetDirNodeName.
inNodeNamePatternA tDataList pointer, which contains the pattern to be matched.
inPatternMatchTypeWhat type of match to perform on inNodeNamePattern. Valid values for this are: eDSExact, eDSStartsWith, eDSEndsWith, eDSContains. Other match types will return an error.
outDirNodeCountNumber of items in the client buffer.
inOutContinueDataPointer to a tContextData variable, if (*inOutCountinueData == 0) there is no more data otherwise can be used in a 2nd call to the same routine to get the remainder of the directory node list. if client does not use if (*inOutCountinueData != 0) and the client doesn't wish to continue then dsReleaseContinueData should be called to clean up.
Find directory nodes matching a certain pattern.
dsFlushRecord |
tDirStatus dsFlushRecord ( tRecordReference inRecordReference ) ;
dsGetAttributeEntry |
tDirStatus dsGetAttributeEntry ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, tAttributeListRef inAttributeListRef, UInt32 inAttributeInfoIndex, tAttributeValueListRef *outAttributeValueListRef, tAttributeEntryPtr *outAttributeInfoPtr ) ;
Get an attribute entry from a buffer.
dsGetAttributeValue |
tDirStatus dsGetAttributeValue ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, UInt32 inAttributeValueIndex, tAttributeValueListRef inAttributeValueListRef, tAttributeValueEntryPtr *outAttributeValue ) ;
Get an attribute value from a buffer.
dsGetDirNodeCount |
tDirStatus dsGetDirNodeCount ( tDirReference inDirReference, UInt32 *outDirectoryNodeCount ) ;
inDirReferenceDirectory reference established with dsOpenDirService.
outDirectoryNodeCountContains count of the total number of directory nodes.
Get the count of the total number of directory nodes in the system.
dsGetDirNodeCountWithInfo |
tDirStatus dsGetDirNodeCountWithInfo ( tDirReference inDirReference, UInt32 *outDirectoryNodeCount, UInt32 *outDirectoryNodeChangeToken ) ;
inDirReferenceDirectory Reference Established with dsOpenDirService
outDirectoryNodeCountContains count of the total number of nodes in the directory
outDirectoryNodeChangeTokenContains token that changes upon any registered node changes.
Get the count of the total number of DirNodes in the Directory System with change information ie. a token gets returned with a different value if there has been a change in the registered nodes so the client can retain the first token and compare with the second to see if any registered nodes have changed
dsGetDirNodeInfo |
tDirStatus dsGetDirNodeInfo ( tDirNodeReference inDirNodeReference, tDataListPtr inDirNodeInfoTypeList, tDataBufferPtr inOutDataBuffer, dsBool inAttributeInfoOnly, UInt32 *outAttributeInfoCount, tAttributeListRef *outAttributeListRef, tContextData *inOutContinueData ) ;
inDirNodeReferenceDirectory node reference obtained from dsOpenDirNode.
inDirNodeInfoTypeListtDataList containing the types of requested data.
inOutDataBufferClient-allocated buffer to hold the data results.
inAttributeInfoOnlyThis flag is set to true if the client wants attribute info only, not attribute values.
outAttributeInfoCountA count of the number of data types present in the DataBuffer.
inOutContinueDataPointer to a tContextData variable. If (*inOutCountinueData == 0) there is no more data. Otherwise can be used in the next call to the same routine to get the remainder of the information. If client does not use non-NULL continue data, then dsReleaseContinueData should be called to clean up.
Get information about a directory node: authentication methods, unique ID's, ICON information, access controls, record types contained in this node, plug-in information, directory node/type/signature.
dsGetDirNodeList |
tDirStatus dsGetDirNodeList ( tDirReference inDirReference, tDataBufferPtr inOutDataBufferPtr, UInt32 *outDirNodeCount, tContextData *inOutContinueData ) ;
inDirReferenceDirectory reference established with dsOpenDirService
inOutDataBufferPtrContains a client allocated buffer to store results..data is extracted with dsGetDirNodeName
outDirNodeCountNumber of directory node names contained in dataBuffer
inOutContinueDataPointer to a tContextData variable, if (*inOutCountinueData == 0) there is no more data otherwise can be used in a 2nd call to the same routine to get the remainder of the directory node list. if client does not use if (*inOutCountinueData != 0) and the client doesn't wish to continue then dsReleaseContinueData should be called to clean up..
Fill a buffer with the names of all the directory nodes.
dsGetDirNodeName |
tDirStatus dsGetDirNodeName ( tDirReference inDirReference, tDataBufferPtr inOutDataBuffer, UInt32 inDirNodeIndex, tDataListPtr *inOutDataList ) ;
inDirReferenceDirectory reference established with dsOpenDirService
inOutDataBufferA buffer containing all the directory node names from dsGetDirNodeList or dsFindDirNodes
inDirNodeIndexOne-based index of directory node name to fetch/build.
inOutDataListAddress of tDataListPtr that is built by this call. The client is responsible for disposing of it with dsDataListDeAllocate.
Parse the return Buffer from dsFindDirNodes or dsGetDirNodeList and build a tDataList representing the directory node's name.
dsGetNextAttributeEntry |
tDirStatus dsGetNextAttributeEntry ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, tAttributeListRef inAttributeListRef, UInt32 inAttributeInfoIndex, SInt32 *inOutAttributeOffset, tAttributeValueListRef *outAttributeValueListRef, tAttributeEntryPtr *outAttributeInfoPtr ) ;
Get the next attribute entry from a buffer. Optimized buffer extraction with offset value. Intent is to only service this call in the FW unless falling through to old call.
dsGetNextAttributeValue |
tDirStatus dsGetNextAttributeValue ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, UInt32 inAttributeValueIndex, SInt32 *inOutAttributeValueOffset, tAttributeValueListRef inAttributeValueListRef, tAttributeValueEntryPtr *outAttributeValue ) ;
Get the next attribute value from a buffer. Optimized buffer extraction with offset value. Intent is to only service this call in the FW unless falling through to old call.
dsGetRecordAttributeInfo |
tDirStatus dsGetRecordAttributeInfo ( tRecordReference inRecordReference, tDataNodePtr inAttributeType, tAttributeEntryPtr *outAttributeInfoPtr ) ;
dsGetRecordAttributeValueByID |
tDirStatus dsGetRecordAttributeValueByID ( tRecordReference inRecordReference, tDataNodePtr inAttributeType, UInt32 inValueID, tAttributeValueEntryPtr *outEntryPtr ) ;
dsGetRecordAttributeValueByIndex |
tDirStatus dsGetRecordAttributeValueByIndex ( tRecordReference inRecordReference, tDataNodePtr inAttributeType, UInt32 inValueIndex, tAttributeValueEntryPtr *outEntryPtr ) ;
dsGetRecordAttributeValueByValue |
tDirStatus dsGetRecordAttributeValueByValue ( tRecordReference inRecordReference, tDataNodePtr inAttributeType, tDataNodePtr inAttributeValue, tAttributeValueEntryPtr *outEntryPtr ) ;
inRecordReferenceRecord reference from an opened record.
inAttributeTypeAttribute type to retrieve.
inAttributeValueAttribute value whose existence is to be confirmed.
outEntryPtrOutput data structure.
This routine verifies the existence of an attribute value within a record.
dsGetRecordEntry |
tDirStatus dsGetRecordEntry ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, UInt32 inRecordEntryIndex, tAttributeListRef *outAttributeListRef, tRecordEntryPtr *outRecordEntryPtr ) ;
inDirNodeReferenceDirectory node reference obtained from dsOpenDirNode.
inOutDataBufferA client-allocated buffer to hold the data results.
Get a record entry from a buffer.
dsGetRecordList |
tDirStatus dsGetRecordList ( tDirNodeReference inDirNodeReference, tDataBufferPtr inOutDataBuffer, tDataListPtr inRecordNameList, tDirPatternMatch inPatternMatchType, tDataListPtr inRecordTypeList, tDataListPtr inAttributeTypeList, dsBool inAttributeInfoOnly, UInt32 *inOutRecordEntryCount, tContextData *inOutContinueData ) ;
inDirNodeReferenceDirectory node reference obtained from dsOpenDirNode.
inOutDataBufferA client-allocated buffer to hold the data results.
inRecordNameListA tDataList of Record names to be matched.
inPatternMatchTypeHow is the pattern matched for the inRecordNameList.
inRecordTypeListWhat record types do we want returned?
inAttributeTypeListWhat type of attributes do we want for each record.
inAttributeInfoOnlyDo we want attribute information only, or do we also want attribute values.
inOutRecordEntryCountHow many record entries are there in the client buffer. However, also a limit of the maximum records returned as provided by the client. If zero or less, then assuming no limit on number of records to be returned.
inOutContinueDataPointer to a tContextData variable. If (*inOutCountinueData == 0) there is no more data. Otherwise can be used in the next call to the same routine to get the remainder of the information. If client does not use and continue data is non-NULL then dsReleaseContinueData should be called to clean up.
Get a list of records, optionally: by name, by type, with or without attribute info, with or without attribute value data.
dsGetRecordReferenceInfo |
tDirStatus dsGetRecordReferenceInfo ( tRecordReference inRecordReference, tRecordEntryPtr *outRecordInfo ) ;
dsIsDirServiceLocalRunning |
dsIsDirServiceRunning |
dsOpenDirNode |
tDirStatus dsOpenDirNode ( tDirReference inDirReference, tDataListPtr inDirNodeName, tDirNodeReference *outDirNodeReference ) ;
inDirReferenceDirectory reference established with dsOpenDirService.
inDirNodeNameDirectory node name to open. Should be split into path components, for example as a result of dsBuildListFromPath
outDirNodeReferenceValid call with eDSNoErr, results in a directory node session reference. This reference represents the client's session context for the contents of the given directory node.
Establish a session for a particular directory node.
dsOpenDirService |
tDirStatus dsOpenDirService ( tDirReference *outDirReference ) ;
outDirReferencereference to use in subsequent Directory Services API calls
Opens Directory Services API reference. Must be called before any other Directory Services API calls because this reference is needed for any other call.
dsOpenDirServiceLocal |
tDirStatus dsOpenDirServiceLocal ( tDirReference *outDirRef, const char *inFilePath ) ;
outDirRefreference to use in subsequent Directory Services API calls
inFilePathunix file path for a ds local node database [if either NULL or "Default" input then the default node is used]
Opens Directory Services API reference to Local Access only daemon. Must be called before any other Directory Services API calls because this reference is needed for any other call.
dsOpenDirServiceProxy |
tDirStatus dsOpenDirServiceProxy ( tDirReference *outDirRef, const char *inHostOrIPAddress, UInt32 inIPPort, tDataNodePtr inAuthMethod, tDataBufferPtr inAuthStepData, tDataBufferPtr outAuthStepDataResponse, tContextData *ioContinueData ) ;
outDirRefreference to use in subsequent Directory Services API calls
inHostOrIPAddresseither the hostname or dotted IP address of the remote DirectoryService machine
inIPPorteither the client defined port or "0" which then allows use of the default
Opens Directory Services API reference via TCP. Must be called before any other Directory Services API calls because this reference is needed for any other call.
dsOpenRecord |
tDirStatus dsOpenRecord ( tDirNodeReference inDirNodeReference, tDataNodePtr inRecordType, tDataNodePtr inRecordName, tRecordReference *outRecordReference ) ;
dsReleaseContinueData |
tDirStatus dsReleaseContinueData ( tDirReference inDirReference, tContextData inContinueData ) ;
inDirReferenceDirectory reference established with dsOpenDirService if inContinueData was returned by dsGetDirNodeList or dsFindDirNodes, node reference (type tDirNodeReference) established with dsOpenDirNode if inContinueData was returned by a node specific API such as dsGetRecordList, dsDoAttributeValueSearch, dsDoAttributeValueSearchWithData, dsDoMultipleAttributeValueSearch, dsDoMultipleAttributeValueSearchWithData, dsGetDirNodeInfo, dsDoDirNodeAuth, or dsDoDirNodeAuthOnRecordType.
inContinueDataPointer to a tContextData variable which will be cleaned up by Directory Services
If continue data from dsGetDirNodeList or any other Directory Services function is non-NULL, then call this routine to release the continue data if the client chooses not to continue the directory node listing or other operation.
dsRemoveAttribute |
tDirStatus dsRemoveAttribute ( tRecordReference inRecordReference, tDataNodePtr inAttribute ) ;
dsRemoveAttributeValue |
tDirStatus dsRemoveAttributeValue ( tRecordReference inRecordReference, tDataNodePtr inAttributeType, UInt32 inAttributeValueID ) ;
dsSetAttributeValue |
tDirStatus dsSetAttributeValue ( tRecordReference inRecordReference, tDataNodePtr inAttributeType, tAttributeValueEntryPtr inAttributeValuePtr ) ;
dsSetAttributeValues |
tDirStatus dsSetAttributeValues ( tRecordReference inRecordReference, tDataNodePtr inAttributeType, tDataListPtr inAttributeValuesPtr ) ;
inRecordReferencethe record reference of the record to modify
inAttributeTypethe attribute type to set values for
inAttributeValuesPtrthe list of all values for the attribute
sets an attribute to have the given list of values
dsSetRecordName |
tDirStatus dsSetRecordName ( tRecordReference inRecordReference, tDataNodePtr inNewRecordName ) ;
dsSetRecordType |
tDirStatus dsSetRecordType ( tRecordReference inRecordReference, tDataNodePtr inNewRecordType ) ;
dsVerifyDirRefNum |
tDirStatus dsVerifyDirRefNum ( tDirReference inDirReference ) ;
Verify an existing tDirReference.
DSPROXY |
#define DSPROXY 1
outDirRefreference to use in subsequent Directory Services API calls
inHostOrIPAddresseither the hostname or dotted IP address of the remote DirectoryService machine
inIPPorteither the client defined port or "0" which then allows use of the default
Opens Directory Services API reference via TCP. Must be called before any other Directory Services API calls because this reference is needed for any other call.
Last Updated: 2009-08-12