tomweber-sas
commented
5 years ago Hey, yes can help you with this. First, so we're clear on terminology let me identify a couple things. Ill use IOM access method to refer to the original access method in saspy that uses the IOM-Java client. I'll use COM access method to refer to the new access method that @hhubbell contributed that uses the Windows com IOM client. IOM itself refers to the interface that both these access methods use to interact with a workspace server.
You're looking at COM access method. In both cases, the host and port are the hostname (ip) of the Object Spawner, not the metadata server, and the port is the port number that object spawner is listening on for Workspace server requests - again, not the metataserver port.
FYI, this is documented in the configuration guide: https://sassoftware.github.io/saspy/install.html#configuration
Next, you're asking about credentials. This is where things vary. So, in the usual case, authenticating via IOM, uses userid/password. For both IOM and COM access methods, you can store these in an _authinfo file (in the above mentioned doc). The COM access method didn't support this in it's first incarnation. The support for the authinfo file is at master right now, Next time I build a new release it will be in that release. But you can pull master to get that now,
However, you mention ldap to authenticate users. I think this correlates to having your authentication mechanism use IWA (Integrated Windows Authentication) instead of user/pw? If that is what you mean, then you wouldn't use the authinfo file, as it's not using user/pw to authenticate. If IWA is what it's configured to use, then the IOM access method supports this by use of the sspi key in your configuration definition:
From the IOM Config doc: sspi - New in 2.17, there is support for IWA (Integrated Windows Authentication) from a Windows client to remote IOM server. This is only for when your Workspace server is configured to use IWA as the authentication method, which is not the default. This is simply a boolean, so to use it you specify ‘sspi’ : True. Also, to use this, you must have the path to the spiauth.dll file in your System Path variable, just like is required for Local IOM connections. See the second paragraph under Local IOM for more on the spiauth.dll file.
However, at this time, I don't believe the COM access method has support for IWA, though I imagine it could, as IWA support is implemented via the IOM client, so I suspect the COM version can do this, since the Java version does. Harry, do you think you could investigate this?
I'm not 100% sure that if your server is configured to use IWA that you cannot use a user/pw, but I suspect that's the case. Certainly you could try it and see. If not, then we could get you up and running with the IOM access method for now, and try out the COM one if IWA support is added.
Thanks! Tom
hhubbell
junwansas
Hi,
I try to user SASpy on a windows server to connect to a remote SAS grid using iomcom. I'd like to have some help on the config file.
The iomhost should be the metadata server or work nodes which the sas session will run? Where should I put the credential? We use ldap on the server to authenticate users. each user has a metadata profile too.
This is what the sascfg.py looks like after installation. I'd like to know how do I change this config file and do I need a config file for each users? or can I let config file using signal signon? iomcom = { 'iomhost': 'mynode.mycompany.org', 'iomport': 8591, 'class_id': '440196d4-90f0-11d0-9f41-00a024bb830c', 'provider': 'sas.iomprovider', 'encoding': 'windows-1252'}
Thank you!
Jun