Atrium & Genie and users without command line access
Posted: Wed Mar 16, 2016 1:22 pm
We are currently enhancing our application to run within the Atrium framework and are rewriting a number of processes as Rich Display Files. However a number of our programs will remain as standard RPG and CL and will be served up within the Atrium tabs by using Genie.
We have set up an XML macro so that when we call one of the standard RPG programs with the Genie URL (and bypassing the signon using /auth) it goes through the inital pages and calls the program in question. This works fine for a user who logs on with command line access. However, it doesn't work for users who don't have command line access and are fed into a menu on logon. I am able to detect for the two different screens and take an action (e.g. if on menu screen, enter a menu #). However, I am at a loss on how to feed in a program call as a variable when there is no command line access.
One thought we had - create a prompt program to put on the menu that accepts a parameter and can call the program passed in - however, that somewhat bypasses the security and allows the user to make calls in green screen that they would not normally be able to make (assuming they could figure out what program to enter in the prompt).
Is there a best practice on how to address this situation without giving some form of command line access to users that shouldn't get access?
Thanks,
Tony
We have set up an XML macro so that when we call one of the standard RPG programs with the Genie URL (and bypassing the signon using /auth) it goes through the inital pages and calls the program in question. This works fine for a user who logs on with command line access. However, it doesn't work for users who don't have command line access and are fed into a menu on logon. I am able to detect for the two different screens and take an action (e.g. if on menu screen, enter a menu #). However, I am at a loss on how to feed in a program call as a variable when there is no command line access.
One thought we had - create a prompt program to put on the menu that accepts a parameter and can call the program passed in - however, that somewhat bypasses the security and allows the user to make calls in green screen that they would not normally be able to make (assuming they could figure out what program to enter in the prompt).
Is there a best practice on how to address this situation without giving some form of command line access to users that shouldn't get access?
Thanks,
Tony