Hi Tyler,   I have a few suggestions, some code, some point & click, some free and some commercial.   1) Write some SAS code using proc metadata or the data step functions to query metadata for InternalLogin objects and then follow the associations to find the associated person (user). For more info check the documentation resources SAS® Language Interfaces to Metadata, SAS® Open Metadata Interface: Reference and Usage and SAS® Metadata Model: Reference   2) If you have access to SAS Display Manager use the metabrowse feature to browse the InternalLogin objects and follow the associations to find the associated person (user).   3) If you have access to SAS Management Console, use our free Metacoda Metadata Explorer plug-in to search for all users that have an associated InternalLogin object and export the results to a CSV file.   4) If this is something you expect to be doing regularly, have a need to generate documentation, and potentially want to get email alerts when somebody adds an internal login for a user that is not in an 'approved' list, then you might consider looking at our commercial Metacoda Security Plug-ins product. This includes several metadata security focused plug-ins, including Internal Login Reviewer and a Metadata Security Testing Framework.   I hope this helps.   Cheers Paul ... View more

It sounds like SSH tunneling is being used where an SSH connection is made to a SAS server (or another machine within the SAS servers network) and the SSH client opens ports on the workstation and forwards traffic to designated ports in the server network. This can be tricky because the SAS servers will return hostnames for the client to connect to and so those hostnames will have to be redirected to the localhost interface for the client to use the SSH tunnels.  I had tried this with mixed success with SAS in the past and ended up switching to using a VPN instead.   However for the use case you mentioned (SAS EG connects to the metadata server on tunnelled port 8561 and then to the object spawner on tunnelled port 8591) I was able to get it to succeed (although if you turn on EG logging you may see failures to connect on other ports such as 7980).   The process I followed, with the SSH server, SAS metadata server and SAS object spawner all running on the same server machine, was: Configure the server firewall to block all connections from the client except SSH port 22 Edit the clients hosts file to redirect the server hostname(s) to localhost - this includes both short and fully qualified hostnames (e.g. 127.0.0.1 locahost sasserver sasserver.example.com). Whilst you might use localhost or 127.0.0.1 for the initial connection to the metadata server the connection to the object spawner will be done using the server name registered in metadata (e.g. sasserver.example.com). This has to also be redirected to localhost to use the tunnel. Of course, if this is being done for remote access for a mobile workstation, it will need to be reverted whenever the workstation returns to the target network. SSH to the server with the 2 tunnels e.g. ssh -v -L 8561:localhost:8561 -L 8591:localhost:8591  localhost is used here because the metadata server and object spawner are on the same machine where the remote end of the SSH tunnel is. Actual host names would be used if they were on different machines to the SSH server. Start up EG and use a profile that connects to sasserver on port 8561. With local host redirection this will send it to localhost port 8561 which will be forwarded over the SSH tunnel to remote localhost/sasserver port 8561 Within EG expand SASApp to trigger the connection to the workspace server. The metadata query will return the object spawner host name and port (e.g. sasserver:8591) With local host redirection EG will connect to localhost port 8591 which will be forwarded over the SSH tunnel to remote localhost/sasserver port 8591 Checking the object spawner log file you will see the client connection peer IP address is the SSH server machine where the remote end of the tunnel emerges (which may be 127.0.0.1 if the SSH server and object spawner are on the same machine). This all worked for me so I am wondering if perhaps there is something amiss with either your local hostname redirections or tunnel configurations. Can you post details on your server topology, how you have edited the workstation hosts file and how you setup the SSH tunnels.   Also which version of SAS and EG are you using. My test above was with SAS 9.4 M0 and SAS EG 7.1.   Cheers Paul   ... View more

Have you seen the document Overview of Deploying SAS Web Parts for Microsoft SharePoint? ... View more

Perhaps a SAS Communities admin could move this from the Web Report Studio community into the SAS Studio community or the Administration and Deployment community? It might get better visibility there. ... View more

When you say it is not working, how is it not working? What error messages are users getting in the SAS Logon Manager web interface? What error messages are you getting in the SAS Object Spawner log files? Are there any interesting error or warning messages in the SAS Metadata Server log files or SAS Web Application Server logs files? By providing more specific details it usually helps to better identify the problem or provide clues on where to look next. ... View more