Migrated from OpenIndia to the Napp-it appliance. Brought over my lic key, and got owncloud up and rocking. Now, fighting with ACL and user authentication.
Just recently connected napp-it to my windows domain to integrate authentication with machines/users. One thing that I've stumbled upon is when browsing to the UNC path I am prompted with a login box to auth. It shows my sign-in domain as the correct domain, but I must enter a un/pw to connect. The only way I've been able to get my domain users to connect is go auth against the omnios appliance.
For example:
domain\windowsuser=will not connect
machinename\windowsuser=will connect
See image below:
san is the name of the omnios box. Machine I am logging in from is joined to the domain. It does not appear to be auth'ing against the domain.
My goal is to use AD to auth the user with no need to input a password.
Looked over napp-it // webbased ZFS NAS/SAN appliance for OmniOS, OpenIndiana, Solaris and Linux : Extensions but it seems I need to set the user/password on the appliance in order for this to work. This would be the last ditch preference as I want to have passwords expire within AD.
Did I skip a step on my configuration?
Just recently connected napp-it to my windows domain to integrate authentication with machines/users. One thing that I've stumbled upon is when browsing to the UNC path I am prompted with a login box to auth. It shows my sign-in domain as the correct domain, but I must enter a un/pw to connect. The only way I've been able to get my domain users to connect is go auth against the omnios appliance.
For example:
domain\windowsuser=will not connect
machinename\windowsuser=will connect
See image below:
san is the name of the omnios box. Machine I am logging in from is joined to the domain. It does not appear to be auth'ing against the domain.
My goal is to use AD to auth the user with no need to input a password.
Looked over napp-it // webbased ZFS NAS/SAN appliance for OmniOS, OpenIndiana, Solaris and Linux : Extensions but it seems I need to set the user/password on the appliance in order for this to work. This would be the last ditch preference as I want to have passwords expire within AD.
Did I skip a step on my configuration?