application login , but user security

From: sql rookie (anytasks_at_gmail.com)
Date: 04/28/05

  • Next message: Donna Lambert: "Re: Multiple accounts with the name MSSQLSvc..." 
    Date: 28 Apr 2005 08:47:12 -0700

    Hi everybody...please don't flame me for my ignorance.
    We are in the process of migrating from mainframe application using
    vsam files to MICROFOCUS and SQL server
    Here is the senario we are at now :
    In mainframe, the application might be able to read and write to the
    file, but the write access is controled by the RACF (security software
    like active directory). In other words, even though USER A can execute
    the application, he cannot write to it, because the security software
    doesn't allow USER A to write to the file.

    In the new environment, our online application are replaced by a
    product called MICROFOCUS -ES_MTO. ES-MTO connects to sqlserver via an
    application userid (lets say APPL1). USERA logins in to the ES-MTO
    using login id USERA, but then ES-MTO connects to sqlserver using
    APPL1. APPL1 has read/write authority on the tables. USERA should be
    able to execute the application, so he can read the table, but
    shouldn't be able to write to it.
    The application is however a read/write application.

    I hope I was clear enough on my sceneraio.
    What I am hoping to find out is, how can I still use sqlserver to check
    permission using the real user login id , when the application uses the
    application userid to connect ?
    Am I making sense ?

    Any help or input is greatly appreciated .

    Thanks

  • Next message: Donna Lambert: "Re: Multiple accounts with the name MSSQLSvc..."

    Relevant Pages

    • Re: Moving BACK to the mainframe
      ... I have been reading IBM-Main off and on for awhile and one of the ... is, of course, the phasing out of the mainframe at various shops. ... More recently, the company wanted to move to a newer version of Windows, but found their old copies of MicroFocus wouldn't run on Windows XP. ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
      (bit.listserv.ibm-main)
    • Re: Moving BACK to the mainframe
      ... They hadn't fully succeeded in doing that yet, so luckily they had the option to fall back to the mainframe once they realized how expensive it was going to be to keep their MicroFocus licenses up-to-date. ... I have been reading IBM-Main off and on for awhile and one of the ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
      (bit.listserv.ibm-main)
    • Re: Read and Write unknown record length? MVS
      ... This is a MicroFocus IBM developement platform. ... It has a catalog like a mainframe. ...
      (comp.lang.cobol)
    • Moving BACK to the mainframe
      ... I have been reading IBM-Main off and on for awhile and one of the ... management decreed many years ago to move everyone off the mainframe. ... More recently, the company wanted to move to a newer version of Windows, but found their old copies of MicroFocus wouldn't run on Windows XP. ... management decided quite recently they were going to get rid of their mainframe and use MicroFocus to run existing COBOL applications on smaller platforms. ...
      (bit.listserv.ibm-main)