Desktop productivity for business analysts and programmers

SAS enterprise guide using signon and rsubmit with authdomain

Reply
Occasional Contributor
Posts: 7

SAS enterprise guide using signon and rsubmit with authdomain

hi

 

i am trying to use proc upload in SAS enterprise guide, and have to use signon server to be able to use rsubmit which is required for proc upload. I am in a "local" server envirement" in SAS EG.

 

the question is, how do i use the login information in SAS EG on this signon for rsubmit?

 

 

%let server=servername 2323;

signon server username=&sysuserid. password="&passwd_PASSWORD.";

RUN;

 

this works, but i have to type in the password which i dont want to do. I rather use authdomain="whatevermyautdomainiscalled"

this doesn't work because it says it can't find the authdomain i have reffered to. i have named my login profile this authdomain, also in the text field where it says "authentication domain".

 

any good ideas how to do this? and please don't comment that there a task that does the same Smiley Happy i need to use proc upload in some cases.

 

basically the question is, how do i use SAS EG login on a signon server?

 

Super User
Posts: 7,380

Re: SAS enterprise guide using signon and rsubmit with authdomain

Letting running code know the password for the current user would be a major security violation, so EG doesn't do it.

 

You might be able to use the encoded password from the egcred file in your Enterprise Guide configuration tree.

(C:\Users\user\AppData\Roaming\SAS\EnterpriseGuide\version\egcred)

 

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
Occasional Contributor
Posts: 7

Re: SAS enterprise guide using signon and rsubmit with authdomain

thank you for answering.

what is the difference between using authdomain in libname Oracle and this?

is it possible to do this With the help of libname?

hard to believe using user= and passwd= is the only way to do this.
Super User
Posts: 7,380

Re: SAS enterprise guide using signon and rsubmit with authdomain

You have to keep in mind that SAS/CONNECT is very old technology that simply does a telnet login to the server and then starts SAS from the commandline.

Since I've never used the SAS/CONNECT Spawner that is defined in the metadata server, I don't know if that could be used to short-cut the login process.

Of course you need to use a remote metadata server for this.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
Super User
Posts: 5,378

Re: SAS enterprise guide using signon and rsubmit with authdomain

I don't think that you need another Metadata server for this, but the remote spawner must be defined in the "local" metadata server.

See the documentation for metadata signons:

 

http://support.sas.com/documentation/cdl/en/connref/67933/HTML/default/n1mnvt2zgyyaqzn1gq0m8t9q7qbu....

Data never sleeps
Super User
Posts: 3,233

Re: SAS enterprise guide using signon and rsubmit with authdomain

If the remote SAS server you are trying to signon to runs under Windows and is in the same Windows domain as your PC then you could use Windows Authentication if SAS/CONNECT has been configured for this. Check with your SAS Adminstrator.

 

If you are not familiar with Windows Authentication it will allow you to signon without supplying a username and password. 

Valued Guide
Posts: 505

Re: SAS enterprise guide using signon and rsubmit with authdomain

I have not used SAS connect recently but I believe

 

1. SAS connect allows automatic login to one or more servers with an encrypted password

2. Unlike EG SAS connect sets up a persistent SSH tunnel integrating ocal and remote processing.

3. The sever real time log and output are  interleaved as staements execute with on your local very powerful display text editor (much better than the enhanced editor) {highlight dataset in log - list 40 obs - lsh for server or ls for local - using mouse button]

4. If you have an appliance then all folders are shared, other wise you should be able yo use SAS remote libraries.

5, Very easy to read/write to the local or server remote libraies.

 

Unfortunately I don't think SAS is alowing or enhancing(need a way to kill deamons amd ghost server processes) this very powerfull integration of server and power workstation(sometimes called PC SAS).

 

SAS connect is not strategic? Like gmap not supported in SAS UE?

Community Manager
Posts: 2,883

Re: SAS enterprise guide using signon and rsubmit with authdomain

Hi @rogerjdeangelis, I just want to clarify a couple of points.

 

First, SAS/CONNECT is still an important enabling technology in SAS.  Its features are the basis of SAS Grid Computing (where one SAS session can distribute work to multiple nodes) and it's also an important bridge between SAS 9.4 and the new SAS Viya platform.  Still relevant, still getting feature updates.

 

And as far as GMAP not being in SAS University Edition -- as a free, downloadable tool for learning, some scope limits are in place to balance usability with the basics needed for learning SAS.  SAS/Graph and the MAP data sets are very large and would expand the SAS University Edition footprint quite a bit.  However, you can practice your SAS skills with these for free by using the SAS OnDemand for Academics environment.  Any learner can sign up for access using SAS Studio, connecting to a SAS environment hosted by SAS.

Valued Guide
Posts: 505

Re: SAS enterprise guide using signon and rsubmit with authdomain

Goof to know about GMAP (but what about)

 

You can ignore the questions below if SAS would just make this stategic statement

 

SAS plans on discontinuing and further increase the cost of  'local' SAS and will soon disable all 'local' IDEs except SAS Studio(or EG).

 

Could we get explanations on other decisions

1. No command line in EG

2. No datastep debugger in EG

3. No interface to the operating system in UE (and frequently in EG)

4. No interactive window  option (ie window %window PMENU in EG

5. Recent increase in price for workstation SAS (SAS calls it PC-SAS)

6 No programmable mouse buttons option  (SAS function keys) in EG

7. Disabeling of 'STORE' script command in EE  single most useful SAS script command 

8. No SAS script commands in EG.

9 No prifix area option  in EG editor

10 No command macros in EG

11 The ignore valuable data option in the old text editor (ignore blank lines)

12 No user 'SAS connect in EG'

13 Disabling the

14 Marketing of 'LOCKDOWN' options

15 No Multiple screen option in VM EG

16 Push for SAS on a VM

17 Average memory limits od <4gb on server EG

18 Average limit on number of cores on VM EG (4 or fewer)

19 No marketing of local SAS using display manager

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PROC Star
Posts: 1,143

Re: SAS enterprise guide using signon and rsubmit with authdomain

I don't think you'll see SAS deprecate DMS (the "local" SAS option) anytime soon. As someone who promotes using EG, I find that the level of resistance to moving away from DMS is absolutely fanatical, sigh!

 

In the context of your list of features available in DMS but not EG, in my opinion most of them aren't suited to using EG with SAS in what is in effect a client-server type of operation, as opposed to the direct connection provided by DMS.

 

I would, however, like to comment on a few of your points:

 

"No interface to the operating system in UE (and frequently in EG)"

If you're referring to the "X" command, it can be available in EG. However, it is frequently disabled, as creating problems for the operating system can be an issue in a multi-user server. I have yet to see a really good use case for enabling it.

 

"No interactive window  option (ie window %window PMENU in EG"

True. Using SAS with EG is more of a "batch" operation, but the prompting framework does provide a pretty good mechanism for adapting the code.

 

"No user 'SAS connect in EG'"

Yes, and I like it this way. Using the very powerful Integration Technologies, the EG environment provides a secure, easy to use mechanism for inter-machine communications. It costs 10 times the support resources to support a user of SAS/Connect and the Libname statement to connect to a database as opposed to the EG mechanism.

 

"Marketing of 'LOCKDOWN' options"

Yes, in a production high-capacity data analysis environment, it is essential that certain options be put off-limits for users. On a per-user basis, this can always be changed on an exception basis.

 

"Average memory limits od <4gb on server EG"

There are absolutely differences between the memory limitations on an EG and SAS environment as opposed to using SAS with DMS. It is completely under the control of the system administrators.

 

"Average limit on number of cores on VM EG (4 or fewer)"

Ditto the previous response. In my opinion, the discussion of "average limits" makes no sense. There's an "average", which is the system default, and there's a "limit", which is the most that can be requested. To my knowledge, there's no difference between EG SAS and SAS DMS on these.

 

However, there is another issue at play here, and an important one. Generally, DMS users are using SAS on a machine that is all their own, which means that the limitations of that machine limits their capabilities with SAS. Also, when they're not using SAS to its fullest, the resources on their machine are going unused. With an EG SAS server environment, resources are shared between users, which means that if you have a need for massive resources, I as administrator can give you full access to the server. If you're fortunate enough to have a server-class machine on your desktop, I'm jealous. I certainly don't!

 

"No marketing of local SAS using display manager"

Given that it's almost impossible to move people AWAY from DMS, why would SAS market it? In terms of new users, yes, I always encourage them to start with EG. I find it's a much more suitable environment for both of the following user types:
1. People who need results using SAS, but who are not IT specialists: In this case, the many mental "programming" patterns and constructs needed to program in SAS can be avoided, and people can get the needed results in a much more cost-effective way.
2. People who will be programming in SAS, but don't know SAS: I find EG to be an excellent start, in that it's provision of generated code can provide a benficial alternative to staring at a blank screen, wondering what to type.

 

With the user type that you and I fall into, experienced, expert SAS programmers, frankly we can use whatever the heck we want. And I encourage you to do so. If you like DMS best, for heaven's sake keep using it. But I hope that you'll admit many of the benefits of the EG environment for less expert users.

 

Best,
   Tom

Super User
Posts: 5,378

Re: SAS enterprise guide using signon and rsubmit with authdomain

[ Edited ]
Spoiler
 

@rogerjdeangelis and @TomKari, your opinions are valid, but I feel like you're high jacking this thread. The discussion is way beyond SAS/CONNECT.
Perhaps you could continue in a new thread in Have Your Say...?

Data never sleeps
PROC Star
Posts: 1,143

Re: SAS enterprise guide using signon and rsubmit with authdomain

Hi, @LinusH and @rogerjdeangelis

 

You are completely correct, and my apologies. My enthusiasm (once again) got away from me!

 

Tom

Super User
Posts: 5,378

Re: SAS enterprise guide using signon and rsubmit with authdomain

@TomKari enthusiasm is gr8, keep it up 😀
Data never sleeps
Ask a Question
Discussion stats
  • 12 replies
  • 1380 views
  • 3 likes
  • 7 in conversation