Sage 100

 View Only

  • 1.  Command line VI jobs without plain text passwords in the batch file?

    Posted 02-20-2024 11:50

    I don't believe VI jobs from a batch file can work without a plain text password.  (Even with Unified login enabled). 

    Is that correct? 

    (Going through a customer IT security review, and I expect they will complain about this).

    Link



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------


  • 2.  RE: Command line VI jobs without plain text passwords in the batch file?

    Posted 02-20-2024 15:19

    Not sure if the VI jobs are automated or not however, you don;t necessarily need to have a plain text password in the batch file.  You could pass the password to the batch file using a parameter.  For example, substitute the password in the bat file for %1 then, if the batch file is named MyBatch.bat. at a command prompt the user would type MyBatch.bat 12345ABC where the password is 12345ABC.

    I have the following MyBatch.bat file saved in C:\users\DouglasHiggs

    cd "C:\Sage\Sage100v71\MAS90\Home\"

    "C:\Sage\Sage100v71\MAS90\Home\Pvxwin32.exe" .. \Launcher\Sota.Ini ..\SOA\Startup.M4P -ARG DIRECT UION tst %1 ABC VIWI2C AUTO

    if I go to a command prompt and directory C:\users\DouglasHiggs then type MyBatch.bat 12345ABC  then 12345ABC gets passed to the %1 variable.

     



    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------



  • 3.  RE: Command line VI jobs without plain text passwords in the batch file?

    Posted 02-20-2024 15:29

    Nice!  This is for automation, but if I put the password as an argument in the Scheduled Task, that would be hidden from users (who won't have access to the Sage server's Task Scheduler).

    Thanks for the idea!



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 4.  RE: Command line VI jobs without plain text passwords in the batch file?

    Posted 02-21-2024 04:07

    Kevin - Exactly what Doug said. Also here's another idea. If you use the Sage Task Scheduler to schedule a V/I import job, I'm pretty sure the Windows Task Scheduler task is created without passing either the Sage user or password as arguments. Rather, executing the task finds its way to reading through Sy_TaskScheduleHeader and Sy_TaskScheduleDetail tables, one of which holds the Sage user/pswd you selected in the Sage Task Scheduler UI, which is what I believe it uses for the external Sage login to run the import. You can see the user/pswd fields with DFDM.



    ------------------------------
    Alnoor Cassim
    Accounting Systems, Inc. (ASI)
    ------------------------------

    Original Message


  • 5.  RE: Command line VI jobs without plain text passwords in the batch file?

    Posted 02-21-2024 10:09

    While I never tried it with Sage, generally when I have this requirement, I convert my bat to an exe (there is a utility called bat2exe that allows this. 
    While this doesn't encrypt the content and can be de-compiled by a savvy user, it would hide the contents from prying eyes (for most...)



    ------------------------------
    George Khairallah
    CTO / Co-Founder | gotomyerp, LLC
    george.k@gotomyerp.com | 877-888-5525
    https://gotomyerp.com
    ------------------------------



  • 6.  RE: Command line VI jobs without plain text passwords in the batch file?

    Posted 02-21-2024 11:25

    Interesting @George Khairallah



    ------------------------------
    Jeff Schwenk
    Bottomline Software, Inc.
    (540) 221-4444
    ------------------------------

    Original Message


Related Content