You may wish to work with SAS Tech Support on this task. There are several different ways to do what you want to do and Tech Support has the people with the expertise to point you in the right direction, depending on whether you want SAS to generate the second form or whether you want to use Web Services or servlets or .... .
I'm interested in writing a simple custom GUI to running stored procs that pull the parameters dynamically from another data source (using ASP.NET). I already have a proof of concept, which actually works just fine. However, there is one major step that I cannot determine how to skirt.
The ASP.NET/HTML interface I have is actually inserted into our information delivery portal as a link. Therefore, whenever someone clicks the link, it opens up the interface right within the IDP. The user can choose options and click submit to see their report. The problem comes about right there. The user is then asked to authenticate again. That leads me to believe that whenever a user runs a stored proc from the IDP via SAS's interface, there is some way that SAS takes care of that authentication in the background.
Here comes the question:
What can I do with my little ASP.NET page to take care of that authentication? The user had already been authenticated through the IDP and I'd rather them not be asked to authenticate again.