No.
There are two logins involved:
1) Connecting to either the metadata server or the metadata repository, which requires the AD login authentication of the EG user. I may not be stating this precisely correctly, but the point is, if the user isn't in the MetaData repository, he/she can't use any remote EG resources.
2) Connecting to the remote server.
There are a number of ways for EG to connect and authenticate to a remote server. At the very least, there is a single Unix account -- let's call it SAS_EG -- that is used by EG to connect to the remote server. At the very most, there is an LDAP product that allows EG to use the user's ID to connect to the remote server.
As examples:
At my previous place, we had a logical server for each group that used SAS. For each of these groups, there was a respective Unix account, which provided a common repository for that groups stuff. It allowed/provided for isolation of the groups from each other for processing efficiency, storage separation, and a certain measure of security. Each user had to be listed in the list of users in the EG metadata repository, and each user was then assigned to a group. Each logical server had access limited to a particular group, and used the group's Unix login ID to connect/login to the Unix box.
At my current place, we have a SAS MetaData Server. A script clears its set of users and repopulates it from AD every night. Through AD each user can access a remote logical server through their individual login id. The remote logical server runs on a Windows server, here. Because of this established mechanism, and a current lack of LDAP for our Unix servers, we are not able to make use of a Unix server for a SAS server (which is a bummer, since we would greatly benefit from the 64-bit processing and faster more efficient IO).