The Unix admins will have to have implemented an LDAP login solution that is integrated with AD for that to work.
What I did previously, at a different place, was to have group logins for the server: Research, Marketing, Operations, Capacity Planning, etc. Each group had its own logical server defined in the EG Repository. Each logical server was limited to allowing only the people in its "group" login access. Login information was not predefined, but retained so that I did not have to know the password the group chose to use. The members of a group could use the group signon to telnet to the box, where they could set their own private password -- but shared within the group -- and then when they went to use their logical server, EG would prompt them for the password, but only once. If the password changed, they would have to explicitly change the logical server's password. This minimized maintenance efforts.
If you have an appropriate LDAP solution, that integrates with AD, then the group login thing wouldn't be necessary, as each user would have their own controlled/auditable access to the server. But, you should still create the logical servers, and use groups to control access to the logical SAS servers. Then, users can be added/removed from the group(s) through AD, simplifying maintenance and auditability.
There is a lot more to this, a lot of little details that can trip you up. So, I recommend doing a lot of reading and planning. When done correctly, the admin will be a consumate expert, but the users will simply have simple access, with out any trouble.