Re: Changing credentials on-the-fly

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 09/26/05

  • Next message: Tony Sebion: "Re: Duplicate an existig SQL user login account"
    Date: Mon, 26 Sep 2005 18:17:27 +0200
    
    

    The application need to set the application role using sp_setapprole.

    -- 
    Tibor Karaszi, SQL Server MVP
    http://www.karaszi.com/sqlserver/default.asp
    http://www.solidqualitylearning.com/
    Blog: http://solidqualitylearning.com/blogs/tibor/
    "Promenade" <promenade@no.com> wrote in message news:u3nPbjqwFHA.596@TK2MSFTNGP12.phx.gbl...
    > Thank you very much, Tom...
    > I don't know anything about application roles, so maybe you can help me...
    > When you said "They can login as themselves and then set the application
    > role"....the process of setting the application role has to be made in every
    > application code or this task can be made in SQL Server?
    > 
    > 
    > 
    > "Tom Moreau" <tom@dont.spam.me.cips.ca> wrote in message
    > news:#tiGw8pwFHA.2132@TK2MSFTNGP15.phx.gbl...
    >> Consider using an application role.  They can login as themselves and then
    >> set the application role.  The role stays in effect until logout.  You may
    >> have issues with connection pooling, however.
    >>
    >> -- 
    >>     Tom
    >>
    >> ----------------------------------------------------
    >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
    >> SQL Server MVP
    >> Columnist, SQL Server Professional
    >> Toronto, ON   Canada
    >> www.pinpub.com
    >>
    >> "Promenade" <promenade@no.com> wrote in message
    >> news:OwhJb2pwFHA.2656@TK2MSFTNGP09.phx.gbl...
    >> > Hi!
    >> > I have a late requirement from de Security Department.
    >> > This is the situation: the apps must connect to SQL Server 2000 through
    >> > OLE
    >> > DB using a generic user, but the developers will not know its
    > credentials
    >> > (at least the password)
    >> > Unfortunatelly, like I said, this is a late requirement because there
    > are
    >> > many apps already working, obviously knowing the credentials.
    >> > I spent so much time thinking a way to solve this problem without
    >> > codification, finally I arrived to this idea, but I don't know if it's
    >> > achievable.
    >> > - Create a new user in SQL Server and grant the right permissions on the
    >> > addecuate DBs
    >> > - Deny permissions to the old user
    >> > - Leave the apps just how they are now
    >> > - When an app attempt to open a connection, SQL Server must modify the
    > old
    >> > credentials with the new ones...
    >> >
    >> > Is this possible?
    >> > And obviously....how???
    >> > Otherwise, do you know another solution (without reprogramming)?
    >> >
    >> > Thanks in advance,
    >> > Promenade
    >> >
    >> > PS: I apologize my english
    >> >
    >> >
    >>
    >>
    > 
    >
    

  • Next message: Tony Sebion: "Re: Duplicate an existig SQL user login account"

    Relevant Pages