Have a read of SAS(R) 9.2 Intelligence Platform: Security Administration Guide to check whether you have IWA correctly configured. I saw that you are running 9.1.3, but documentation for IWA for that version is less easy to come by. Personally, I would be looking at upgrading any - both Windows 2003 and SAS 9.1.3 were released over 10 years ago. The omaconfig option only relates to saving of credentials for inbound connections (connections to the metadata server) - so doesn't apply to your situation, as you are not entering credentials for the metadata server host but relying on a windows token. Next, the host on which your SASApp workspace server is running on should be in the same authdomain as the metadata server (defaultauth). Then do the checks suggested by SASKiwi. If you are still being prompted, check your Object Spawner log file for some clues. Jaap highlights some interesting points for a generalised world but much is not relevant to you - configuring trusted web authentication doesn't help with Enterprise Guide and the sasauth module doesn't exist on windows. What you are attempting is a good practice, as it removes any dependency on passwords stored within metadata (and any perceived vulnerability this might bring), instead you using Windows' ability to pass kerberos tokens around between machines.
... View more
