----- Original Message ----- > On Sun, Jun 15, 2014 at 07:08:55PM -0400, Yassir Elley wrote: > > > > > > * You suggested using the name of the DC that SSSD is currently connected > > to in the smb uri (rather than the domain.name, which will require > > libsmbclient to perform a DNS resolution). Is there an easy way to get the > > name of the DC that SSSD is currently connected to? I am having trouble > > finding it. > > > > In struct ad_gpo_access_state you have a member struct sdap_id_conn_ctx > *conn. conn->service->uri is the LDAP uri for the current connection. > You can use calls from OpenLDAP or ldb to split it into components, picj > the hostname and create the smb uri. > > In general the uri should always be available since you read the GPO > data from LDAP before doing the smb operations. Nevertheless you can > call be_resolve_server_send() to make sure it is set, see e.g. > auth_get_server() how to use it. > > HTH > > bye, > Sumit > _______________________________________________ > sssd-devel mailing list > sssd-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/sssd-devel >
I have attached a revised patch that modifies the smb uri to use the server name rather than the domain name. Thanks, Yassir. _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-devel
