Sponsored Content
Special Forums Windows & DOS: Issues & Discussions Windows AD for Unix authentication Post 302301248 by speriya on Thursday 26th of March 2009 10:02:47 AM
Old 03-26-2009
Windows AD for Unix authentication

I am not an expert in Unix at all. My knowledge of Unix is average. We have a couple of Unix servers, Solaris and Linux, which run mostly web servers, and Oracle databases. Currently users have multiple user IDs for Unix and AD applications. Is it possible to make use of the Windows Active directory as the authentication provider for Unix users? Can this be done at all? I was reading on Windows Service for Unix. But not very clear if it does provide direct AD authentication for Unix boxes? We would like to centralize the authentication to just one provider, the AD. Appreciate any inputs.
 

5 More Discussions You Might Find Interesting

1. Linux

How to Unite Redhat 9 Linux with Windows 2003 Active Directory authentication

Dear All, How to configure a Redhat 9 client to windows 2003 server. I have windows 2003 server which act has domain controller in my office. I have been asked to use redhat 9 has client. how to configure so that redhat 9 can authenticate with windows 2003 server .I have username created in... (0 Replies)
Discussion started by: solaris8in
0 Replies

2. Solaris

Key authentication between solaris & windows server.

Hi Gurus I have a solaris box from which i will have to sftp into a windows box. I have installed core ftp server in the windows box and so am able to log in. My problem is that,I have to enable password less authentication between solaris box and this core ftp server. How do i do this? ... (1 Reply)
Discussion started by: Hari_Ganesh
1 Replies

3. Linux

How to connect Linux server (configure two way authentication) with Windows server?

Hi my name is Manju. ->I have configure the two way authentication on my linux server. ->Now I am able to apply two way authenticator on particuler user. ->Now I want to map this linux server to my AD server. ->Kindly tell me how to map AD(Active Directory) with this linux server. ... (0 Replies)
Discussion started by: manjusharma128
0 Replies

4. Cybersecurity

Looking for suggestion on authentication method for UNIX/Windows

Hello, We have mid level infrastructure of all on-premises servers. All windows servers are getting authenticated by Microsoft Active Directory Services, half Unix (Solaris+Linux) servers are getting authentication by NIS and other half by LDAP. We have plans to migrate from NIS to LDAP, so... (2 Replies)
Discussion started by: solaris_1977
2 Replies

5. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
CURLOPT_UNIX_SOCKET_PATH(3)				     curl_easy_setopt options				       CURLOPT_UNIX_SOCKET_PATH(3)

NAME
CURLOPT_UNIX_SOCKET_PATH - set Unix domain socket SYNOPSIS
#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_UNIX_SOCKET_PATH, char *path); DESCRIPTION
Enables the use of Unix domain sockets as connection endpoint and sets the path to path. If path is NULL, then Unix domain sockets are dis- abled. An empty string will result in an error at some point, it will not disable use of Unix domain sockets. When enabled, curl will connect to the Unix domain socket instead of establishing a TCP connection to a host. Since no TCP connection is created, curl does not need to resolve the DNS hostname in the URL. The maximum path length on Cygwin, Linux and Solaris is 107. On other platforms it might be even less. Proxy and TCP options such as CURLOPT_TCP_NODELAY(3) are not supported. Proxy options such as CURLOPT_PROXY(3) have no effect either as these are TCP-oriented, and asking a proxy server to connect to a certain Unix domain socket is not possible. The application does not have to keep the string around after setting this option. DEFAULT
Default is NULL, meaning that no Unix domain sockets are used. PROTOCOLS
All protocols except for file:// and FTP are supported in theory. HTTP, IMAP, POP3 and SMTP should in particular work (including their SSL/TLS variants). EXAMPLE
Given that you have an nginx server running, listening on /tmp/nginx.sock, you can request a HTTP resource with: curl_easy_setopt(curl_handle, CURLOPT_UNIX_SOCKET_PATH, "/tmp/nginx.sock"); curl_easy_setopt(curl_handle, CURLOPT_URL, "http://localhost/"); If you are on Linux and somehow have a need for paths larger than 107 bytes, you could use the proc filesystem to bypass the limitation: int dirfd = open(long_directory_path_to_socket, O_DIRECTORY | O_RDONLY); char path[108]; snprintf(path, sizeof(path), "/proc/self/fd/%d/nginx.sock", dirfd); curl_easy_setopt(curl_handle, CURLOPT_UNIX_SOCKET_PATH, path); /* Be sure to keep dirfd valid until you discard the handle */ AVAILABILITY
Since 7.40.0. RETURN VALUE
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not. SEE ALSO
CURLOPT_OPENSOCKETFUNCTION(3), unix(7), libcurl 7.54.0 December 21, 2016 CURLOPT_UNIX_SOCKET_PATH(3)
All times are GMT -4. The time now is 05:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy